Striking Distance Keywords: The Query Your Average Hides

A striking distance keyword is a query your site already ranks for just off page 1, close enough that a modest gain in ranking turns a page nobody sees into real traffic. The catch is that striking distance is a property of a query, not of a page, and Google Search Console reports position as a page-level average that hides the one query actually within reach. This guide shows you how to find the real near-miss in your own data, a three-part test for which ones are worth the work, and the honest limit on what your Search Console data can tell you.

The reason this matters: the near-miss almost never looks like a near-miss in the page report. It hides inside a blended average, and the tools that tell you to "export positions 11 to 20 and add the keyword" are working from the wrong number.

TL;DR:

• Striking distance is a query-level opportunity: one search sitting around position 8 to 20 with real impressions behind it, on a page whose overall average makes it look mid-ranked and unremarkable.
• Google's average position is the topmost spot you held, averaged across every query the page appeared for. A page averaging position 12 can hold position 8 for the query that matters. The average hides it.
• Find it in the query view, not the page view. Then gate each near-miss on three things: does the query have real demand, does it match the page's job, and does the page actually answer it or just mention the words.
• The move is to earn the ranking (deepen the section that answers the query, link to it internally), not to rewrite the title. Winning a click you already earn is a different job. And your Search Console data can tell you which queries are close, but not what is beating you.

What is a striking distance keyword?

A striking distance keyword is a query where your page ranks close to page 1, typically around positions 8 to 20, so a small improvement moves it into the range that actually earns clicks. Different tools draw the line differently (some say strictly page 2, positions 11 to 20), but the useful definition is behavioral: close enough that the gap to real traffic is worth closing, and far enough that you're getting almost none of it today.

The clicks live at the top. On a rough industry curve, position 3 earns around 10.2% of clicks, position 5 around 5.1%, and position 8 around 2.1% (First Page Sage, 2026 meta-analysis). Those are averages across many SERPs, not your site, so treat them as a gut check rather than a promise. But the shape is the point: moving a query from position 8 to position 5 more than doubles its clicks, and moving it to position 3 roughly quintuples them. That gradient is why the near-miss is worth finding. When you have several to choose between, the same gradient tells you which to push first: the payoff of a climb is impressions times the click rate you'd earn higher up, so a flat list becomes a ranked one. It's also why the bottom of page 1 and the top of page 2 are where the gains sit: you've already earned the relevance to rank, you just haven't earned the placement that pays.

Why does your average position hide the real near-miss?

Because Google Search Console reports position as an average of your topmost placement across every query a page appeared for, and averaging blurs the one query within reach into the crowd. Google's own definition is specific: for each query, it records the single highest position your page held, then averages that number across all the queries where the page showed up.

Google's worked example makes the blurring concrete. If one query returns your page at positions 2, 4, and 6, that query counts as position 2 (the topmost). If another query returns it at 3, 5, and 9, that counts as 3. The reported average across those two is 2.5. Now scale that up: a page that shows for forty queries reports one position number, and a single query sitting at position 8 with strong demand is averaged in with thirty-nine others ranking far lower. The page reads as "position 22" and looks hopeless, while the query that could move is invisible.

This is the same reason the page-level number is honest for volume but useless for finding the near-miss. The overall average tells you how the page does on the whole. It cannot tell you which query inside it is one push away, because it was never designed to. To see that, you have to stop looking at the page and look at its queries. In a 28-day read of a real SaaS account, exactly this pattern showed up: a query sitting close to page 1 that the page's blended average had buried out of sight. The page looked ordinary. One of its queries wasn't.

If the "topmost, then averaged" behavior is new to you, the Search Console metrics guide walks through why position is the most misread number in the report.

How do you find striking distance keywords in Search Console?

Open the query view for a page, not the page report, and look for a query with a position around 8 to 20 that already carries real impressions. The page-level average is where the opportunity hides; the per-query breakdown is where it surfaces. Sort a page's queries by impressions, then scan for ones ranking just off the top with demand behind them.

Three signals mark a genuine near-miss:

• Position roughly 8 to 20. Close enough that a content and linking pass can realistically move it, not a position 40 that needs a different page entirely.
• Real impressions. Google is already showing the page for this query often enough that a better ranking would convert into clicks. A query with three impressions is noise; the position is a rounding error, not an opportunity.
• A query you can point at. You need the exact phrase, because the whole move downstream (the section you deepen, the anchor text you link with) is built around it.

One honest limit rides along here. The per-query view under-reports impressions, because Google hides queries issued by only a handful of people to protect privacy, so the counts you see are a floor, not the full picture. That's fine for this job: you're using the query view to find the phrase and confirm the ranking is real, not to total up traffic. Use the page-level number when you care about volume, and the query view when you care about which query is close.

