How to build a topic cluster that actually ranks

A topic cluster is one broad pillar page and a group of narrower posts that all link back to it. Build one well and your pages stop fighting each other for the same spot and start ranking as a set. This is how you take a pile of related posts and turn it into coverage a search engine reads as real depth on a subject.

What a topic cluster actually is

The model is simple. A pillar page covers a wide subject at a high level. Cluster pages sit around it, each answering one specific question or use case. Every cluster page links up to the pillar, and the pillar links back down to each of them.

HubSpot named this the pillar-cluster model in 2017, after an internal experiment showed that adding links between related posts lifted rankings across the whole group. In their own reporting they saw steady month-over-month growth in the number of keywords landing on page one of Google. The idea underneath is older than the label: search engines have always rewarded sites that cover a subject in depth and connect that coverage cleanly.

Pick a pillar topic you can own

Start with a subject broad enough to support eight to fifteen posts, and narrow enough that you can say something real about each one. "Marketing" is too wide. "Email deliverability for B2B SaaS" is a topic you can own.

A quick test: can you list ten questions a buyer asks about it without straining? If you run dry at three, the topic is too small to be a pillar. If you could write fifty, it's really two clusters, so split it.

Map the cluster before you write a word

List every question, comparison, and how-to inside the topic. Each one with its own search intent becomes its own cluster page. Group anything that overlaps.

This is the step that keeps your pages from competing against each other for the same query, which is what happens when three posts all chase "email deliverability" instead of one owning it and the rest owning the long tail. One page, one intent. One strong page beats ten thin ones, and a mapped cluster is how you decide which page gets which job.

Write the pillar, then the spokes

The pillar is the overview. It introduces the whole subject, defines the terms, and links out to every cluster page for the detail. Keep it scannable, with a clear heading for each subtopic.

The cluster pages go deep on one thing each. A page about SPF records doesn't re-explain the whole of deliverability. It answers the SPF question, then links back to the pillar for readers who want the wider picture. Brief each page on the single query it owns, so writers don't drift into the pillar's territory and write the same post twice.

Wire the links both ways

The links are the cluster. Without them you have a folder of posts. Every cluster page links up to the pillar at least once, usually on the first mention of the broad topic. The pillar links down to each cluster page. When two cluster pages touch the same idea, link them to each other.

Use anchor text that says what the reader will get, never "read more" or "click here". HubSpot's rough guide is about one internal link per 150 words of body copy, which keeps the linking natural instead of stuffed.

Where most clusters stall

Two failures are common. The first is a pillar that's really a long list of links with no substance of its own. Readers bounce off it and Google treats it as thin, so give the pillar real content between the links. The second is writing all the cluster pages and forgetting to link them back up, so the structure lives on your sitemap but not in the HTML. Ship the links with the posts, not as a cleanup task for later that never comes.

Planning a cluster is mostly deciding which page owns which query, and that's the part teams get wrong. If you want help mapping one for your topic, that's the kind of work we do.