← All posts

Which Striking Distance Keywords to Prioritize (Click Math)

Not all striking distance keywords are worth the same push. Rank them by the clicks a climb actually buys, using your own Search Console impressions.

QueryScope team · · 8 min read ·
search console gsc striking distance rankings

When you've got a handful of striking distance keywords, push the one where a climb buys the most clicks, not the one with the most impressions. The payoff of moving up is that query's impressions times the click-through rate you'd earn at the higher position, minus the clicks you get now. Run that on each near-miss and a flat list becomes a ranked one.

Once you've found the queries sitting just off page 1, the real question is which one to spend time on first. This post gives you the click-through-rate curve to answer that, a worked example where the higher-impression query loses, and the honest limit on what the number can promise.

TL;DR:

  • The payoff of a climb is impressions times the click-through rate at the target position, minus the clicks you get today. Rank your near-misses by that number, not by impressions alone.
  • The click-through-rate curve is steep near the top: moving from position 8 to 5 roughly doubles clicks, and 5 to 3 doubles them again. The same one-spot climb is worth far more the higher you already are.
  • A near-miss with fewer impressions but a shorter, more certain climb often beats a high-impression query stuck deep on page 2. Weight the payoff by how reachable the climb is.
  • The number is an upper bound. Search Console can't see the competition, the curve is a clean-results-page average and not your site, and it stops at the click.

How much extra traffic does ranking higher actually get you?

Take the query's monthly impressions, multiply by the click-through rate at the position you're aiming for, then subtract the clicks you already get. That difference is the extra traffic the climb buys. A query with 1,000 impressions moving from position 8 to position 3 goes from about 21 clicks to about 102: a gain of roughly 80 a month.

Those percentages come from a large click-through-rate study. On a clean results page, with no ads, no image pack, and no AI Overview, organic clicks fall off fast below the top few spots:

  • Position 3: about 10.2% of clicks
  • Position 5: about 5.1%
  • Position 8: about 2.1%
  • Position 10: about 1.6%

The study is explicit that these are averages for a plain results page, and that the top positions read lower when a snippet, an AI Overview, or a local pack sits above them (First Page Sage). So treat the curve as a rough shape, not your site's actual rates. Your own click rate at a given position is the honest input when you have it; the curve is the gut check when you don't.

Why do more impressions not mean a bigger payoff?

Because the payoff is impressions times the click-through-rate jump, and the jump is bigger the closer you already are to the top. A query buried at position 15 has plenty of impressions but almost no reachable click rate: even a big climb to position 8 only unlocks 2.1%. A query at position 6 sits on the steep part of the curve, where a few spots are worth real traffic.

Say you've found two near-misses in your query view:

  • Query A gets 600 impressions a month at position 6. At 4.4% it earns about 26 clicks now. Nudge it to position 3 (10.2%) and it earns about 61: a gain of roughly 35 clicks a month, for a three-spot climb on a page you already rank on.
  • Query B gets 2,500 impressions a month at position 14, deep on page 2, earning almost nothing. Push it to the bottom of page 1 at position 8 (2.1%) and it earns about 53 clicks: a gain of roughly 53, for a six-spot climb across the page-1 line.

By impressions, Query B wins four to one. By raw payoff, B still edges A, 53 to 35. But look at what each climb asks. A is a short hop on a page that already ranks. B is a long haul across the page-2 wall, past everything already on page 1, with no guarantee you clear it. Adjust for that and A is the safer first move: a near-certain 35 beats a speculative 53.

How do you turn a list of near-misses into a priority order?

Run the payoff math on every near-miss, then weight each number by how reachable the climb looks. A short climb on a page you already rank well on is money in the bank. A long climb from deep on page 2 is a bet. Sort by payoff, then bump the near-certain ones up and the long shots down.