Which near-misses are actually worth chasing?

Not all of them, and this is where most striking distance advice goes wrong. A query ranking at position 9 is only worth the work if it clears three tests: it has real demand, it matches what the page is for, and the page genuinely answers it. Fail any one and pushing it up the results is effort spent to attract the wrong visitors, or clicks you can't keep.

• Does the query have demand? Impressions are your proxy. A near-miss on a query almost nobody searches will still be a near-miss with almost no traffic after you win it. Chase the ones with volume behind them.
• Does it match the page's job? A checkout page ranking near page 1 for a "how does X work" question is a near-miss you may not want. Winning it brings researchers to a page built to convert. That's an intent mismatch, and the honest move might be to route that demand elsewhere rather than pull the page up for it.
• Does the page actually answer it? This is the test that separates a real opportunity from a trap. If the page only mentions the query's words in passing, ranking it higher just sends people to a page that doesn't deliver, and they bounce. If the page answers the query well but ranks just below the fold of page 1, that's the clean case: the relevance is already there, the placement isn't.

That last test is the one to run first, because it decides the move. A page that answers the query is a ranking job. A page that only mentions it is a content job, or not a job at all.

How do you push a page from page 2 onto page 1?

Once a near-miss passes the three tests, you earn the ranking the way Google assigns it: make the page a better answer to that exact query than the pages above you, then reinforce it with internal links that use the query as anchor text. Pushing a page from page 2 to page 1 walks the full playbook: what deepening the answer concretely means, how to link with the right anchor text, and how to read the climb in Search Console afterward.

This is a different job from winning a click you already earn, and it's worth being precise about the difference. If a page already sits on page 1 and just gets skipped over, that's a title and snippet problem: you're visible, the click is going elsewhere, and rewriting the title to match the query is the fix. Striking distance is the opposite situation. You're not on page 1 yet, so there's no earned click to win back. The job is to move the ranking itself, and a sharper title alone won't do it, though matching the title to the query helps here too because it reinforces relevance. The tell for which case you're in is position: a strong position with a weak click rate is a title or AI Overview problem; a just-off-page-1 position is a ranking problem.

Change one page at a time and note the date. Rankings move slowly and depend on things outside the page, so give it a few weeks and read the query's position again before deciding it worked.

What can't striking distance tell you?

Your Search Console data can tell you which of your queries are close to page 1. It cannot tell you why they're stuck there, or what it will take to pass the pages above you. That's the honest ceiling on this whole exercise, and pretending otherwise is how striking distance advice oversells itself.

Search Console shows your side of the results page and nothing else. It has no view of the competitors ranking above your near-miss, their backlinks, their content depth, or whether the query is locked up by a few entrenched pages you won't dislodge with a content refresh. A query at position 8 might jump to position 3 with one good editing pass, or it might be stuck behind sites you can't outrank without authority you don't have yet. Your own data can't tell those two cases apart, because the thing that decides them (the competitive results page) is the one thing Search Console doesn't record.

So treat a striking distance list as a list of candidates, not a list of wins. Two more limits ride with it: position is a blended average, so re-check the query directly rather than trusting the page number, and Search Console stops at the click. It can show you the ranking move and the clicks that follow, not whether those clicks turn into anything. Knowing where the ceiling is keeps you from spending a week on a query that was never yours to win.

Finding these without checking every page by hand

Done by hand, this is slow and easy to skip. You'd open the query view for every page, scan for positions around 8 to 20 with real impressions, run each candidate through the three tests, and separate the ranking jobs from the content jobs and the not-worth-it ones. It's the kind of weekly discipline that falls off the moment you're busy, which is most weeks.

That's what QueryScope does from your editor. It reads your real Search Console data, surfaces the queries sitting just off page 1 with the demand to make them worth chasing, and points at the exact phrase and the page that ranks for it, so your coding agent can deepen the right section and add the internal links without you exporting a thing. It reads one machine, your search traffic, and it's honest about the ceiling: it can tell you which queries are close, not what's beating them. For the one-line meaning behind position or impressions, the Search Console glossary defines each metric with the caveat that comes with it.

Sources

• Google Search Console Help, What are impressions, position, and clicks? (Google's own definition: position is the topmost position your link held for a query, averaged across all queries the page appeared for; a query returning your page at positions 2, 4, 6 counts as position 2, and the average across queries is what the report shows).
• First Page Sage, Google Click-Through Rates by Ranking Position (2026 meta-analysis: position 3 around 10.2%, position 5 around 5.1%, position 8 around 2.1%, position 10 around 1.6%; averages across many SERPs, useful as a rough curve, not a per-site promise).