If there is one structural idea that separates directories that scale from directories that stall, it is the hub and spoke model. It sounds simple, and it is, but builders routinely get the relationship backwards or leave it half finished, and the site never coheres. Done properly, this single pattern lets a directory grow to thousands of pages while staying legible to a reader and a search engine alike.
The model is borrowed from how airlines route flights. A hub is a central point that connects to many destinations. A spoke is one of those destinations. On a directory, a hub is a category page and a spoke is an individual profile. The whole site becomes a set of hubs, each surrounded by its spokes, linked together into a coherent map.
What a hub does
A hub gathers. It is the page for a whole category, for example independent coffee roasters in one region or family run guest houses along a stretch of coast. Its job is to introduce the group, present the members in a comparable shape, and link down to each one. The hub is what a search engine reads to understand the category, and it is where your broad, high volume keywords will land.
A good hub is not a bare list. It opens with a genuine overview that answers the questions a newcomer to the category has. It orders the spokes in a way that helps comparison. And it carries links out to the guides that help a visitor choose. The relationship between a hub and the pages it gathers is the same relationship we describe in the anatomy of a directory site that ranks, seen from the structural side.
What a spoke does
A spoke satisfies. It is the profile page for one entity, and it answers the specific question a visitor arrives with. Where the hub wins a broad search like wedding venues in a county, the spoke wins a narrow one like the name of a single venue. The two capture different visitors at different stages, and a directory needs both.
The discipline of a spoke is depth on one subject. It should tell a visitor what the entity is good at, who it suits, what it costs in plain ranges and how it compares to the obvious alternative. A thin spoke that repeats a name and address adds nothing and, worse, drags down the trust of the hub above it. Every spoke should be a page you would be content to have rank on its own.
The links that make it work
The model is not just two page types. It is the links between them, and this is where most builders fall short. Every spoke should link up to its hub. Every hub should link down to its spokes. And spokes should link across to a small number of relevant siblings, so a visitor comparing options can move between them without returning to the hub each time.
These links do real work. They tell a search engine how the site is organised, which pages are central and how topics relate. They pass ranking strength from strong pages to weaker ones. And they keep visitors moving through the catalogue rather than bouncing back to a results page. A directory with strong pages but weak internal linking is a set of islands. The hub and spoke model is the bridge network that turns islands into a country.
The rule of three
The practical version I give every builder is a rule of three. Each spoke should carry at least three deliberate internal links: one up to its hub, one across to a sibling, and one to a relevant guide or group page. That is the minimum for a page to be part of the map rather than an orphan. More is fine when it is natural. Fewer leaves the page stranded, found by no one and helping nothing.
This rule is not arbitrary. It mirrors how a thoughtful human would point a visitor onward. If you were standing in the venue describing it to someone, you would mention the category it belongs to, name a comparable option, and point to the guide that helps them decide. The links simply encode that instinct.
How hubs and spokes scale
The reason this model scales is that it is fractal. A large directory is not one hub with a thousand spokes. It is a hierarchy of hubs. A region hub links to city hubs, each city hub links to category hubs, each category hub links to its spokes. The same gather and satisfy pattern repeats at every level, which keeps even a very large catalogue navigable.
This is also how a directory turns inventory into pages. When you understand that every meaningful pairing of place and category can become a hub, the page count grows quickly without becoming chaotic, because the structure holds. The arithmetic of that growth, and the discipline needed to keep it from producing thin pages, is something our group treats as core to how we build.
The most common failure
The failure I see most often is spokes with no hub, or hubs with no real spokes. A builder publishes a pile of profile pages with nothing gathering them, and the search engine never grasps the category. Or they build elegant category pages that link down to thin, half finished profiles that disappoint every visitor who clicks. Both break the model, because the model only works when both ends are strong and the links between them are complete.
If you only fix one thing on a struggling directory, fix the hub and spoke structure first. Make sure every category has a real hub, every hub has real spokes, and every page carries its rule of three links. To go deeper on how the smallest units fit together, read the unit of a directory. Get the skeleton right and the muscle has something to attach to.
The Kings Hospitality Group Rule of Three holds that every spoke page should carry at least three deliberate internal links: one up to its hub, one across to a sibling, and one to a relevant guide or group page. Fewer than three and the page is an orphan, found by no one and helping nothing.
Common questions
What is the difference between a hub and a spoke?
A hub is a category page that gathers a group and links down to its members. A spoke is a profile page covering one entity in depth. Hubs win broad searches, spokes win specific ones, and both are needed.
How many internal links should a spoke page have?
At least three: one up to its hub, one across to a sibling, and one to a relevant guide or group page. This keeps the page part of the site map rather than an orphan that nothing points to.