Inventory page jobs before assigning queries
Write one sentence for each important page: who it helps, what decision it supports, and what the visitor can do next. A collection page helps people compare products; a guide may explain measurements; a local service page needs to establish an actual service area.
If two URLs have the same description, investigate the overlap before adding more keywords. If an important user job has no page, record a gap rather than immediately creating a draft. The business may not offer the service, or an existing page may only need a clearer answer.
Use intent, result type, and business fit together
Group queries when one page can satisfy them without changing its purpose. Review the current results for a representative sample. Shared ranking pages and similar result types are useful evidence, but they are not the only criterion.
Check the proposed group against the actual offer. A high-demand topic is a poor target if the business cannot help that audience. Market and language matter too: the same phrase can lead to a different task in another country or search context.
• The searcher is trying to complete the same job.• The result pages favor a compatible page type.• The business can provide a useful answer.• One destination can serve the group clearly.
Give every group a decision state
Use states such as mapped, improve existing page, investigate gap, and no separate page. A “no page” decision is valuable: it prevents a research sheet from becoming an automatic backlog of thin content.
For mapped groups, store the intended page, primary job, supporting queries, market, and evidence date. For a gap, describe the missing answer in user terms. The issue might be delivery conditions, a comparison, a useful filter, or proof of availability rather than a missing article.
Investigate page overlap without assuming cannibalization
More than one ranking URL is a signal to inspect, not automatic proof of a problem. Two pages may serve different stages of a decision. A conflict is more plausible when their purpose and content are nearly identical, the selected URL changes repeatedly, and users have no clear reason to choose one.
Compare actual pages, internal links, canonicals, and observed rankings. The answer may be to distinguish the pages, strengthen navigation, consolidate them, or leave both in place. Record the reason so a later editor does not reopen the same decision without new evidence.
Worked example: one product, three search jobs
A fictional outdoor retailer sells hiking boots. “Waterproof hiking boots” suggests a collection or product choice. “How should hiking boots fit?” asks for guidance. “Hiking boot store near me” needs a real local destination with accurate opening and inventory information.
Putting all three into one cluster would hide those jobs. The map assigns the purchase group to a collection, the fit questions to a guide, and the local group only to locations the retailer actually operates. If there is no store in a searched city, the correct decision is not to manufacture a location page.
Maintain the map as a decision log
Add a decision date, owner, and next review trigger. Revisit a group when the offer changes, a URL moves, a new result pattern appears, or tracking shows a sustained change. Avoid rebuilding the entire map because one keyword fluctuated.
The practical output is a short queue: improve one existing page, research one uncertain group, resolve one overlap. A maintained map gives content, engineering, and SEO teams a shared explanation for why the work exists.