TL;DR
Search Console is the most honest data you have about your own site, and it is blind in two specific directions. It cannot tell you what you do not rank for, because it only contains queries where you already appeared. And on a large site it cannot tell you which query lost the traffic, because the table stops at 1,000 rows and the rare queries are never tracked. Both limits are structural. Neither is a setting you can change.
In an audit I wrote for a fitness certification site in 2022, one row read: ‘health coach’, 15,317 impressions, 25 clicks, average position 44. Two people can read that row and reach opposite conclusions. Both of them would be wrong.
The row that means three different things
The first reader says: position 44, that is page four, forget it. The second says: fifteen thousand impressions, this is the biggest opportunity on the site. Neither follows from the row.
Position 44 is not a place. Google defines it as the topmost position occupied by a link to your property in search results, averaged across all queries. It is a mean. Some of those impressions came from page two, most came from much deeper, and the average lands at 44. Nothing in the row tells you the shape of that distribution.
What the row does prove is that the demand exists and nothing on the site is answering it. That is why I recommended a dedicated page rather than a tweak. The impressions were the finding. The position was noise dressed up as a measurement.
Question one: what are we nearly ranking for?
Search Console can only answer this for queries you already appear on. If a page has never surfaced for a phrase, there is no row. There is no zero. The query simply does not exist in the report.
That is not a flaw, it is what the tool is. But it means Search Console will never tell you what your market is, only what your slice of it currently looks like. Every audit I write pairs it with something that can see outside the property.
It is also why my sweet spot filter is shaped the way it is: positions roughly 4 to 20, with enough impressions to prove demand. It is built deliberately around what Search Console actually knows. Worth being honest about one thing there: the threshold in my own audits is not consistent. A 2021 audit used positions 5 to 20 with 500 or more impressions. A 2022 one used 4 to 20 with 100 or more. The band is a judgement about how much movement is plausible on that site, not a constant. Anybody quoting you a fixed one is quoting a habit.
Question two: which keyword lost the traffic?
This is the question clients ask most often after a drop, and on a large site it frequently has no answer in Search Console at all.
Two documented limits stack up. Google does not track queries made a very small number of times or containing personal or sensitive information, and the tables show a maximum of 1,000 rows. So the clicks in the query table never sum to the clicks for the site. The gap is not a bug you can chase down.
On a small local site the gap is small and the query table is close to complete. On a classic car marketplace I audited with 9,220 pages indexed, the query table could show a thousand rows against a catalogue generating a very long tail. Most of the traffic lived in queries that were never listed individually.
So the sequence matters. Diagnose a drop at page level first, where the URLs are few enough to be complete, and only then look at queries for the pages that actually moved. Doing it the other way round means starting with the least complete data in the tool and trying to reason backwards.
What it is genuinely excellent at
Indexing. The Pages report tells you what Google has, what it looked at and declined to keep, and what it has never fetched. No third party can tell you that, and it is the first thing I check when a site should be ranking and is not. Everything in this post is a caveat on one report, not on the tool.
How I use it in an audit
- Pages report first, always. Indexing is a yes or no question and this is the only place it gets answered.
- Query data second, and only for pages that moved. Not as a starting point.
- Impressions as demand, position as a hint. High impressions with a deep average position is a content gap, not a ranking problem.
- Never quote the query total as the site total. They are different numbers and they are meant to be.
Two related habits worth naming. Crawl tools flag things that do not matter, and Search Console has the opposite failure: it under-reports rather than over-reports. And reading a crawl is the other half of the same job, because the crawler sees the pages Search Console has never heard of.
The short version
- Average position is a mean across all queries. Position 44 with 15,000 impressions is a content gap, not a near miss.
- Search Console only holds queries you already appear on. It is structurally blind to your market.
- The query table caps at 1,000 rows and rare queries are never tracked, so query clicks never sum to site clicks.
- On a large site, “which keyword dropped” often has no answer here. Diagnose at page level first.
- My sweet spot band is a judgement, not a constant. It has moved between audits and it should.
- Indexing is what it is best at. Start there and stay there longer than feels necessary.
If a site should be ranking and it isn’t, that’s the work I do. An SEO audit is where the Search Console data gets read against a crawl rather than on its own, and technical SEO covers the indexing side of it.
