Site architecture: the Hub & Spoke model

The Hub & Spoke model organizes a site around a central page — the hub, or pillar page — that covers a broad topic, surrounded by secondary pages — the spokes — each covering a sub-topic in depth and consistently linking back to the hub. This architecture, popular in SEO for years, serves visibility in generative engines just as well.

The principle, in one image

Picture a bicycle wheel. The hub at the center is the pillar page: a page that introduces an entire topic (say, “GEO” or “keyword research”) without going deep into every detail. The spokes are pages that cover a specific sub-topic (“thinking in entities”, “finding keywords with Google Search Console”) in depth, each linked to the hub and, ideally, to other relevant spokes.

A hub with no spokes stays shallow on every sub-topic. Spokes with no hub remain isolated pages, with no overall structure or coherence signal for engines to pick up on. It's the combination of both that creates value.

Why this model beats a set of isolated pages

Without an explicit structure, a site that publishes content regularly often ends up accumulating similar pages with no clear relationship between them, competing against each other instead of reinforcing one another. The Hub & Spoke model imposes the opposite discipline: before publishing a new page, you ask which hub it belongs to and which existing spokes it should reference. Content organizes itself into coherent clusters rather than a flat list of articles.

A concrete example: a site that publishes ten independent articles on aspects of SEO, with no hub and no cross-links, will statistically struggle more to rank any one of them than a site that organizes those same ten articles into a single cluster around a shared pillar page.

What star-shaped linking brings to classic SEO

Three well-documented benefits. First, the distribution of link equity: every spoke that earns external links passes some of that value to the hub through internal linking, reinforcing the cluster's most strategic page. Second, a signal of topical depth: an engine that sees a hub surrounded by ten specific, well-linked pages understands the site covers the subject seriously, not just on the surface. Third, easier crawling: a star-shaped architecture limits the number of clicks needed to reach any page from the hub, which favors faster, more complete indexing.

What it brings specifically to GEO

For a generative engine that has to answer a precise question, a well-built Hub & Spoke cluster offers exactly what it's looking for: a page that addresses the exact sub-topic of the question, without dilution, and a broader context (the hub) that confirms this page belongs to a site that genuinely knows the subject — a trust signal that matters when the engine picks which sources to cite.

It's also easier to maintain over time: when a topic evolves, updating one precise spoke is simpler than reworking a monolithic article that mixed every level of detail together. And it scales more gracefully with a team: different writers can own different spokes in parallel without stepping on each other's territory, as long as everyone agrees on what the hub already covers.

Building your own Hub & Spoke, step by step

1. Identify the broad topic that deserves a hub: a theme you have enough content, or enough material, for to justify five to ten distinct sub-topics.
2. List the sub-topics using data you've already gathered — queries from Search Console, suggestions from free tools, recurring questions from your customers.
3. Write or identify the hub: a pillar page that introduces every sub-topic and points to its corresponding spoke.
4. Write the spokes one at a time, each linked to the hub from the introduction onward, and supplemented with links to neighboring spokes where relevant — this work of linking pages to one another is covered in the lesson on internal linking.
5. Check the consistency of entities used from page to page: the glossary helps keep terminology stable across the whole cluster.

Expect anywhere from several weeks to a few months for a complete cluster to show visible results in rankings or citations, the time it takes engines to recrawl and reassess the whole set of linked pages.

How many spokes does a hub need

There's no fixed number, but a cluster starts producing measurable effects from around five to seven spokes, well linked to each other and to the hub. Below that, the signal of topical depth stays too weak to stand out from a site that only covers the subject on the surface. Beyond around fifteen spokes, it's often worth asking whether the topic should be split into two separate hubs, each with its own, tighter set of spokes.

Common mistakes to avoid

The first mistake is creating spokes that repeat the hub's content instead of deepening it: every spoke should add information the hub, being more general by design, can't develop. The second is forgetting links back to the hub once spokes are published, or adding them only once at the bottom of the page with no context, where they go largely unclicked. The third, more subtle, is building a hub too early: without at least three or four spokes already written, a hub remains an empty shell that proves nothing. A fourth, less obvious mistake is linking every spoke to the hub but never to each other, which leaves the cluster looking more like a set of spare spokes than an interconnected wheel.