Search and Organic Discovery

Search Intent Content Map

Map a search query cluster to distinct reader jobs, page types, current coverage, evidence needs, journey stages, and meaningful content gaps.

Free editable Markdown · SEO strategists, content architects, and editors · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Query cluster

Cluster name: [Neutral reader-job label]
Query examples: [Representative phrases]
Data source and period: [Search Console, research tool, support log; dates]
Market, language, device: [Scope]
Primary reader job: [Learn, compare, do, solve, navigate, or buy]
Journey stage: [Awareness, evaluation, action, support]
Meaningful modifiers: [Audience, region, version, format, price]
Alternative interpretation: [Other plausible job]
Confidence: [High, moderate, or low with reason]

Coverage decision

Expected page type: [Guide, tool, help, comparison, policy, or other]
Existing primary URL: [Current best page or None]
Coverage strength: [Complete, partial, mismatched, duplicate, or absent]
Reader need not met: [Specific gap]
Original contribution available: [Evidence, example, workflow, or tool]
Decision: [Improve, merge, redirect, reframe, create, or decline]
Supporting internal links: [Adjacent distinct intents]
Owner and review date: [Name; YYYY-MM-DD]

Quality checks

Clusters reflect jobs rather than exact-match wording alone.
Market, language, device, and data period are recorded.
Search result observations are dated, not treated as permanent facts.
Existing pages were evaluated before new URLs were proposed.
One primary page owns each materially identical intent.
New pages have expertise and original value available.
Adjacent jobs are linked without being collapsed.
Decisions include measurement and review ownership.

How to use this template

Collect a bounded query set with source, market, device, date range, and available performance signals.
Group queries by reader job, stage, context, and meaningful modifiers.
Inspect current pages and result patterns to determine expected format and unmet need.
Assign one primary URL or justified new page to each distinct intent and resolve overlap.
Record evidence, differentiation, links, owner, priority, and review date for every decision.

Infer the job behind the wording

Group queries by the task a reader appears to be performing: learn a concept, compare options, complete a procedure, solve a problem, reach a known site, or make a transaction. Note modifiers that genuinely change the job, such as audience, format, jurisdiction, price, version, or urgency. Similar words can hide different needs, while different words can describe the same need. Record confidence and alternative interpretations rather than treating a classification tool as final truth.

Match intent to an appropriate experience

Choose a page type that can complete the job: explanatory guide, product tool, help article, policy, comparison, calculator, research report, or landing page. Inventory current URLs and judge whether each provides the expected answer, evidence, and next step. A high-ranking page format can reveal expectations, but copying its outline will not create original value. Define what your site can add through experience, data, workflow, examples, or clearer decision support.

Resolve overlap before naming gaps

When multiple pages target the same job, decide which should become primary and whether others should be merged, redirected, reframed, or kept for a truly distinct audience. Mark a gap only when no existing page can reasonably be improved to serve it and the team has enough expertise to produce useful content. Connect adjacent intents through internal links rather than squeezing every question into one page. Revisit the map as demand, products, and result formats change.

See the fields in context

Fictional example: bicycle repair workshop searches

Pedal Shed is an invented workshop and all query observations are illustrative.

Queries: “bike puncture class,” “learn to fix flat bicycle tire,” and “puncture repair workshop.”
Mapped job: Find an instructor-led class, not merely read repair instructions.
Existing coverage: A fictional blog explains the process but omits class dates, accessibility, cost, and booking.
Decision: Improve the class page for transactional details and link to the guide for preparation; do not create three keyword pages.
Review signal: Track impressions and completed bookings while also recording support questions about class suitability.

Frequently asked questions

How many keywords belong in one cluster?

There is no useful fixed number. Group expressions when they share the same reader job and can be served naturally by one coherent page.

Does a different search result page require a different URL?

Not automatically. Results vary by market, device, and time. Create a separate page only when the underlying intent and useful experience are genuinely distinct.

Should low-volume questions be ignored?

No. A low-volume question can be essential to conversion, support, safety, or trust. Prioritize by reader and business value as well as estimated demand.

When should the map be updated?

Review it after major site or product changes, emerging queries, significant traffic shifts, and periodic performance analysis.