What is a topical map?
A topical map is a plan of everything a website needs to cover to treat one subject completely, organized as a hierarchy and tied to specific pages. It starts with a central topic, breaks it into subtopics and the questions people ask about each, then records which URL answers each question and how those pages link to each other.
For example, a topical map for a home espresso site might look like this in a spreadsheet:
| Section | Subtopic | Question the page answers | URL | Parent page | Status |
|---|---|---|---|---|---|
| Core | Espresso machines | Which type of espresso machine should I buy? | /machines/ | Home | Live |
| Core | Espresso machines | Is a dual boiler worth it? | /machines/dual-boiler/ | /machines/ | Planned |
| Core | Grinders | Do I need a separate grinder for espresso? | /grinders/ | Home | Live |
| Core | Dialing in | Why is my espresso sour? | /dialing-in/sour-espresso/ | /dialing-in/ | Draft |
| Outer | Coffee beans | What roast is best for espresso? | /beans/espresso-roast/ | /beans/ | Planned |
A topical map is a planning document. Google never sees it. What Google sees is the site that results from it.
What is a topical map used for?
A topical map is used to plan complete, non-overlapping coverage of a subject before writing starts. It answers four questions at once: what the site still needs to publish, which page owns each query, how pages should link, and what to work on next.
The most practical benefit is avoiding two common failures. The first is gaps, where obvious questions on the subject have no page. The second is overlap, where two or three pages chase the same query and compete with each other. Both are easy to see in a map and hard to see in a list of published posts.
What should a topical map include?
A topical map should include, for every planned page, the subtopic, the main question or query it answers, its URL, its parent page and its status. Most published guides describe the hierarchy but leave out the columns that make the map usable as a working document.
A useful working map has these columns:
- Section. Core (directly about the central topic) or outer (connected material that supports it). Gübür's framework uses the same core and outer distinction [2].
- Subtopic and question, in the wording searchers use.
- Search intent. Learn, compare, buy or fix.
- URL. One per row. If two rows share a URL, they are one page.
- Parent page and links to, so internal linking is planned, not improvised.
- Status. Planned, draft, live, needs update.
- Last reviewed date, so the map also drives updates.
What is the difference between a topical map and a topic cluster?
A topic cluster is one pillar page plus the cluster pages that link to it, while a topical map is the plan for the whole subject, which usually contains many clusters. HubSpot's 2017 research defined the topic cluster as a pillar page acting as the hub for a broad topic, with related pages linking back to it and to each other [1]. A topical map sits above that: it decides which clusters exist and how they connect.
Search Atlas presents topical maps as the successor to topic clusters [5]. The more accurate description is that a topical map contains clusters. The cluster model still describes how each section links internally.
What is the difference between a topical map, a keyword map and a sitemap?
A topical map plans which subjects and questions a site covers, a keyword map assigns target keywords to existing or planned URLs, and an XML sitemap is a file that lists a site's URLs for search engines to crawl. They are often confused because all three can be spreadsheets of URLs.
| Document | What it records | Who reads it |
|---|---|---|
| Topical map | Subtopics, questions, hierarchy, page ownership, planned links | Your team |
| Keyword map | Target keywords per URL, volumes, rankings | Your team |
| XML sitemap | URLs and last-modified dates | Search engines |
| Content calendar | What gets written, by whom, by when | Your team |
A keyword map is often a column inside a topical map. A content calendar schedules the work a topical map defines. An XML sitemap is a technical file and plays no part in planning.
Where did topical maps come from?
Topical maps grew out of the topic cluster model HubSpot published in May 2017 [1], and the term was popularized in the early 2020s by Koray Tuğberk Gübür, whose semantic SEO case studies treat the topical map as the plan behind topical authority [2] [3].
2017: topic clusters
HubSpot's research report "Topic Clusters: The Next Evolution of SEO," published May 11, 2017, argued that organizing content as linked pillar and cluster pages was a cleaner, more deliberate site architecture for search [1].
2018: Google's Topic Layer
In September 2018, Google added a Topic Layer to its Knowledge Graph to understand subtopics within a topic space and how they relate [6]. It was built to organize results for searchers, but SEOs read it as confirmation that Google models topics as structured hierarchies, which strengthened the case for planning content the same way.
2023 to 2024: semantic SEO topical maps
Gübür's January 2023 guide described expanding a topical map by covering more entities in the same category, more attributes of existing entities, and connecting sections with contextual bridges [2]. His February 2024 case study described sites built from several interconnected topical maps [3].
How do you create a topical map?
To create a topical map, define the central topic, list every subtopic and question, group them into a hierarchy, assign one URL to each, plan the links, and then compare the result with what the site already has:
- Define the central topic and its borders. Decide what the site covers and, just as important, what it does not.
- List subtopics. Use search suggestions, "People also ask" questions, competitor navigation, customer questions and forum threads.
- Write each subtopic as questions. One row per distinct question or intent.
- Merge duplicates. Questions with the same answer belong on the same page.
- Build the hierarchy. Group rows under parent pages, core sections first, outer sections after.
- Assign URLs and links. Every row gets one URL and a parent. Every page should be reachable within a few clicks of the homepage.
- Audit what exists. Mark rows already covered, rows needing an update and rows with no page. The gaps become the plan.
Hallam's guide follows a similar sequence from niche to keyword research to pillar pages and clusters [4]. The step most guides skip is the audit in step 7, which is where existing pages that compete with each other show up.
Do topical maps actually improve rankings?
Topical maps do not improve rankings on their own, because a topical map is a plan and Google only sees the pages and links that come from it. Any ranking gain comes from what the plan produces: pages that answer real questions, fewer gaps, less overlap and clearer internal linking.
Case studies credited to topical maps are reports from practitioners about their own sites, not controlled tests, so they cannot separate the effect of the map from the effect of simply publishing more and better pages. Google's John Mueller has also described "topical authority", the goal most topical maps aim at, as relevance under another name [7]. Search Insider knows of no published controlled study isolating the effect of topical mapping.
When should you build a topical map?
Build a topical map before launching a new site or section, before a large content push, and when an existing site has grown without a plan and pages have started to overlap. Revisit it whenever the subject changes or new questions start appearing in search.
Do not use a topical map as a license to publish hundreds of thin pages to fill every row. A map shows what a complete resource would cover. Rows with nothing useful to say should stay empty, since mass-produced pages made mainly to rank fall under scaled content abuse.