Search-intent mapping is often treated as a spreadsheet exercise: list a keyword, assign a page, and move to the next row. A useful map does more. It states the user’s job, the business decision, the evidence required, the page that should answer it, and the reason another page should not be created.
Google’s people-first content guidance asks whether content serves an intended audience and provides a satisfying answer. Its link guidance also explains how links help people and crawlers understand a site. Use those principles as quality gates, not as a promise that a particular query will rank.
Start with the decision, not the phrase
For each candidate, write: “The reader wants to decide whether to ___.” Examples include diagnose a falling lead rate, compare two implementation options, choose a provider, or complete a setup. A phrase such as “SEO audit” may hide several jobs; the map should expose them.
Record audience, stage, geography, serviceability, and urgency. If the business cannot serve the audience or cannot support the promised outcome, route the idea to HOLD or a service-page review before writing.
Classify the page job
Use a small intent vocabulary:
| Page job | Reader needs | Typical artifact | |—|—|—| | definition | vocabulary and boundaries | glossary or explainer | | diagnosis | symptoms, causes, evidence | diagnostic tree | | comparison | criteria and tradeoffs | decision matrix | | implementation | sequence, owner, QA | implementation plan | | selection | proof, scope, red flags | provider checklist | | service | fit, scope, proof, next step | service page |
Do not combine jobs just to create a longer article. If one page would need two unrelated opening promises, the map likely contains two intents or one broader hub plus supporting pages.
Collect evidence before choosing a URL
For every intent record existing URLs, published titles, body-level overlap, canonical hints, internal links, source availability, and the practical artifact that would make the answer useful. Search snippets are a signal, not proof of a gap. Review the actual pages and the business’s current offer.
Mark claims as fact, assumption, or question. Add freshness triggers for platform rules, pricing, regulations, product versions, and capacity. A topic with no reliable evidence may remain an idea, but it is not ready for a draft.
Map one primary job to one owner
The map should name an accountable editor, a subject-matter reviewer, a source owner, and a decision owner. For a small team, one person may hold several roles, but the handoff still needs to be explicit.
Set a status such as NEW_URL, UPDATE_EXISTING, MERGE, HOLD, or REJECT. A candidate becomes NEW_URL only when it has a distinct job, a useful artifact, evidence, and no unresolved live overlap.
Check cannibalization before writing
Compare the proposed opening answer, audience, artifact, and next action with nearby pages. Similar words are not always a problem; identical jobs are. If two pages would satisfy the same reader under the same conditions, consolidate or give one a genuinely different boundary.
Write a one-sentence boundary: “This page covers X; it does not cover Y.” If the boundary cannot be written without vague qualifiers, the intent is probably not resolved.
Build the content brief from the map
The brief should include primary question, audience, page job, evidence, practical artifact, internal-link role, source register, expiry trigger, acceptance owner, and publication status. Include the reason the topic survived dedupe and the nearest live semantic neighbor.
Keep indexable: false while the article is under local review. Drafting is not publication approval, and an attractive outline is not evidence that a new URL is warranted.
Sequence a small-team backlog
Prioritize by decision value, evidence strength, standalone intent, and operational capacity. A useful first cohort mixes diagnostic, implementation, comparison, and local or commercial topics so the team can test whether the standard works across archetypes.
Limit work in progress. Finish source review and QA for one cohort before opening several hundred drafts. Repeated overlap or weak evidence is a signal to improve the map, not to generate faster.
Review after publication or update
After an approved change, compare the page’s actual queries, internal-link role, qualified actions, and overlap signals with the map. If the page attracts a different job, update the boundary or route the next content decision. Do not rewrite the map to make an old assumption look correct.
Hold a short monthly mapping review. Retire stale candidates, merge repeated ideas, and record which assumptions changed. The map should become a decision history, not a frozen keyword inventory.
When a candidate is sent to UPDATE_EXISTING, name the exact URL and the evidence that makes an update preferable to a new page. When it is sent to MERGE, record which URL survives and where supporting sections will move. These decisions prevent the backlog from quietly recreating the same intent under a new title.
Review the map with the service owner as well as the SEO owner. A technically distinct query can still lead to the same commercial decision, and a page that cannot be fulfilled should be marked HOLD even when its wording is unique. Keep the route decision beside the evidence.
Implementation verdicts
Ready for brief: intent, audience, evidence, artifact, owner, and boundary are clear.
Update existing: a current page can answer the job with focused repair.
Merge: multiple candidates share the same primary job.
Hold: demand, evidence, serviceability, or ownership is unresolved.
Reject: the topic adds no distinct useful function.
The Search Intent Map is complete when every candidate has a reader decision, page job, evidence status, URL route, boundary, owner, artifact, overlap result, and next review date. The map is successful when it helps the team publish fewer, clearer pages that do more useful work.
How did this article land?
Choose one reaction. You can change it anytime.
