Topic clusters are the difference between a blog and a body of work. A blog is a reverse-chronological pile of posts that happen to share a domain. A cluster is a structure: one hub page that covers a topic broadly, surrounded by spoke pages that each answer one specific question, all connected by internal links that make the relationship explicit.
The model is not new, and it keeps working because it lines up with how search engines evaluate sites and how people actually search. This guide explains the structure, the reasons it works, and a practical way to build your first cluster.
What topic clusters are
Three parts, each with a distinct job:
- The hub: one substantial page targeting the broad head term, covering every major subtopic at overview depth
- The spokes: separate pages, each targeting one narrower question or long-tail keyword at full depth
- The links: every spoke links up to the hub, and the hub links down to every spoke where the subtopic appears
Why the structure works
First, coverage. A single page cannot answer a broad topic at depth, and a pile of disconnected posts does not read as expertise. A cluster shows a search engine, and a human, that you have treated a topic thoroughly: the overview exists, and so does the detail behind every part of it.
Second, internal links carry meaning. When ten related pages point at a hub with descriptive anchor text, they make it clear what that page is about and that it is the most important page on the subject you own. Links a spoke earns from elsewhere benefit the neighborhood it is connected to, not just the spoke itself.
Third, clusters prevent your own pages from fighting each other. When each keyword belongs to exactly one page, you stop publishing three near-identical posts that split clicks and confuse the results. The map itself enforces the discipline.
How to plan your first cluster
Pick a topic close to your product, broad enough to have real subtopics but narrow enough that you could plausibly become a reference on it. Then do keyword research to list the spokes: the questions, comparisons, and how-tos people search within the topic. Each spoke should map to one query with one clear intent. Ten to fifteen spokes is a healthy first cluster; three is a hub with a rounding error.
Build in whichever order keeps you shipping. Writing a few spokes first gives the hub something real to link to on day one. Writing the hub first gives every future spoke a home. What matters is that the cluster exists on the site, in links, and not only in a spreadsheet.
Internal linking rules that make it real
The links are the cluster. Skip them and you just have posts with a theme. Follow four rules:
- Every spoke links to the hub with anchor text that names the hub topic, not 'click here'
- The hub links to every spoke at the point where its subtopic comes up
- Spokes link sideways to sibling spokes only when a reader would genuinely want the jump
- One page per keyword: if two pages target the same query, merge them and redirect
Common mistakes and how to tell it is working
The usual failures: a hub that is just a table of contents with no substance of its own, spokes that restate the hub instead of going deeper, and starting five clusters at once so none of them ever gets finished. One completed cluster beats five skeletons.
To measure it, watch rankings for the head term and the spoke queries together, and watch Search Console for the queries each page collects over time. Movement tends to be gradual, which is why keeping the loop in one place helps. In Creaiter, the chat that mapped the cluster can also track those rankings and draft the next spoke, so the structure keeps growing instead of stalling after launch. Either way, judge the cluster as a unit: the hub and its spokes rise together or not at all.
Keep reading