Topical maps — every page your topic actually needs.

Most websites are built from a wishlist. Someone decides the site “should have” a few service pages, an about page, a blog, and maybe a resources section — and that becomes the sitemap. A topical map works the other way around. It starts from the topic itself and asks: what does this subject demand of anyone who claims to cover it? The answer is usually a lot more pages than the wishlist had — and a different set of pages than the ones the owner would have guessed.

What a topical map actually is

A topical map is a structured inventory of every page a topic needs in order to be covered well — organised so you can see the pillars, the clusters under them, and how the whole thing maps onto the way a buyer moves toward a decision. It is not a keyword list. A keyword list is flat and tells you what people type; a topical map is hierarchical and tells you what your site should be. The keyword list feeds the map; it doesn’t replace it.

Think of it as the difference between a pile of bricks and an architect’s drawing. You need the bricks — the queries, the questions, the entities — but the drawing is what tells you they form a house and not a wall with no roof. When a search engine crawls a site that was built from a real topical map, it sees a subject covered from edge to edge with the internal connections to prove the pages belong together. That completeness is the thing that out-ranks a prettier, thinner competitor. (For why the structure matters as much as the page count, see content clusters and the pillar model.)

How you build one — entities, subtopics, queries

The process has four moves, and the order matters.

• Name the entities and subtopics. Start with the core topic — say, “air conditioning” for an HVAC contractor — and list everything that is a real part of it: repair, installation, maintenance, ductwork, refrigerant, thermostats, indoor air quality, sizing, financing, warranties, the equipment brands, the failure modes. These are the subtopics. You’re not writing pages yet; you’re inventorying the territory. A useful test: if a knowledgeable person would expect a comprehensive site on this topic to address it, it goes on the list.
• Derive the queries each subtopic generates. Each subtopic spins off real searches — “how much does AC installation cost,” “why is my AC freezing up,” “what size AC do I need for 1,800 sq ft,” “does homeowners insurance cover AC replacement.” This is where keyword research earns its keep: it tells you which of those queries have demand and which are theoretical. But you generate the candidates from the subtopic first, then validate with the tools — not the other way around. Leading with a keyword tool gives you the queries that happen to have volume and miss the ones that are obviously part of the topic but under-measured. (More on the practical method in how to figure out what pages to write.)
• Group queries into pillars and clusters. Now the hierarchy emerges. A handful of subtopics are big enough and central enough to be pillars — the comprehensive hub pages a buyer or a search engine would expect to land on. The rest become cluster pages that sit under a pillar, go deep on one slice of it, and link back up. “AC repair” might be a pillar; “AC repair vs. replace,” “emergency AC repair,” and “AC repair cost” are cluster pages beneath it. Some queries are FAQ-sized — a single clean answer — and become their own short pages or sections.
• Map it onto the buyer journey. Lay the whole structure against the questions a buyer asks before they’re in the market (educational — “is it worth repairing a 12-year-old AC”), during the decision (comparison and cost — “AC repair near me,” “best AC for Florida humidity”), and after they’ve decided or even after the work is done (“how often should I service my new AC”). Every stage needs pages. A map that’s all bottom-of-funnel service pages reads as a sales site; a map that’s all top-of-funnel reads as a blog with no business behind it. You want the full arc.

How to know it’s “complete enough”

A topical map is never finished in the sense that a building is finished — the topic keeps generating new questions, and you keep adding. But there’s a defensible bar for “complete enough to ship and compete,” and it has two parts.

The first is the buyer test: have you covered the questions a buyer asks before, during, and after the decision? Walk the journey honestly. The person who doesn’t yet know they have a problem; the person comparing two contractors; the person who’s hired you and wants to know what to expect; the person whose system broke again and is deciding whether to call you or replace it. If every one of those people would find a page on your site that speaks to exactly where they are, the map is doing its job. If a stage is thin, that’s the gap to fill next.

The second is the competitor floor. Pull the sites that actually rank for your core terms and inventory what they cover. That’s not your ceiling — it’s your floor. If three competitors all have a “repair vs. replace” page and a financing page and you have neither, you’re not in the conversation. Comprehensive doesn’t mean “more pages than everyone”; it means “no obvious hole a competitor has already filled.” Once you clear the floor on coverage and you’ve passed the buyer test, you have a map worth building. After that, completeness is maintenance — new questions, new services, new locations — which is exactly what a care plan is for.

A topical map isn’t the pages you want to write. It’s the pages the topic was always going to require — you’re just the one who finally listed them.

The mistakes that wreck a topical map

Three failure modes, in roughly the order they’re common.

Mapping to the queries you want instead of the queries that exist. It’s tempting to build the map around the searches you’d love to rank for — high-value, high-intent, “AC installation [your city].” Those belong on the map, but they’re the destination, not the route. Buyers don’t start there. They start with the symptom, the cost question, the “is this normal.” If your map skips the early and middle questions, you’ve built a site that only meets people who are already ready to buy — which is the smallest, most-contested slice of the demand, and the slice your bigger competitors are already buying ads against. The pages that pick up the long tail are the ones that make the high-value page rank in the first place.

Mapping for volume, not intent. A keyword tool will happily hand you a list sorted by search volume, and it’s a trap. A high-volume query with diffuse intent (“air conditioning”) is worth less to a contractor than a low-volume query with a buyer behind it (“AC compressor making loud noise should I turn it off”). Build the map around what the searcher is trying to do, not how many of them are doing it. The intent tells you what the page is for, what it should say, and what the call-to-action should be — three things volume can’t tell you. (This is the same reason more pages isn’t automatically better: a page only belongs on the map if a real searcher with real intent is at the other end of it.)

Never actually finishing the map. The opposite failure: treating the map as a permanent research project. Teams spend months refining the inventory and ship nothing. The map only matters once it’s built into pages. Get it to “clears the competitor floor, passes the buyer test,” draw the line, build it, and then let the live site tell you what’s missing — Search Console will show you the queries you’re nearly ranking for, and those become the next batch. A good map is a living document, but it earns its keep by being built, not by being perfect.

Where to go from here

The map is the blueprint; the cluster structure is how you assemble it, and the internal links are what hold it together. Read content clusters and the pillar model for how the pillars and clusters fit, and internal link architecture for the linking that makes the whole thing legible. If you’d rather hand the mapping and the build to someone who’s done it 100 times, that’s the authority sites service — the map is the first deliverable, and you sign off on it before a page gets written. Or send your URL through the topical authority overview’s free audit and we’ll show you the holes in your current coverage in five minutes.