A content hub is a cluster of pages on one topic, tied together by internal links. The linking is what does the work.
A content hub is a set of pages that cover one topic in depth, organised around a central page that links to every piece and is linked back to from each one. The hub targets the broad term. The spokes target the specific questions underneath it. The internal linking is what makes it a hub rather than a folder of vaguely related posts.
Why the structure earns rankings
Three effects stack up. Internal links pass authority from the pages that earn it to the pages that need it, so one spoke picking up coverage lifts the whole cluster. Clear topical grouping helps Google understand what your site is actually about, which matters more now that quality systems judge sites, not just pages. And the hub page can compete for a broad head term that no single article would ever win.
Hub and spoke in practice.
Say you sell commercial coffee machines. The hub covers choosing one, end to end. The spokes cover bean-to-cup vs traditional, water filtration requirements, servicing intervals, lease vs purchase and what output you need for 200 covers a day. Each spoke links up to the hub. The hub links down to each spoke inside the copy, where the link is relevant, not as a list of related posts in a sidebar.
The test for whether a spoke belongs is simple. Would somebody researching the hub topic plausibly search for this? If not, it sits in a different cluster or nowhere.
Common ways hubs fail
- Spokes that overlap. Two pages chasing the same query split the signals and neither one ranks. Map the queries before anybody writes.
- A hub page that is only a menu. If it lists links and says nothing itself, it will not rank for the head term and you have wasted the strongest URL in the cluster.
- Links running one way. Hub to spoke with no route back, or links buried in a footer widget rather than placed in the copy.
- Publishing one piece a quarter. A cluster works once it is complete. Half a hub performs as scattered posts because that is what it is.
How to plan one
Start with the query set, not the article titles. Pull everything people search around the topic, group it by intent and drop anything that duplicates a page you already have. You will usually find existing posts that should become spokes with a rewrite and a few links, which is far cheaper than starting from scratch.
Settle the URL structure before you publish anything. Nested under the hub path or flat both work fine, but changing your mind later means redirects. We map hubs at the start of an engagement as part of our /seo-agency/, because retrofitting structure onto 60 existing posts is the slowest job in the calendar.
Common questions
How many pages does a content hub need?
Enough to cover the topic properly, which usually lands between six and fifteen spokes. Fewer than five and it behaves like a set of unconnected posts. More than twenty and you probably have two topics, each deserving its own hub.
Should the hub be a blog post or a landing page?
Whichever fits the intent behind the head term. Check what already ranks. If the results are guides, write a guide. If they are commercial pages, build a landing page with the depth of a guide.
Do content hubs help with AI search?
They do. Covering a topic thoroughly with clear internal structure makes it easier for a model to find the specific passage that answers a question and being consistently associated with a topic across many pages strengthens that link.
Can I build a hub from posts I already have?
Usually yes and it is the fastest route to results. Audit what exists, merge the overlapping posts, fill the gaps with new pieces, write a proper hub page and link it together. Most sites already have half a hub sitting there unorganised.
See our glossary entry for content hub.
