It’s not a
content calendar.
A topic cluster is not like a calendar organized by theme.
This is the most common misunderstanding about the model. It produces content programs that look like topic clusters but function like random publishing schedules.
A topic cluster is a deliberate architecture.
one authoritative pillar page that establishes your claim to a topic, supported by spoke pages that go deep on specific subtopics, all connected through intentional internal links that tell Mama Google this content belongs together and Look no further because I am the authoritative source on this domain.
Content without architecture is just content. The architecture is the point. Here is how to build one from scratch.
Step One:
Choose the Pillar Topic
Mindfully, Correctly
The pillar topic is the broad subject you are claiming authority on. It needs to be:
1: Broad enough to support multiple subtopics. “Content strategy” is a pillar topic. “Content strategy for B2B SaaS companies with under fifty employees” is a spoke.
2: But Specific enough you have a real claim to authority. “Marketing” is not a pillar topic — it is a category. “Content strategy” is a topic you can own if you try.
3: Aligned with what you actually do.
The most durable topic clusters are built around genuine expertise, not keyword opportunities. I want to be clear on this one because everyone who is not us doesn’t understand this:
If you wouldn’t be comfortable being interviewed by a journalist as an authority on this topic, do not cluster around it.
The pillar page is the most comprehensive piece of content on the subject that you will produce. It should answer the core question — what is this, why does it matter, what does it involve — and link out to spoke pages for depth on each subtopic.
Step Two:
Map Your Spokes
Spoke pages are the subtopics that constitute the actual expertise in that pillar domain.
what does someone need to understand to truly understand this topic?
For a content strategy cluster, the spokes might include content audits, content briefs, editorial calendars, brand voice, content measurement, topic clusters (so meta), content distribution.
Each spoke should be:
A specific, answerable question. “Content audits” isn’t a spoke, “how to do a content audit” is: a specific query with a specific answer.
Meaningfully distinct from your others. Spokes that overlap mean cannibalization. “How to write a content brief” and “what goes in a content brief” are the same spoke.
Sized correctly. A spoke topic that requires ten thousand words is actually a pillar in its own right. A spoke topic that requires two hundred words is a FAQ answer, not a page.
A healthy cluster has between 5-15 spokes. Fewer and the cluster lacks depth, which misses the whole point. More, and you are almost certainly a cannibal.
Step Three:
Sequence Production
In a Conscious Way
This is where most topic cluster strategies go wrong.
They identify the cluster and then publish everything at once, or publish randomly, and then wonder why the cluster is not performing.
Sequence matters because Google’s topical authority model works by accumulation. Each new piece of relevant content on a topic strengthens the cluster. But the pillar page needs to exist before the spokes point to it.
You can’t build a hub before you have a hub, in other words.
The production sequence:
- Pillar page first. Comprehensive, well-structured, containing internal links to spokes that do not yet exist (you will update these links as they publish).
- Two or three spoke pages covering the highest-volume, most-searched subtopics. These establish the initial cluster signal.
- Remaining spokes over time, in order of search opportunity and relevance.
Do not wait until the full cluster is built to publish. Publish and build. The cluster strengthens with each addition.
Step Four:
Build the Link
Architecture
Every spoke page links back to the pillar, obviously, and the pillar links out to every spoke. (This is two moves, to be clear: Linking out and linking in.)
Less obvious, or so it would seem: Every spoke page links to at least one or two related spoke pages, but really every relevant existing page, at the moment of its relevance. (Not in a sidebar, not in a “related posts’ block. You are not getting off that easy. A contextual link is a stronger signal than a structural one, so that’s what we use.)
This is the architecture that makes this a cluster, rather than just some related posts. The links are the semantic signals telling Mama Google these pages belong together, but also that the pillar is the authority and the spokes are the depth.
Update the pillar every time a new spoke publishes. Add the contextual links, update the date, and yes: submit the pillar URL to GSC for reindexing. It’s a freshness signal on the authoritative page that reinforces the entire cluster’s performance across the board.
What a
Working Cluster
Looks Like
A properly working topic cluster produces a measurable increase in rankings across the cluster over 3-6 months.
Note: It’s not just the pillar that benefits — spokes too. The topical authority built by the cluster benefits every page in it, which is why they are a big deal.
You will also begin to see your pillar page in featured snippets and AI Overviews for cluster-adjacent queries it’s not even y targeting. This is the topical authority signal working as intended — Mama Google has decided your site is authoritative on this topic and is surfacing your content across the query space.
This is the end goal.
One cluster, built correctly, produces more durable organic performance than fifty isolated posts. Which is a big number for something we work pretty hard on, which tells us we should take this seriously.
I write about content strategy, editorial leadership, and the infrastructure that makes search performance possible.
For inquiries: jacob@cliftoncreative.agency · cal.com/cliftoncreative