The lesson
- Take totals from the date dimension; the query report is a breakdown, and a breakdown can be incomplete
- If a number is about to drive a decision, reconcile it against a second view of the same data first
The short answer
Anonymised queries are searches that Google Search Console deliberately hides from your query report. When a search term is used by very few people, showing it could identify the person who typed it, so Google withholds the whole row. The clicks and impressions still count towards your site's true totals, but they appear in no query breakdown, in the interface or the API.
That creates a gap you can measure on any property: the performance graph and the date-grouped totals are complete, while the query table underneath them is not. On a large site the gap is a few percent. On a small or young site, where almost every query is rare, the query report can be missing almost everything.
How this caught us
This page exists because the gap cost us real analysis, on this site's own
Search Console property. Every week, an automated report pulled our organic
clicks from the Search Analytics API. We had built it the obvious way: request
the query dimension, get one row per search term, sum the clicks column.
Tidy, auditable, and wrong.
For weeks that report said zero organic clicks. Not low. Zero. We started drawing the obvious conclusion, that nothing on the site was earning clicks yet, and we began planning around it.
Then we asked the same API the same question a different way. Same property,
same 28 days, but grouped by date instead of by query: 4 clicks.
Stretch the window to 87 days and the query report still summed to zero while
the date totals showed 19 clicks. We measured this on 21 August 2026, and
those numbers are exactly what came back. Every one of the 19 was a real
person who searched, clicked, and landed.
The genuinely dangerous part is that a zero is more persuasive than a wrong number. A report saying 3 clicks when the truth is 19 invites a shrug. A report saying zero invites a strategy change.
Why Google does this
This is documented behaviour, not a bug. Google's own help notes say some queries are omitted to protect user privacy. What is easy to miss is the consequence: the withheld rows are not blanked out or bundled into an "other" bucket you can see. They are simply absent, while their clicks and impressions still count towards the property's totals. The report does not warn you. Nothing errors. You get a well-formed table that happens to be missing its subject.
How to count your clicks properly
Take headline totals from the date dimension, or from a request with no
dimensions at all. Those views are complete. Use the query and page
dimensions only for what they are: a breakdown of the portion Google is
willing to itemise.
Two habits made it stick for us:
- Totals and breakdowns come from different requests. Our reporting now sums clicks from date-grouped rows, and the query table is displayed beside that total, never summed into it.
- Reconcile the two on every pull. If the query rows sum to less than the date total, the difference is your anonymised traffic. Watching that gap is itself useful: for us it was briefly 100% of all clicks, which is a very honest description of a site with young content and no head terms.
The same class of error appears anywhere a breakdown is quietly incomplete, which is most analytics tools. It is the reason a proper technical SEO audit cross-checks its sources rather than trusting one table, and the reason we treat search intent data as directional rather than exact. Crawl Cove applies the same principle to crawling: every issue it reports links to the evidence it was derived from, because a number you cannot reconcile is a number you cannot trust.
The lesson, in one line
A breakdown is not a total. Sum the dimension that cannot hide rows, and let the query report be what it is: a partial, privacy-filtered sample.
Frequently asked questions
- What are anonymised queries in Search Console?
- They are rare searches that Google withholds from the query report to protect the privacy of the person searching. The clicks and impressions still count towards your totals, but the query text, and its whole row, never appears in the query breakdown.
- Why is my Search Console query table lower than the totals graph?
- The graph is built from complete totals, while the query table excludes anonymised queries. The gap between the two is roughly how much of your traffic comes from rare queries, which on small or young sites can be most of it.
- Does this affect the API or just the interface?
- Both. In the Search Analytics API, rows grouped by query omit anonymised queries, so summing them under-reports. Group by date, or request no dimension at all, to get true totals.
- Can I see which queries were anonymised?
- No. Google never reveals them, in the interface or the API. You can only measure their combined size: subtract the sum of your query rows from the date-dimension total for the same period.