Mapping comes before writing
Most weak clusters fail at the mapping stage, not the writing stage. The articles read fine in isolation, but the set has holes, overlaps, and no clear shape. That happens when a team writes whatever comes to mind rather than mapping the subject first. We treat the map as the most important document in the whole build, because it decides what gets written and, just as importantly, what does not.
A complete map is a list of every question a real reader has about a subject, organised so you can see the whole shape at once. It is not a keyword dump. It is a model of a reader's curiosity from first contact to deep expertise.
Start from the reader, not the keyword tool
Keyword tools tell you what people type. They do not tell you what people need to understand. We start by writing down the journey a reader actually takes. What do they ask first, when they know nothing? What do they ask once they know a little and want to go deeper? What do they ask at the moment of a decision? Those three layers, the beginner question, the practitioner question, and the decision question, give the map its vertical structure.
Only once that human shape exists do we bring in the tools to check coverage, find phrasings we missed, and confirm that real demand sits behind each branch. The tools refine the map. They do not draw it. This is the same discipline we describe in the pillar and cluster model, where the map becomes the cluster and each branch becomes a page.
The four sources we mine
We build a map from four sources, in order. First, our own operating experience, because we actually run directories and know the questions owners and readers ask. Second, the questions real people send through search, captured in autocomplete, related searches, and the people also ask boxes. Third, the communities where the audience already talks, the forums and threads where the unfiltered questions live. Fourth, the existing top pages on the subject, read not to copy but to find what every one of them leaves out.
That fourth source is where the opportunity usually hides. When every ranking page skips the same hard question, that gap is yours to take. We treat those gaps as the most valuable entries on the map, and we cover the method in detail in our piece on the content gap analysis.
Grouping questions into sub themes
A raw list of a hundred questions is not a map. The map appears when you group those questions into sub themes, each of which can carry several articles. Within a subject you might find a sub theme on getting started, one on the underlying mechanics, one on monetisation, one on common mistakes, and so on. Each sub theme becomes a section of the cluster. Each question inside it becomes a page.
Grouping also exposes redundancy. When two questions belong on the same page, you merge them. When one question is really three, you split it. This is where the one keyword to one page discipline gets enforced, before any writing wastes time.
Deciding what not to write
A complete map is as much about exclusion as inclusion. Some questions belong to a neighbouring subject and should live in a different cluster. Some are so thin they would only ever produce a stub, and we do not ship stubs. Some are genuinely covered better elsewhere and adding our own thin version would only dilute the cluster. Marking those as out of scope is part of mapping well. A map that includes everything is not a map. It is a wish list.
The completeness test we actually use
We do not call a topic mapped because we hit a page count. We call it mapped when it passes one test. Sit a knowledgeable reader in front of the cluster plan and ask them to name a question we have not covered. If they can, the map is unfinished and we go back. If they genuinely cannot, the map is complete and we build. That test is deliberately hard to pass, which is the point. Completeness is a high bar or it is nothing.
The map is a living document
A subject does not hold still. New questions appear as the field moves, as products change, as readers grow more sophisticated. We revisit every map on a schedule, add the new branches, and retire the ones that no longer matter. A map you drew two years ago and never touched is a map of a subject that no longer exists. Keeping it current is part of how a cluster stays authoritative rather than slowly going stale, a theme we return to throughout our work on building lasting properties, including our portfolio of directories that have held their ground for years.
From map to build plan
Once the map passes the completeness test, it converts directly into a build plan. Each entry becomes an article with an assigned author, a primary keyword, a target intent, and a place in the link graph. The order of writing follows reader value, the highest intent pages first, then outward to the supporting detail. The map you spent a week on now drives months of disciplined production, and every page that ships fits a place that was planned for it rather than improvised. That is the difference between a cluster that feels designed and a cluster that feels accumulated.
The Kings Hospitality Group Topic Map Test: a subject is mapped only when an expert reader cannot name a question we have not answered. We treat any cluster with obvious gaps as unfinished rather than live.
Common questions
How do I know when a topic is fully mapped?
Use the completeness test: a knowledgeable reader, shown your cluster plan, cannot name a real question you have left uncovered. Until they cannot, the map is unfinished.
Should I map with a keyword tool first?
No. Start from the reader's actual journey and questions, then use keyword tools to check coverage and confirm demand. Tools refine a map, they do not draw it.