Query the right dimensions
Request Search Analytics with query and page, over a complete date window. Keep pairs averaging roughly positions 11–20 and with a meaningful number of impressions; avoid interpreting unreturned rows as zero.
Search Console · SEO diagnosis
Find striking-distance keywords in Google Search Console
Find queries where your pages average roughly positions 11–20, then group them by landing page and weigh impressions, relevance and current clicks. These are candidates for inspection, not keywords guaranteed to reach page one.
14 days free · No credit card
Google Search ConsoleIllustrationAverage position · fictional query12.7
A position near page one plus 3,900 impressions can justify a closer look; it does not predict future traffic.
Position 20Position 11
01 / Understand the signal
Near page one is a shortlist, not a forecast
An average position of 12.7 blends different searches, devices and locations. The same URL can rank near the top for one query and much lower for another. Start with query–page pairs and meaningful impressions, not a flat export of keyword averages. An attractive number without matching search intent is not an optimization opportunity.
02 / The analysis01 02 03
Find plausible opportunities without inventing traffic gains
Group by landing page and intent
Several near-page-one queries may map to one URL. Group them so you can investigate the page once, then check whether it actually answers the shared intent.
Prioritize and validate
Look at clicks, impressions and position in the same context. Manually inspect relevant SERPs and the page before adjusting H1, title or sections. Measure again after publication; do not estimate clicks from position alone.
03 / Worked example
Three query–page pairs; only two are in the shortlist
Position 11–20 is a practical filter, not a Google rule. Add impressions and intent before calling any query a quick win.
| Query / example URL | Impressions | Avg. position | Decision |
|---|---|---|---|
| gsc mcp guide → /guides/mcp | 3,900 | 12.7 | Review intent and this page's coverage first. |
| search data ai → /blog/analysis | 560 | 16.4 | Possible secondary query; inspect intent before investing. |
| brand docs → /docs | 2,800 | 9.7 | Already inside top 10: exclude from the 11–20 shortlist. |
All URLs, queries and numbers in this table are fictional. They demonstrate the method, not actual performance.
Read the evidence
A query at position 12.7 is not one edit away from ranking #1
In this fictional sample, the 3,900-impression pair deserves analysis because the query and landing page may fit. The query at 16.4 receives far fewer impressions, so potential impact is less clear. The third pair already averages 9.7 and should not be counted as striking distance under a strict 11–20 rule. None of those averages predicts future clicks.
04 / Ready-to-copy prompts
Three prompts for finding near-page-one queries
These prompts target query–page pairs. Ask for URLs and relevance checks rather than a bare list of keywords.
AskGSC offers read-only Google Search Console access through MCP: accessible properties, Search Analytics and period comparisons. Use the exact authorized property, not a guessed domain.
Explore all 18 Google Search Console prompts01Find the candidates
For [PROPERTY], get the last complete 28 days grouped by query and page. Keep returned query–page pairs averaging positions 11–20, with at least [MIN_IMPRESSIONS] impressions. Show query, URL, impressions, clicks and average position; group candidates by page.
02Separate signal from noise
For [PROPERTY], rank query–page pairs averaging positions 11–20 in a complete 28-day window. For each leading URL, cluster related search intents, exclude irrelevant queries and explain why impressions are meaningful without forecasting clicks.
03Check the trend
For [PROPERTY] and [PAGE URL], compare the same query–page combinations over two complete equal 28-day periods. Show clicks, impressions and average position in each. Explain improvements or declines without treating average position as a fixed daily rank.
05 / Decide what to do01 02 03
Decide whether to refresh, clarify or leave alone
Clear intent gap
The page already addresses the query but misses a relevant subquestion. Improve that section with a useful answer, not keyword repetition.
Query does not match the page
Do not force the target term into the title. Consider whether a different existing page matches better before building new content.
Position looks promising, demand is tiny
Skip for now if better opportunities exist. A 20% visibility gain on almost no impressions may have little impact.
Average position is not a precise rank or a traffic forecast
GSC averages positions across impressions; it can omit anonymized queries, and the newest reporting days may be incomplete. AskGSC cannot supply external search volume, scrape SERPs, detect on-page quality or calculate reliable extra clicks from a hypothetical jump to position ten.
06 / FAQ
Questions worth answering
What Search Console can and cannot tell you about this particular SEO problem.
01What are striking-distance keywords?+
They are queries where a page sits just outside an arbitrary visibility threshold, often average positions 11–20. They are candidates for review, not guaranteed wins.
02Should I optimize for every query in positions 11–20?+
No. Check impressions, intent, click history and which URL already ranks. Ignore irrelevant or very low-impact queries.
03Can GSC tell how much traffic a top-10 ranking would add?+
Not reliably. Average position, SERP layout and query demand vary. Avoid precise uplift forecasts from a fixed CTR curve.
Run it on your own data
Prioritize opportunities by intent, not just position.
Ask your AI assistant for the right query–page pairs and a shortlist you can verify before writing another paragraph.
Find my ranking opportunities14 days free · No credit card