
What keyword mapping is
Keyword mapping is assigning each target keyword (and its close variants) to one specific URL, so every page owns its own query and no two pages compete for the same one. It's the spreadsheet that says "this page targets this term, that page targets that one." The stakes: without a map, you publish overlapping pages that cannibalize each other, split clicks, and confuse Google about which URL to rank, which quietly caps the whole site's performance.
A good map is the difference between a site where every page pulls in one direction and a pile of posts fighting over the same handful of terms. It's the planning document that prevents the mess before it starts, and the diagnostic that untangles it once it has.
A real keyword map (with rows you can copy)
A map isn't a keyword list; it's an assignment. Each row ties a primary keyword, its intent, and its supporting terms to exactly one URL. Here's what a working slice looks like:
| Primary keyword | Intent | Target URL | Secondary terms | Status |
|---|---|---|---|---|
| running shoes for flat feet | Commercial | /best-running-shoes-flat-feet/ | overpronation shoes, arch support runners | Ranks #4 |
| how to fix flat feet | Informational | /guides/flat-feet-treatment/ | flat feet exercises, fallen arches | Ranks #8 |
| flat feet insoles | Commercial | /best-insoles-flat-feet/ | orthotic insoles, arch support inserts | New, unranked |
| are flat feet bad | Informational | /guides/flat-feet-treatment/#risks | flat feet problems, flat feet pain | Section, not new page |
Notice the discipline in that last row. "Are flat feet bad" doesn't get its own page; it's a section on the treatment guide, because spinning up a thin page for it would just cannibalize the guide. That's the whole point of a map: it forces you to decide up front whether a keyword earns a URL or a heading. One URL per intent, secondary terms clustered under it, and everything else consciously folded in.
New page vs. existing page vs. section
The hard call in mapping is whether a keyword deserves its own URL. Use this:
| Keyword characteristic | Decision | Why |
|---|---|---|
| Distinct intent, real search volume, no existing owner | New page | It can rank on its own without stealing from anything |
| Same intent as an existing page, just a variant | Assign to that page | Google already treats them as one query; one URL should own both |
| Subtopic of a broader page's intent | Section / H2 on the existing page | A thin standalone page would cannibalize the parent |
| Two existing pages already target it | Consolidate them | You already have a cannibalization problem to fix |
Get this wrong and you generate the exact content cannibalization the map is supposed to prevent. The map isn't bureaucracy; it's the gate that stops two of your pages from ever chasing the same term in the first place.
How to check it on your own site
- Pull your ranking keywords from Search Console (or your rank tracker) and export them alongside the URL that ranks for each.
- Sort by keyword. Any query where two or more of your URLs appear is a cannibalization flag; highlight it.
- For each target keyword, confirm exactly one URL is the intended owner. If reality (what actually ranks) disagrees with your intent, that's a mapping gap to close.
- Assign each keyword an intent (informational, commercial, transactional, navigational) and make sure the mapped URL's format matches that intent.
- For overlaps, decide per the table above: reassign the variant, demote a subtopic to a section, or consolidate the two competing pages.
- Keep the map as a living document. Every new page proposal gets checked against it before anyone writes a word, so you never publish into an owned query.
Common mistakes and how to fix them
- Mapping keywords, ignoring intent. Two terms with the same intent don't need two pages. Fix: cluster by intent first, then assign one URL per intent, not one URL per keyword string.
- One keyword mapped to several pages "to be safe." That guarantees cannibalization. Fix: every keyword gets exactly one owner URL; supporting pages link to it, they don't compete with it.
- Building the map once and never touching it. New posts drift into owned queries over time. Fix: treat the map as the gatekeeper for every new page, and re-audit rankings against it quarterly.
- Giving every long-tail variant its own thin page. That's how you get a hundred pages splitting the same demand. Fix: fold close variants into the parent page as sections.
- Mapping to a URL whose format fights the intent. Pointing a "buy" keyword at a long essay won't rank. Fix: match the page format (list, tool, guide, product) to the searcher's intent.
FAQ
How does keyword mapping prevent cannibalization?
By enforcing one owner per query. When each keyword is assigned to exactly one URL up front, you never publish a second page targeting a term you already own, which is the root cause of cannibalization. The map is the checkpoint every new page has to clear.
What's the difference between keyword mapping and keyword research?
Research finds the terms worth targeting and their volume and difficulty. Mapping decides which URL owns each of those terms. Research is "what could we rank for"; mapping is "which page is responsible for what." You do research first, then map the results onto your site.
Should every keyword get its own page?
No, and thinking so is how sites end up with hundreds of thin, cannibalizing pages. Only keywords with distinct intent and real demand earn a dedicated URL. Variants and subtopics get folded into an existing page as sections. When in doubt, fewer, stronger pages beat many thin ones.
How do I map keywords for a site that already has overlap?
Audit first. Export your rankings, flag every query where multiple URLs appear, and decide the intended owner for each. Where two pages genuinely compete, consolidate them and 301 the loser. Then lock the intended owners into the map so the problem doesn't regrow.
How often should I update the keyword map?
Treat it as living. Update it every time you plan a new page (to check the target isn't already owned) and re-audit rankings against it at least quarterly, since real-world rankings drift and new cannibalization can creep in even from well-intentioned posts.
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.







