How hub and spoke works
One page takes the broad subject: the hub. Around it sit narrower pages, each answering a single specific question in depth: the spokes. Every spoke links up to the hub using anchor text that describes it, the hub links down to each spoke, and spokes link sideways to each other wherever a reader would genuinely follow the connection.
The value comes from the links as much as from the pages. A tight group of pages linking to each other tells search engines that these URLs belong together and that the hub is the entry point for the subject. It also gives readers a route: land on a narrow question, discover the overview, and find the questions they had not thought to ask yet.
Why hub and spoke matters
It solves a problem every growing site meets. A single page cannot cover a broad subject well without becoming unreadable, but breaking it into separate articles leaves them scattered and competing. The structure lets each page hold one job while the group covers the whole subject, which is how topical authority is built in practice rather than in theory.
It makes planning easier too. Once the hub exists, gaps become obvious: a spoke that ought to exist and does not shows up as a missing link. And because each spoke has a defined question, briefs almost write themselves and two writers cannot accidentally produce the same article.
Where hub and spoke goes wrong
The commonest failure is a hub that duplicates its spokes. If the hub explains every subtopic fully, it competes with the pages beneath it and search engines are left choosing between your own URLs. A hub should orient, summarise and hand off.
Another is spokes split for the sake of the diagram. Three pages saying nearly the same thing, created because the structure had three boxes, are just thin pages in a tidy arrangement. A spoke needs its own question, its own search demand and enough substance to stand alone. The last failure is linking in one direction only, usually hub to spokes, which leaves the hub receiving none of the support that would make it rank.
How to act on it
Start from questions rather than boxes. List what people actually ask about the subject, group the questions that share an intent, and let the natural groups become spokes. Where a group holds only one thin question, fold it into the hub instead of forcing a page into existence.
Build the hub so it works as a page in its own right, not only as a directory: it should answer the broad question for someone who reads nothing else. Then wire the links deliberately, using anchor text that names the destination, and check the result after publishing by looking at which pages actually receive internal links, rather than assuming your plan survived the CMS.
