Documentation checked: October 7, 2026
Before turning a search query into a new article, check whether an existing page already answers it. Improve that page when the reader's task is the same. Consider a separate post when the task, required explanation, or practical outcome is genuinely different.
This approach turns search data into an editorial decision rather than a list of near-duplicate titles. It works with a small site, provided you keep observed data separate from ideas you have not yet validated.
Start with a consistent reporting view
In Search Console's Performance report, select a date range and search type, then examine queries alongside pages. Clicks, impressions, CTR and average position help describe the results within that view. Google's report guide explains the available dimensions and filters.
Record the actual start and end dates. Also record country and device filters. An English-language article can reach readers in several markets; do not silently compare a worldwide report with a country-specific report.
Save one row per candidate:
- Query and associated page URL
- Reporting dates, country, device and search type
- Impressions and clicks
- What the reader appears to be trying to do
- Where the current page answers that task
- The proposed editorial action
This is evidence about your site's observed visibility. It is not a measurement of total market demand or a keyword-volume estimate.
Translate the query into a reader task
Consider two hypothetical queries: “affiliate link not working” and “affiliate payout pending.” The first reader needs to inspect a link and its destination. The second needs to understand a provider's payment process. They may justify different articles.
By comparison, “calculate blog CTR” and “blog click-through rate formula” may need the same answer. Different wording alone does not establish a new editorial opportunity.
For each candidate, finish this sentence: “After reading, the visitor should be able to…” Then identify the evidence, example or worksheet needed to deliver that result.
Choose update, new article, or hold
| Finding | Editorial action | Useful addition |
|---|---|---|
| The answer exists but is difficult to find | Improve the existing post | A clearer opening or better section order |
| Several queries ask the same question | Consolidate their coverage | Plain-language explanations of common terms |
| The reader needs a distinct procedure | Consider a separate article | A complete workflow with its own examples |
| The official conditions cannot be verified | Hold the idea | A specific research question to resolve |
| The query is unrelated to your readers | Reassess its relevance | A reason to cover it beyond traffic potential |
These are editorial rules proposed here, not Google's scoring formula. Google encourages original value and a clear intended audience rather than simply rewriting other sources. See its people-first content guidance.
Do not let one percentage choose the topic
Suppose candidate A has 800 impressions and eight clicks, while B has 120 impressions and six clicks. Their CTRs are 1% and 5%. These are invented figures for illustration.
These figures do not prove that A has a poor title or that B should become a ten-part series. A may appear for broader queries or in different positions. B may answer a narrower, well-matched question. Read the pages and inspect the query mix before deciding.
A useful planning note might say:
“Readers asking about mismatched analytics counts currently reach a general metrics glossary. That page defines the terms but lacks a comparison worksheet. Investigate a separate troubleshooting article that aligns units, dates and filters.”
That note identifies a concrete addition without inventing a traffic forecast.
Prioritize a repair when it matters more
An incorrect condition or broken destination can deserve attention before a new post. After urgent corrections, prioritize questions you can answer with reliable sources and a useful original example.
If your query history is sparse, use genuine reader questions, documented workflow problems or official help topics as starting hypotheses. Label them accordingly. Do not describe them as high-volume keywords.
After publication, check which queries actually lead to the article and whether they match its intended task. A page with little data belongs in “insufficient evidence,” not automatically “failed.”
Editorial note: Prepared with AI assistance using official documentation. Query examples and figures are hypothetical. This process does not guarantee search demand, rankings or revenue.
