Striking-distance queries explained

A striking-distance query is a search term where a page already earns impressions but sits below the top results, so a modest content or technical improvement has a measurable path to test. SiteBienfait ranks these opportunities by evidence rather than assumption. Google Search Console’s Search Analytics API, updated 2026-08-11, returns clicks, impressions, CTR and average position per query and page.

What counts as striking distance?

There is no official threshold. The useful working band is page one to page two: queries where a page has impressions but its average position is beyond the first few results. The exact cut-offs depend on the niche and the device mix, which is why the band should be written down in the review document rather than treated as a law.

The filter that matters more than the position cut-off is impressions. A query with a handful of impressions does not have enough data to learn from, and acting on it produces noise.

Where does the data come from?

Two places: the Performance report in Search Console and the Search Analytics API. The report is enough for a first read. The API, documented with an update on 2026-08-11, returns rows containing the requested dimensions together with clicks, impressions, CTR and position.

Request the query and page dimensions together, because the same query can reach a site through several URLs. A shortlist built on query totals alone hides which page is actually competing, and the fix belongs on a page, not on a query in the abstract.

Two cautions are documented in the data itself. Position is an average across users, locations and devices, not a rank. And queries are only reported when they meet a privacy threshold, so the list is a sample, not the full demand.

How is the list filtered?

Start with the queries that have enough impressions to matter and whose intent the site genuinely serves. Remove the ones where the query is about a different product, a different location or a different job. Add the page URL beside every row, then group the rows by page.

The shortlist should be small enough to work through. Ten pages with a clear gap each are more useful than two hundred rows in a spreadsheet. For each page, look at the actual results for that query and ask what the top pages do that this page does not: a direct answer, a comparison table, local detail, a named author, a price.

Also check whether the page is simply the wrong destination. Sometimes the striking-distance query needs a new section on an existing page, and sometimes it reveals that two pages compete for the same term.

What change actually helps?

The change has to make the page a better answer to that query. In practice that means a short direct answer near the top, a title and description that name the query honestly, internal links from related pages, and the sub-questions the query implies answered in order. Structure helps: headings phrased as the questions people ask, and facts dated and attributed so they can be quoted.

Google Search Central, updated 2025-12-10, publishes a guide to the ranking systems and makes the point that no single signal explains a result. That is why a change should be a bundle that improves the page, not a keyword insertion. Google’s page experience documentation, updated 2026-09-22, adds that Core Web Vitals are used by ranking systems, so a slow template can hold a good page back.

How should the results be measured?

Write the baseline down before changing anything: the query set, the page, average position, clicks and impressions for a fixed window. Change one group of pages at a time. Wait for recrawl and reindexing, then compare the same queries over a comparable window, not a single day.

Expect a mixed result. Some queries move, some do not, and some change because a competitor published something. The honest output of a test is a documented outcome — improved, unchanged or worse — and a decision to keep or roll back. A rising average position is not a promise about the future.

SiteBienfait’s SEO route builds striking-distance work as a change set: the evidence, the proposed edit, the preview and the measurement window, all approved before publishing. The redirect map checker is useful before the analysis begins, because a page that is still redirecting is not a page that can be improved. The companion guide on reading Search Console after a migration explains the reports when the site has just moved.

Sources

• Google Search Console API, Search Analytics: query, last updated 2026-08-11.
• Google Search Central, A guide to Google Search ranking systems, last updated 2025-12-10.
• Google Search Central, Understanding page experience, last updated 2026-09-22.