An anonymised query is a search term that Google Search Console counts but does not show, because so few people searched for it that listing it could help identify them. The clicks and impressions from these queries are included in your totals but left out of the queries table.
How anonymised queries work
Search Console’s Performance report shows clicks, impressions, click-through rate and average position for your site in Google Search. Before it shows any query text, Google applies a privacy rule: searches made by only a small number of people over a period of a few months are withheld. Google does not publish an exact threshold.
The effect shows up in three places:
- The chart total includes anonymised queries but the queries table does not, so the rows never add up to the total.
- When you filter by query, for example to searches containing your brand name, anonymised queries drop out altogether, so filtered totals understate the true figure.
- The pages table still includes anonymised traffic, which is why a page can show more clicks than all its listed queries put together.
This is a separate issue from the interface’s row limit. The Search Console interface shows up to 1,000 rows and the API returns more, but neither shows the text of anonymised queries. The bulk data export to BigQuery marks anonymised rows explicitly, so you can measure exactly how much of your traffic they account for.
Why it matters
Anonymised queries are the far end of the long tail, and for many UK small businesses the long tail is where the customers are. A search like “boiler service near Crystal Palace on a Saturday” or “employment solicitor for NHS staff in Bristol” is rare on its own, but together such searches can add up to a meaningful share of clicks. A business that only reads the queries table can conclude that its search traffic comes from a few broad terms and plan content around those, missing the specific needs that bring in enquiries.
Hidden queries also confuse reporting. Brand and non-brand splits built with query filters leave out the anonymised traffic, which is mostly non-brand, and comparisons between Search Console and GA4 look worse than they are. I cover the wider problem in why Search Console and GA4 disagree.
Common mistakes
- Adding up the queries table and treating the result as total organic search traffic.
- Building brand versus non-brand reports from query filters without noting that anonymised queries are missing from both.
- Assuming the hidden traffic is a tracking fault or a Search Console bug.
- Planning content only around visible broad terms and ignoring the specific, low-volume searches that often convert best.
- Confusing it with “(not provided)” in older Google Analytics reports, which came from Google hiding organic keywords from analytics tools altogether.
How to act on it
Measure the gap first. In the Performance report, note total clicks for the last three months, export the queries table and compare its sum with the total. For a fuller answer, set up the bulk data export to BigQuery, which flags anonymised rows directly.
Then look at the pages that carry most of the hidden traffic. Their content, their titles and the visible queries they rank for tell you what kind of long-tail searches they attract, even when the exact words are hidden. Use that to strengthen those pages with the details searchers want, such as areas covered, prices and specific services.
Search Console is one input when I carry out keyword research for UK businesses; tool estimates, competitor pages and the questions customers ask on the phone fill in what Google keeps private.