Three things decide reachability, and none of them are in the payoff number:

  • How far the climb is. Three spots on page 1 is a nudge. Six spots across the page-1 boundary is a project.
  • Whether the page already answers the query. If it does, you're closing a small gap. If it only mentions the words, ranking it higher just sends people to a page that bounces them.
  • Whether you can realistically beat the pages above you. Sometimes you can't, and Search Console won't tell you (more on that below).

Once you've picked the near-miss worth the most, pushing it onto page 1 is a matter of deepening the answer and linking to it with the query as anchor text. The picking is this post; the pushing is that one. If you'd rather not run the math by hand on every page, the striking-distance view surfaces the near-misses already ranked by the clicks a climb would buy.

Try it

Read your own Search Console, not just an essay about it.

QueryScope brings your real Search Console data into Claude Code or Cursor, so your agent reads it for you. From $14.99/month.

Isn't this just fixing a low click-through rate?

No. A low click-through rate is a page already on page 1 that gets skipped over: same position, and you win a better click rate with a sharper title. This is the opposite. You're not on page 1 yet, so there's no earned click to win back. You're paying for a better position, and the clicks come with it.

The two use the same curve from opposite ends. Fixing a low click-through rate at a good position compares your click rate to the curve at the position you already hold, and asks why you're under it. This asks what click rate you'd earn at a higher position, and whether the climb is worth it. One is a title job; this is a ranking job. The tell is position: a strong position with a weak click rate is the title problem, and a just-off-page-1 position is the ranking problem this math is for.

What can't the click math tell you?

It can't tell you whether you'll win the climb. The payoff number is an upper bound, the clicks you'd get if you reach the target position. Whether you can reach it depends on the pages above you, and Search Console shows you none of them: not their backlinks, not their depth, not whether the query is locked up by sites you won't outrank.

Three limits ride with every payoff estimate:

  • The climb isn't guaranteed. The number assumes you land the target position. Search Console is blind to the competitive results page, so it can't tell a query you'll win in a week from one you'll never take. Treat the estimate as the ceiling, not the forecast.
  • The curve is a stranger's average. Those click-through rates are blended across many sites and clean results pages. Your brand, your snippet, and any AI Overview above you all move the real number. Use your own click rate at each position when you have it.
  • Position is a blended average. A page's reported position hides the per-query positions inside it, so read each near-miss at the query level, not off the page number. The metrics behind the report explain why the page average buries the query that's actually close.

And the limit under all of them: Search Console stops at the click. The math ranks clicks, not customers. A query worth 50 clicks a month might convert better than one worth 200. The payoff estimate points you at traffic; the value of that traffic is a judgment the data can't make for you.

Doing this without checking every page by hand

Run by hand, this is a lot of lookups: open the query view for every page, find the near-misses, pull each one's impressions and position, apply the curve, and weigh the climb. It's the kind of weekly math that gets skipped the week you're busy, which is most weeks.

That's what QueryScope does from your editor. It reads your real Search Console data, surfaces the near-misses ranked by the clicks a climb would buy, and points your agent at the query and the page so it can deepen the answer and add the links. It reads one machine, your search traffic, and it's honest about the ceiling: it ranks the clicks a climb could earn, not whether you'll win the climb or what the clicks are worth. For the one-line meaning of position or impressions, the Search Console glossary defines each metric with its caveat.

Sources

  • First Page Sage, Google Click-Through Rates by Ranking Position (updated December 2025: position 3 around 10.2%, position 5 around 5.1%, position 8 around 2.1%, position 10 around 1.6%; averages for a clean results page with no ads, image pack, or AI Overview, which the report notes pull the top positions lower. A rough curve, not a per-site promise).
  • Google Search Console Help, What are impressions, position, and clicks? (position is the topmost position your link held for a query, averaged across all the queries the page appeared for, which is why a page's reported position hides the per-query near-miss).
Try it

Read your Search Console where you code.

Ask your coding agent how your site is doing. QueryScope reads your real Search Console data in the terminal: clicks, queries, intent, and indexing. From $14.99/month. One to ten sites.