How to build a topical map from a list of keywords
A working method for grouping topics into pillar and spoke pages, naming each page's job, and keeping the map from competing with itself.
What a topical map is
A topical map is a plan of the pages a site needs to cover a subject properly, and how those pages relate. It names each page, says what question it answers, and shows which page is the main one for a theme.
More
The idea is simple. A reader who lands on one page should be able to move to the next question without leaving your site. A search engine, in turn, has a clearer picture of what the site is about when pages on a subject are connected on purpose.
Steps 1 and 2: gather topics, then group by intent
Start with a flat list. Sources can be your product's features and problems, autocomplete suggestions, questions your support team gets, competitor sitemaps, and queries from Search Console if you have them. Do not sort yet.
More
- One topic per line, written as the phrase a person would type.
- Keep the source next to each line so you can judge it later.
- Remove exact duplicates and anything unrelated to what you sell.
Group topics that belong to the same subject. Then label each topic with its search intent: someone learning, someone comparing, or someone ready to act. Topics with different intent usually need different pages, even if the words are similar.
| Intent | Typical phrasing | Page type |
|---|---|---|
| Informational | how to, what is, why | Guide or explainer |
| Commercial | best, vs, alternatives, review | Comparison or roundup |
| Transactional | pricing, demo, trial | Product or pricing page |
| Navigational | brand name plus a feature | Product or docs page |
If two phrases return the same kind of results and mean the same thing, they belong on one page. If they return different kinds of results, split them.
Step 3: choose a pillar and its spokes
In each group, pick one broad topic as the pillar. The pillar covers the subject at overview level and links to narrower pages, the spokes. Each spoke answers one specific question in depth and links back to the pillar.
More
- Choose the broadest phrase in the group as the pillar.
- List the narrower questions as spokes.
- Write one sentence for each page that says what it answers and what it does not.
- Check that no two pages answer the same question.
- Decide the links: each spoke to the pillar, the pillar to each spoke, and neighbouring spokes where the reader would naturally go next.
Keep groups small. A pillar with three to eight spokes is easier to finish and maintain than one with thirty.
Step 4: check for overlap and gaps
Compare the map with pages you already have. Where an existing page answers a planned topic, mark it as 'exists' and plan a refresh rather than a new page. Two pages chasing the same question is keyword cannibalization, and it is the most common fault in maps built from long lists.
More
Then look at a competitor's public sitemap and ask which of their topics you do not cover. Treat that as a source of ideas, not an instruction. Some of their pages will be irrelevant to your product.
A small worked example
Suppose a site sells scheduling software for clinics. After gathering topics you have a flat list. Grouped, it might look like this.
More
| Cluster | Pillar | Spokes |
|---|---|---|
| Appointment reminders | Appointment reminders for clinics | SMS or email reminders, reducing missed appointments, reminder wording examples |
| Switching tools | Clinic scheduling software alternatives | Comparison with a named rival, migration checklist, what to export first |
Each spoke has a different job. The wording-examples page is informational, the comparison page is commercial, and the migration checklist serves someone who has already decided. They link to their pillar, and the pillar links out to all of them.
Linking rules and keeping the map useful
A map that is never updated turns into a document nobody trusts. Change it whenever the plan changes, and record why a topic was dropped.
More
- When a new topic appears, place it in an existing cluster before creating a new one.
- When a spoke grows long, consider splitting it into two pages with separate questions.
- When two pages start ranking for the same query in Search Console, merge them or sharpen the difference.
- When a product feature changes, review the spokes that mention it.
Links are where a map becomes visible to readers. Use descriptive link text that says what the destination answers, and place the link where the reader would naturally want the next step, not in a block at the bottom.
- Every spoke links to its pillar near the top, so a reader can step back to the overview.
- The pillar summarises each spoke in a sentence before linking to it.
- Do not link every page to every other page. A few relevant links are more useful than a wall of them.
- If a page has no inbound links from the map, it is an orphan and either needs a place or should be removed.
Where BlogFactory fits
BlogFactory's Topical map panel groups the topics on your plan into clusters. The grouping is computed each time you open it, using the shortest term in a cluster as the pillar. Nothing extra is stored, so the map follows the plan as it changes. Topics that overlap content the site already has are flagged during discovery, and a competitor's public sitemap can be read to list topics you do not cover.
More
- Needs: planned topics on the site. The competitor gap needs a public sitemap and no key.
- Cannot do: judge intent perfectly or choose the best pillar for you. The shortest-term rule is a heuristic, so rename or reassign by hand.
- Cannot do: write the internal links for you in the article text. A person reviews every draft, and agents never publish live.
Try it in BlogFactory
Questions
How many pages should a topical map have?
As many as you can finish and keep accurate. A small, complete cluster is more useful than a large map of half-written pages.
Do I need a pillar page for every cluster?
It helps, because it gives readers and crawlers a clear main page. If one page already serves that role, mark it as the pillar and link the spokes to it.
Can one keyword sit in two clusters?
Avoid it. Assign each topic to one page. If it genuinely fits two, the clusters probably overlap and should be merged.
How often should I revise the map?
Revisit it when you publish a batch or when Search Console shows pages ranking for queries you did not plan for.
Is a topical map the same as a content calendar?
No. The map says what should exist and how it connects. The calendar says when each page is written. You can build the calendar from the map.
Plan it, draft it, approve it.
BlogFactory does the research and drafting steps in this guide. You approve every draft, and nothing publishes itself.