Key takeaways
- A keyword map answers one question: which single page owns which query. Nothing else in content strategy matters until that is decided.
- A topic cluster answers a different question: which pages support which other pages. It is about internal structure rather than about query ownership.
- They are not alternatives. A map without clusters produces orphaned pages; clusters without a map produce pages competing for the same query.
- The failure a map prevents is cannibalisation, where two of your own pages contest one term and both underperform. It is extremely common and invisible without a map.
- The failure clusters prevent is orphaning. Before we built our own cluster map, 26 of 71 posts on this site had no inbound internal link at all.
- Start with the map because it is cheaper and the decisions are forced. You cannot build clusters sensibly until you know what each page is for.
Search content strategy has two vocabularies for overlapping ideas, and the industry argues about which is correct. Keyword mapping sounds mechanical and dated; topic clusters sound modern and strategic.
They answer different questions and you need both answers. One decides what a page is for; the other decides what links to it.
What follows is what each actually is, the specific failure each prevents, and the order to do them in.
What is keyword mapping?
Short answer: Assigning each query you want to rank for to exactly one page, and recording that assignment. It is a spreadsheet rather than a methodology, and its value is that it forces a decision nobody makes otherwise: which single page owns this term.
The output is unglamorous. One row per query, one column for the page that owns it, one for whether that page actually exists yet.
The value appears when two queries want the same page or one query has two candidate pages. Both situations are decisions, and without a map they get made by accident.
| Column | Why it is there |
|---|---|
| Query | The phrase as people actually type it |
| Owning page | Exactly one URL, which is the whole point |
| Exists yet | Turns the map into a content backlog |
| Current position | From Search Console, so priority is evidence-led |
| Current impressions | Distinguishes no demand from no ranking |
The last two columns are what turn a map from a plan into a diagnosis. A query with impressions and no position is a different problem from one with neither.
What do topic clusters do that a map does not?
Short answer: They decide what links to what. A map tells you a page exists and what it is for; a cluster tells you which other pages should argue for it, which is how a page accumulates internal authority rather than sitting in isolation.
The structure is a hub page covering a subject broadly, with supporting pages covering parts of it in depth, all linking to the hub and to each other.
The mechanism is unexciting and reliable. A page with eight internal links pointing at it from topically related pages is treated differently from one with none.
We can be specific about the problem it solves, because we had it. Before this site had a cluster map, 26 of its 71 posts had no inbound internal link at all, and four of its eleven pillar articles had zero.
Our cluster map is a data file rather than a document, and the link block it generates is baked into each article HTML rather than rendered by a component.
A component-rendered link block is invisible to anything that does not run JavaScript, which is most of what we care about reaching.
Is the topics versus keywords argument real?
Short answer: Mostly not. The genuine shift is that a page should answer a subject thoroughly rather than target a phrase repetitively, which nobody serious disputes. The framing as a choice between two strategies is a positioning device rather than a methodological disagreement.
What the topics framing gets right is that queries are not the unit of user intent. Many phrasings share one intent, and one page should answer all of them.
What the keywords framing gets right is that you still have to decide which page that is. Topics do not assign themselves to URLs.
So the argument resolves into sequence rather than choice. Group queries by intent, assign each group to one page, then structure the pages into clusters.
What is cannibalisation and how does a map stop it?
Short answer: Two of your own pages competing for the same query, so neither one accumulates the signals it needs and both of them underperform. A map stops it by making the collision visible at planning time, rather than six months after both pages have published.
The symptom in your own data is a query where your appearing URL changes between weeks. That instability is the engine choosing differently each time because neither page is clearly the answer.
We have shipped this defect ourselves and it is instructive. Adding a dedicated business-to-business SEO page left it and our main SEO service page both titled for the same term, which is two of our own pages contesting one query.
The fix was retargeting one of them, and the durable fix was a test that fails if any two service page titles open with the same two words. A map is the planning-time version of that test.
Which should you build first?
Short answer: The map, because it is cheaper and because clusters depend on it. You cannot sensibly decide which pages support a hub until you know what each page is for, and the map is where that gets decided one row at a time.
- Export your queries from Search Console, with impressions and average position. This is free and it is better starting data than any keyword tool.
- Group them by intent rather than by wording. Several phrasings of one question belong in one group.
- Assign each group to exactly one page. Where two pages compete, decide now which one wins and what the other becomes.
- Mark the groups with no page. That list is your content backlog, prioritised by the impressions column.
- Only then build clusters, by deciding which pages are hubs and which support them.
Step three is the step with the real work in it, because it requires deciding to deprioritise a page somebody wrote. That is why it gets skipped.
Frequently asked questions
How many keywords should one page target?
One intent, which usually covers many phrasings. A page can reasonably own dozens of query variations that mean the same thing; it cannot own two different intents without being a worse answer to both.
Do I need a tool to build a keyword map?
No. A spreadsheet and a Search Console export will do it, and the export is better input than a keyword tool because it reflects queries you actually appeared for rather than estimates.
How big should a topic cluster be?
Big enough that the hub receives meaningfully more internal links than its spokes, which in practice means at least four or five supporting pages. A hub with one spoke is a page with one extra link.
Can one page be in two clusters?
It makes the structure harder to reason about and it dilutes the signal, so we keep each page in exactly one cluster and link across clusters at the hub level instead. Our own cluster test fails if a page appears twice.
How do I fix two pages that already compete?
Decide which owns the query, then either narrow the other to a different intent or consolidate it into the winner with a redirect. Google documentation on canonical URLs covers the consolidation case.
Sources and further reading
- Google Search Central, creating helpful, reliable, people-first content
- Google Search Central, how to specify a canonical URL
- Google Search Central, getting started with Search Console
- Google Search Central, AI features and your website
- Google Search Central, how to control your snippets in search results
Want your own collisions found?
Send us your Search Console export. We will tell you which queries have two of your pages contesting them, which is the cheapest content problem to fix and the hardest to see without a map.