Choose SEO keywords by identifying the reader’s task, retaining the query evidence and assigning a clear page owner. Use observed search data and result inspection to test the interpretation. Similar wording may belong on one page, while a superficially related query may require a different answer, service route or official destination.
Begin with the business’s actual offering and the questions it can answer well. Write the intended reader outcome beside each candidate query before proposing a title. This gives the team a way to reject an attractive phrase when it does not fit the service, the available evidence or a useful article format.
What does the query evidence actually describe?
Google’s Search Console performance guidance provides one source of observed site data. Search Console’s performance report shows queries bringing traffic to the site. The queries dimension groups report data by the search query entered. Retain the query and report context together when using that evidence in an editorial decision.
Search Console clicks count clicks from Google Search results. Search Console impressions count appearances in search results. Click-through rate divides clicks by impressions. Keep these meanings explicit when discussing why a page deserves attention; the metrics answer different questions about the site’s observed search presence.
Average position describes the site’s topmost result. Treat the reported value with its grouping and context rather than presenting it as a fixed rank that every searcher sees. Observed search results depend on the searcher’s time, place, device and recent history. Record those details when inspecting results for the proposed task.
Report views can use different metrics, dimensions and date ranges. Save the selected context with an export or review note so another person can understand the comparison. A query in a site performance report is evidence about that report, not a licence to invent a national demand estimate.
How should intent determine the page’s job?
Read the query as the beginning of a task. Someone looking for a software login needs a destination; someone comparing implementation approaches needs a decision; someone describing a fault needs a diagnostic. State the intended outcome in plain language before deciding whether the site should create another article.
Inspect relevant results and open the primary documents needed for consequential facts. Keep search-result titles and snippets as discovery evidence. The author still needs the underlying source, its applicability and the qualifications that affect the reader’s decision.
Compare the proposed task with existing pages. A synonym that asks for the same answer usually needs a relationship to the existing owner rather than an automatically generated new URL. A genuinely different workflow needs its own boundary and original contribution so it earns space in the content inventory.
| Candidate task | Ownership decision to assess | Useful evidence |
|---|---|---|
| Find a named login | Route to the legitimate destination where appropriate | Actual navigational intent and official page |
| Understand a service | Use the relevant service page | Confirmed offering and clear enquiry journey |
| Compare implementation approaches | Assign a distinct decision guide | Opened primary documents and useful comparison |
| Resolve a specific fault | Assign a focused diagnostic | Reproducible question and documented behaviour |
| Ask a synonym of an existing question | Consolidate with the existing owner where the outcome matches | Current page body and explicit overlap decision |
This original ownership worksheet connects evidence to the page’s purpose. It also gives the editor a way to explain why a candidate was consolidated or rejected. Preserve that decision so the same synonym does not repeatedly return as a supposedly new opportunity.
What should a research record retain?
Keep the original query, evidence source, retrieval date and relevant market or report context. Record the result inspection separately from the claim sources used in the article. A keyword tool, search listing and product manual perform different roles in the research trail.
Write a boundary statement for the proposed page. Specify the decision or workflow it owns and name the adjacent pages it should link to. Add the original contribution the reader will receive, such as a task-specific comparison or diagnostic worksheet. This helps the author develop depth without reproducing a neighbouring guide’s complete introduction.
Google’s SEO starter guide explains discovery and inspection. Google primarily discovers pages through links from pages it has already crawled. Plan relevant links between the new page, its service route and genuinely related answers as part of the editorial work.
Google’s starter guide recommends URL Inspection to examine how Google sees a page. Keep delivery and index-status checks in the later verification record. A well-supported editorial decision and a page’s actual search delivery are related stages, each requiring its own evidence.
Original query-to-owner decision exercise
Consider a fictional website team reviewing queries about appointment software. Its sample list includes a product login, a request for booking-software development, an integration question and a synonym of an existing scheduling guide. These are illustrative task descriptions, not measured keyword findings.
First, write the reader’s expected result for each sample. Give the navigational query its appropriate destination decision and identify the genuine service enquiry. Ask the editor to explain why an article would or would not help the person complete each task.
Next, inspect the current content inventory for the integration question and scheduling synonym. Read the candidate owner’s body, not just its title. Record what it already answers and what remains distinct. A different title alone should not settle the decision to create another page.
Then propose an original contribution for the distinct integration question. List the primary documents required and the exact configuration or exception the proposed worksheet will help the reader assess. If those documents cannot be retrieved or do not support the task, retain that gap rather than replacing it with generic prose.
Finally, record the owner URL, boundary, evidence and decision for every sample. Have another editor review the mapping and explain any disagreement through the actual reader outcome. Keep that record with the content brief so later revisions remain faithful to the page’s purpose.
How should the decision be reviewed after publication?
Compare later observations using a recorded report context. Ask whether the page is appearing for the intended task, whether another existing page is serving it instead and whether the delivered answer needs clarification. Use those findings to revise the content and ownership decision thoughtfully.
Keep measurements and interpretations distinguishable. A change in clicks may prompt an investigation, while the cause still needs evidence. Retain the observed data and the editorial changes being considered so the next reviewer can follow the reasoning.
For related work, see search visibility and website development. Get started with the query evidence, current page inventory and outcomes your content needs to serve.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.