Hub, sequence, or flat library? Choose a site architecture

Three site shapes answer different operating needs

A cluster diagram is not inherently superior to a journey sequence or a well-labelled flat library. The useful comparison starts with constraints: how many distinct decisions exist, whether they have prerequisites, how often the catalogue changes, and how confidently editors can maintain answer ownership. This article compares three models without assigning a universal winner. Google documents logical organization and crawlable links, while user-centered guidance asks whether people can complete realistic tasks. Those principles leave room for several shapes. Create a decision matrix with rows for reader orientation, answer overlap, maintenance burden, direct-link resilience, accessibility of labels, and ease of testing. Evidence belongs in cells; a decorative score does not. A hard failure—such as destinations that cannot be reached or labels whose purpose is unclear—should stop adoption regardless of a high total.

Evidence: Google Search Central; GOV.UK Service Manual

Set the comparison constraints

The matrix is the original artifact and should be filled from the site’s actual inventory rather than from an SEO diagram found elsewhere.

Evidence: Google Search Central; World Wide Web Consortium

Hub and spoke: orientation with a maintenance cost

A hub-and-spoke model suits a broad subject that can be introduced coherently while each child owns a durable subdecision. The hub can set boundaries, disclose the map, and route readers directly to evidence-rich destinations. It becomes fragile when the hub repeats every answer, spokes compete for identical jobs, or editors add children simply because a keyword appears related. Maintenance also concentrates at the center: consolidations, renamed branches, and new prerequisites require the hub to stay accurate. In the matrix, this option performs well when newcomers need orientation and the subject has a stable taxonomy. Mark it for review when most sessions begin on deep pages, when children cross-link mainly to satisfy a scheme, or when the central label cannot predict the range beneath it. Google’s guidance supports sensible structure but does not certify the pillar page as a ranking mechanism.

Test this option by asking whether a visitor can enter through a spoke, understand context, and continue without returning to the hub.

Evidence: Google Search Central; Google Search Central

Journey sequence: strong prerequisites, weaker random access

A sequential path works when one decision genuinely depends on another—for example, defining a claim before checking its substantiation, then deciding how to disclose an offer. Its strength is pedagogical order: prerequisite links are explicit and each step can state what the reader should carry forward. The risk is false linearity. Experienced visitors may need step four immediately, and a forced ‘next’ interface can obscure direct access or create unnecessary clicks. In the matrix, examine whether every sequence edge represents required knowledge or merely the author’s preferred teaching order. Use descriptive anchors that remain meaningful outside the sequence and make every destination available through ordinary navigation. W3C’s link-purpose principle is particularly relevant because ‘previous’ and ‘next’ may be ambiguous when pages are shared in other contexts.

Choose this shape only when skipping a step creates a specific comprehension or decision error that can be explained, not because a funnel graphic looks tidy.

Evidence: Google Search Central; GOV.UK Service Manual

Flat task library: direct access with naming pressure

A flat library gives each answer a clear task label and makes popular destinations directly reachable. It can be the most honest structure for a small site whose subjects do not form reliable prerequisites. There is less pressure to manufacture a pillar, and deep links remain useful. However, the labels must carry more orientation, related tasks can become difficult to scan, and new articles may silently duplicate an existing job. Score this model against actual findability sessions: can newcomers select the correct answer from the top-level list, and can they recognize what is intentionally absent? GOV.UK’s realistic-task discipline is more informative than counting menu items. As the library grows, lightweight groupings or filters may help, but every added layer needs its own comprehension test. A flat design is not a lack of architecture; it is an explicit choice to prioritize direct task access.

Its maintenance control is an ownership ledger checked before any new label enters the catalogue.

Evidence: GOV.UK Service Manual; World Wide Web Consortium

A mixed model for an affiliate learning site

Consider a small publisher covering disclosure, offer due diligence, tracking, and content operations. The matrix might support a flat task library at the top because these areas do not always form one sequence. Inside offer due diligence, a short hub could distinguish merchant legitimacy, commercial fit, and claim verification. A disclosure tutorial might use a sequence because recognition, placement, and wording build on one another. This is an illustrative design choice, not a tested performance result. The mixed model is defensible only if navigation labels reveal the change in shape and deep pages still receive direct, crawlable links. Document why each local model was chosen, who maintains it, and which task would cause reconsideration. Consistency of visual treatment should not force conceptual relationships that the evidence does not support.

The example also shows why choosing one architecture for an entire domain can create more duplication than clarity.

Evidence: Google Search Central; Google Search Central; GOV.UK Service Manual

Make a conditional decision, then revisit it

Fill the matrix for one bounded subject with dated inventory evidence, two representative task observations, and the known maintenance owner. Record a pass, review, or stop for each criterion instead of averaging incompatible risks. The immediate next step is to compare the current shape with exactly one alternative and identify the smallest reversible difference—perhaps relabelling a hub, exposing a deep task, or removing a redundant sequence edge. Limitations are material: search-engine crawling is not equivalent to reader comprehension; a usability session cannot forecast ranking; and a model that works for ten URLs may fail after the catalogue triples. Do not migrate solely to match a preferred diagram. Choose the shape whose weaknesses can be maintained and tested under current resources, preserve the old route map, and set a review trigger based on new jobs or repeated navigation failure rather than an arbitrary redesign calendar.