Why Position 14 With 40k Impressions Beats Position 11 With 200

Why Position 14 With 40k Impressions Beats Position 11 With 200

Every SEO who has ever sorted a Search Console export by average position has made the same mistake: they pulled the queries sitting at 11 through 20, picked the ones closest to the top, and started rewriting pages. That instinct feels right and it is almost always wrong. A query at position 14 with 40,000 impressions is a far better target than a query at position 11 with 200, and until you weight striking distance by demand, you will spend your month polishing pages nobody is searching for. This is the case for scoring striking-distance queries as impressions multiplied by position gap to page one, and it changes which pages you touch first.

Why raw position hides the real opportunity

Position is a ratio, not a volume. A query at position 11 is ranked 11th out of however many pages compete for it, and that number tells you nothing about how many people see the result. Search Console’s average position is also an average across every impression, so a query that ranks 3rd on desktop and 25th on mobile can report something like 11.7 and get flagged as striking distance when the real story is mobile. Sort by position alone and you are sorting by a metric that has already thrown away the two numbers that matter: how often you appear and how far you have to climb.

Impressions are the demand signal. They tell you how many times Google showed your page for that query in the selected period, which is a decent proxy for how many people are actively looking. A query with 40,000 impressions and a position of 14 is a page that Google already considers relevant enough to surface thousands of times a month, just not high enough to earn the click. That is headroom. A query with 200 impressions at position 11 is a page that barely gets shown, and even a jump to position 3 might add a few dozen visits.

Run the arithmetic and the gap becomes obvious. Position 14 with 40,000 impressions sits four spots from the bottom of page one. Position 11 with 200 impressions sits one spot away. If you assume a rough click-through curve where page-one positions capture meaningful traffic and page-two positions capture almost none, the first query has tens of thousands of impressions of upside and the second has a rounding error. The weighted score, impressions times position gap, puts them at 160,000 against 200. That is not a close call.

Building the weighted striking-distance score

The formula is deliberately simple: impressions multiplied by the number of positions between the query’s average position and page one. Define page one as position 10 or better, so a query at 14 has a gap of 4, a query at 19 has a gap of 9, and anything already inside the top 10 scores zero because it is not striking distance at all. This keeps the math honest and forces every candidate to justify itself on both demand and distance.

The gap matters because it estimates effort. Climbing from 14 to 10 is usually a matter of tightening on-page relevance, adding a missing subtopic, or fixing an internal link; climbing from 30 to 10 is closer to a rebuild. Multiplying by the gap rewards queries that are both in demand and realistically winnable in a single update cycle, which is exactly the set you want at the top of the queue.

Where the data comes from and what to filter out

Pull the raw query data from Google Search Console, ideally a 90-day window so seasonal noise averages out, and filter to queries with an average position between 11 and 30. Below 11 you are optimizing something already on page one, which is a different job. Above 30 the gap is so large that the score inflates on distance alone, and you end up chasing queries you cannot move this quarter. As covered at https://kittoseo.com/, apply a few sanity filters before you trust the ranking:

  • Drop branded queries, since you already own those results and the position is not a content problem.
  • Drop queries where impressions are inflated by a single viral day; a 90-day view mostly handles this, a 7-day view does not.
  • Separate desktop and mobile using the device filter, because blended averages hide mobile-specific ranking drops.
  • Flag queries where the landing page is a category or tag archive rather than a real article, since those need a different fix.
  • Check that the query actually matches the page’s intent; a high score on a mismatched query means you need a new page, not an update.

Kitto connects to Google Search Console directly, so this pull happens without exporting CSVs and rebuilding pivot tables by hand. Its opportunity map applies the weighted impressions-times-gap scoring automatically, which means the pages at the top of your list are the ones with real demand headroom rather than the ones that merely look close to page one.

From opportunity map to published update

Once the list is ranked, the work is unglamorous: take the top page, read it against the query, and find what is missing. Usually the page covers the topic but not the specific phrasing people search, or it buries the answer three scrolls down, or it lacks the comparison table, the current year, or the named source that would let Google trust it for that query. Fixing those is where the ranking move comes from. The weighted score just tells you which page deserves your Tuesday afternoon.

This is where most AI writing tools fall apart. They will happily generate 1,500 words of fluent filler, but fluent filler does not move a position-14 query, because the page is already relevant and the problem is depth, accuracy, and freshness. Kitto is AI SEO content software built for the opposite job: it writes SEO articles for existing pages, targeting the specific striking-distance queries you feed it, rather than spinning up net-new posts that compete with your own URLs. You give it the URL and the query, and it drafts the expansion, the updated section, or the missing comparison in the voice of the existing page.

Drafting is the easy half. The part that decides whether an update helps or hurts is whether the new claims are true. Every draft Kitto produces goes through a quality gate before it reaches you. The gate checks claims with a number, a date, or a name against sources, and anything it cannot verify gets flagged for you rather than published as fact. That matters more than it sounds: a single fabricated statistic on a page you are trying to push from 14 to 8 can undo months of link equity and trust, and Google is not gentle about it.

Approach to striking-distance updates What it optimizes for Main weakness
Sort by average position, 11 to 20 Proximity to page one Ignores demand; picks 200-impression queries
Sort by impressions only Raw volume Surfaces queries you already rank 2nd for
Manual CSV export and pivot Full control Hours of work per cycle, easy to drift
Impressions times position gap Demand and winnable distance together Needs clean, deduplicated query data
Weighted score plus a quality gate Demand, distance, and factual safety Requires a review step before publishing

The publishing step is where a lot of good analysis dies. You find the right page, write the update, and then it sits in a draft folder for two weeks because nobody wants to touch the CMS. Kitto publishes articles through a WordPress connection, so the approved draft lands on the live page without a manual copy-paste, and the change goes out while the query data is still fresh. That loop, from Search Console pull to published update, is what SEO content automation should actually mean: not mass-producing posts, but shortening the distance between a data signal and a shipped fix.

Before you commit a full cycle to a list, it is worth confirming the basics are not broken. A free SEO audit from Kitto will surface crawl issues, missing metadata, and indexing problems that can quietly cap a page’s ceiling, and there is no point rewriting a page that is being held down by a technical fault. The audit runs against your site and gives you the fix list; the striking-distance work comes after. You can start at app.kittoseo.com and run the audit before you touch content.

Start this week by pulling 90 days of Search Console queries, filtering to positions 11 through 30, and scoring each one as impressions times the gap to position 10. Sort descending, take the top five, and check whether the landing page for each actually answers the query. Fix the single biggest gap on the highest-scoring page, run the draft through a quality gate so no invented number slips through, and publish it through your WordPress connection the same day. Then watch that one query’s position and impressions for 30 days before you repeat the process. The pages that move are the ones with demand behind them, and now you can tell which those are before you spend the afternoon.

Share with

Start typing and press Enter to search

Shopping Cart

No products in the cart.