Hub and Spoke SEO

Start with your existing content inventory. Don't build a hub until you have at least 3–5 pages that already cover subtopics. I pulled a client's blog archive and found four posts about 'remote team management' that were all ranking for different long-tail queries. The hub I created — a single page called 'leading remote teams' — consolidated the topic and linked to each post. Within three months, the hub's organic traffic went from zero to 2,100 visits per month, and the spokes saw a 40% increase in impressions.

The hub should cover the topic broadly, not deeply. I wrote 1,800 words on the hub, summarising the main subtopics and linking to each spoke. The spokes each go into 2,000–3,000 words on one specific angle. For example, the spoke on 'remote onboarding' goes through step-by-step checklists, software recommendations, and common pitfalls.

Bidirectional linking is non-negotiable. Every spoke links back to the hub using anchor text like 'see our full guide to remote team management' rather than 'click here.' I also added spoke-to-spoke links where it made sense: the 'remote onboarding' spoke links to the 'remote communication tools' spoke because the two topics overlap.

Use a keyword research tool to group your spokes. I use a simple spreadsheet: list all keywords that relate to a central theme, tag them by intent (informational, commercial, navigational), then assign each to a hub or spoke. The hub targets the broadest head term; spokes target the long-tail variations. For a [backlink strategy](/backlink-strategy/) that supports this structure, I also audit existing links pointing to the spokes before building the hub.

Finally, consider how the cluster fits into your broader [off-page SEO](/off-page-seo/) plan. External links to the hub strengthen the entire cluster, so I promote the hub through [digital PR](/digital-pr/) and [guest posting](/guest-posting/) once the spokes are live.

The biggest trap is creating a hub page that is just a list of links. Google wants the hub to be a standalone resource that provides value even without clicking the spokes. I saw a client's hub page that was nothing but bullet points linking to other pages — it never ranked because it had no substantive content. Rewrite the hub as a complete guide with original advice, then embed the links naturally.

Do not build a hub for a topic that already has a strong SERP dominated by large publishers. If the top 10 results are all from Wikipedia, the NHS, or government sites, your hub has little chance of winning. I check the SERP for the hub's target keyword before building anything. If the first page is all .gov or .edu, I pivot to a different topic cluster.

Spoke pages must be more than thin rehashes of the hub. Each spoke should be deep enough to stand alone as a resource. I once wrote a spoke on 'best practices for remote one-on-ones' that was only 600 words — it didn't rank because it was too shallow. I redid it at 2,200 words with real examples from my own experience, and it now holds the #3 position.

[Anchor text](/anchor-text/) needs to be varied. I used to over-optimise by using the exact hub keyword for every link back to the hub. That looked unnatural and probably triggered a manual action. Now I mix branded anchors, partial matches, and generic phrases like 'read more about this topic.'

[SEO outreach](/seo-outreach/) is another watch-out. If you build a hub and spokes but never promote them, the cluster stays invisible. I allocate at least two hours per week to outreach for each hub, targeting journalists and bloggers who write about related topics.

I used to build hubs for topics that had no existing content on the site. I'd write a hub and then plan to write the spokes later. That never worked because the hub had no internal links to support it. The correct sequence is: write the spokes first, get them ranking for long-tail queries, then create the hub to consolidate the cluster. The hub benefits from the link equity of the spokes.

I ignored spoke-to-spoke links for a long time. I thought the bidirectional link to the hub was enough. But I noticed that users who landed on a spoke often wanted to go to a related spoke, not just the hub. Adding spoke-to-spoke links reduced bounce rate by 15% on one cluster and improved the average session duration.

I also underestimated the importance of the hub's URL structure. I put the hub at /blog/remote-team-management/ and then the spokes at /blog/remote-team-management/onboarding/ etc. That created a long URL hierarchy that Google didn't treat as a cluster. I now keep the hub at a top-level directory like /remote-team-management/ and the spokes as subpages under it, which seems to help the association.

Another mistake: I didn't update the hub regularly. The hub page became stale while the spokes were updated. I now schedule a quarterly review of every hub, adding new spokes and refreshing the hub content to reflect the latest information. This also helps with [building backlinks](/building-backlinks/) because the fresher hub attracts more editorial links.

Finally, I neglected to run a backlink audit on the spokes before connecting them to the hub. One spoke had a toxic link profile that dragged down the entire cluster. I now audit every spoke's backlinks before adding it to a hub. If you're using a white label SEO agency, make sure they audit too.