Blog

Search Console's "average position" isn't your ranking — here's what it actually is

Open Search Console, look at any query, and you'll see a number like 11.3. It's tempting to read that as "I rank 11th." You don't. Nobody does — 11.3 isn't a position anyone has ever held on a results page, because positions are whole numbers.

That number is an average, and understanding what it's averaging changes what you should actually do about it.

What's actually being averaged

Search Console's position for a query is the mean of every position that query's impressions were logged at, across:

  • Every device — a page can rank differently on mobile and desktop for the same query, and GSC blends both into one number.
  • Every location — "best running shoes" can mean a #3 result in Toronto and a #14 result in São Paulo. One row in Search Console, two very different realities.
  • Every personalization state — signed-in results, Search history, local pack inclusion or exclusion — all folded into the same average.
  • A rolling multi-day window, reported with a two-to-three day delay.

So when a query shows 11.3, that could mean: a stable #11 everywhere, or a genuine #3 in one country dragged down by a #40 everywhere else, or a page that used to rank #6 and dropped off page one three days ago and GSC hasn't caught up yet. From the number alone, you cannot tell which.

Why this is worse than it sounds

The practical failure mode isn't "the number is slightly off." It's that two completely different situations produce the identical average, and only one of them is a problem worth reacting to.

A page holding a stable #11 across every market is a normal optimization target — write better content, build more relevance, and expect to climb gradually. A page that's actually #3 in your biggest market but invisible everywhere else is a distribution problem, not a quality problem — the content is clearly good enough to rank, it's just not reaching the other markets you're being judged as if you're already in.

You'd fix those two situations completely differently. Search Console hands you the same number for both.

What a verified check adds

A verified rank check is the opposite of an average: it's a single, real search, run right now, from one specific country, with no blending. Search "best running shoes" from a browser physically in Germany and you get Germany's actual result page — not a number that's secretly 60% Germany and 40% somewhere else.

Run that same search from five countries and you get five real answers instead of one blended guess. That's the entire idea behind tranck — it starts from your Search Console data (free, and it already knows which keywords matter to your site), then lets you verify any of them from any country you actually sell in, with a real search, on demand.

You don't need an account to see the difference for one keyword right now — the free rank checker runs a real, live search from any country and shows you the actual number, not an average.

The honest caveat

Search Console isn't wrong to report an average — it's answering a genuinely different question than "where do I rank." It's telling you about demand: how much impression volume you're getting, in aggregate, across everywhere Google showed your page. That's real, useful information a verified check can't give you on its own — a verified check tells you the rank in one place, not how much traffic is actually flowing.

The mistake is using one to answer the other's question. Demand and rank are both worth knowing. They're just not the same number, and no amount of decimal precision in an average makes it one.