Topical authority · Quick answer
Knowledge guideWhat is a topic cluster?
A short definition, a worked example on a real service-business site, and why search engines treat a cluster better than a pile of unrelated pages.
The answer.
A topic cluster is a pillar page — the comprehensive hub for a topic — plus a set of supporting pages (deep-dives and FAQ-style answers) that link up to the pillar and across to each other. The whole group reads as one authoritative treatment of the subject. The pillar covers the topic broadly; each supporting page goes deep on one slice of it.
The three parts, plainly
Strip the jargon and a cluster has three moving pieces:
- The pillar page. A long, comprehensive page on the core topic — the one you’d send someone who knew nothing about it. It defines terms, frames the decisions, and links out to the detail.
- Supporting pages. Each one takes a single sub-topic — a comparison, a “how much does it cost,” a specific service in a specific area — and answers it properly. These are where most of the long-tail traffic lands.
- The links between them. Every supporting page links up to the pillar; the pillar links down to every supporting page; siblings link across where the topics touch. That’s what turns a list of pages into a structure.
A worked example
Take a home-services company that does water heater work. The cluster might look like this: a “water heater repair” pillar — comprehensive, covers symptoms, repair-vs-replace, brands, what a visit costs. Underneath it: a set of neighbourhood pages (“water heater repair in [neighbourhood]”), each with real local detail; a “tankless vs. tank” deep-dive for the people weighing the upgrade; answer pages for “how much does water heater repair cost” and “how long does a water heater repair take”; and a “signs your water heater is failing” page for the problem-aware searcher who doesn’t yet know they need anyone.
Every one of those is a real query someone types. None of them duplicates another. They all link up to the pillar and across to the obvious neighbours — the cost page links to the tankless deep-dive, the “signs it’s failing” page links to repair and to replacement. Read together, they’re one site that clearly knows water heaters. Read apart, each one answers exactly the question that brought the visitor in.
A blog is a stream of dated posts. A cluster is a deliberate, mostly-permanent structure built around a topic — planned from a map, interlinked on purpose, kept current. Posts can feed a cluster, but “we have a blog” and “we have a topic cluster” are different claims. More on that in content clusters and the pillar model.
Why search engines like it
Three reasons, all of them about clarity:
- One strong topical signal. A tight, interlinked group of pages on a subject is unambiguous about what the site is an authority on — far more so than scattered pages with no relationship to each other.
- No cannibalisation. Because each page owns a distinct query, your pages don’t compete with each other for the same result. One page, one job.
- Every query has a home. Broad question? The pillar answers it. Narrow, specific one? The supporting page does. Nothing falls through the gap, and nothing has to stretch to cover something it shouldn’t.
Where to start
You don’t design a cluster by guessing — you build it from a list of the questions the topic actually generates, organised by where buyers are in their thinking. That list is a topical map, and it’s the first deliverable in the authority sites build. The cluster is just the map, executed: pillar at the centre, a supporting page for each query that earns one, links wiring the whole thing together.
If this was useful: read what to write about next in this cluster — and for the bigger picture, the same depth applied as a programmatic build.
Q2 capacity · 4 builds · 2 slots remaining
What would your cluster look like?
Send us your URL and your main service. We’ll send back a free 5-minute Loom sketching the pillar, the supporting pages, and roughly how many your market actually has.