--- title: "Google Search Console anonymized queries explained · GSC PAP" source: https://gscpap.com/guides/google-search-console-anonymized-queries updated: 2026-09-18 --- [All guides](https://gscpap.com/guides) Guide · about 6 minutes # Google Search Console anonymized queries: measure the traffic you can't see By the [GSC PAP team](https://gscpap.com/about) · Updated September 18, 2026 Pull every query row Search Console will give you, add up the clicks, and the sum comes up short of the total shown above the chart. For most sites, that gap is anonymized queries: real searches that led to your site, which Google counts but won't name. No tool can show you what those searches were. Google doesn't release the text in the interface, the API or BigQuery, and that includes GSC PAP. What you can do is measure how much of your traffic they account for, and plan your reporting around it. This guide covers both. ## What are anonymized queries in Google Search Console? Google's definition: an anonymized query is one that wasn't issued by more than a few dozen users over a two-to-three-month period. Search Console withholds the text of those queries to protect the privacy of the people who typed them, since a search almost nobody else makes could point back to the person who made it. The traffic itself is real. Those searches showed your pages and some of the searchers clicked. Search Console counts every one of those impressions and clicks; it just won't tell you which words were typed. Rare doesn't mean unimportant. Long, specific searches are individually rare, and together they can add up to a meaningful share of a site's traffic. ## Where anonymized queries are counted, and where they're missing The rule is simple once you know it: the words are always hidden, but the numbers are counted everywhere except in query rows and query filters. - Query tables: missing. Anonymized queries never appear as rows in the Performance report's Queries table or in Search Analytics API responses, and there is no "other" row that collects them. - Chart totals: counted. The total clicks and impressions above the chart include them. - Query filters: missing. Filter by query and they drop out of the totals too, so "queries containing brand" plus "queries not containing brand" adds up to less than the unfiltered total. - Page, country and device filters: counted. Only a query filter removes them from the chart total. - BigQuery bulk export: counted, without the words. Anonymized queries arrive as rows with an empty query field. ## Can you see anonymized queries in the API, BigQuery or another tool? No. The text of an anonymized query never leaves Google. The Search Analytics API leaves those rows out, BigQuery bulk export ships them with an empty query field, and every tool built on Search Console data, GSC PAP included, receives exactly what Google releases. What the API does give you is more of the queries Google is willing to name. The Performance report's table stops at 1,000 rows, while the API returns up to 25,000 rows per request and can page further. On a site with a long tail, that is thousands of named queries the interface never showed you. It is a real gain, and it is what accessing "more hidden Search Console data" can honestly mean, but none of those extra rows are anonymized queries. ## How to measure how much of your traffic is anonymized It takes one subtraction. Get the property's total clicks and impressions for a date range with no dimension selected. Then add up clicks and impressions across every query row for the same range. The difference is traffic from queries Google didn't name; divide it by the total to get your anonymized share. With GSC PAP this is one question to your AI assistant. get_performance_overview returns the property's true total for the period, and search_analytics_query returns the query rows, up to 25,000 per request, which the assistant sums and subtracts. Share of gscpap.com's Search Console traffic from anonymized queries - Impressions: 63% - Clicks: 98% gscpap.com, web search, May 2 to October 21, 2026: the property total minus the sum of every named query row. Our site is young and most of its visitors arrive through rare, long questions, which pushes the share up. It varies a lot between sites, so measure your own. - Use the API rather than the interface on anything but a small site. The Performance table stops at 1,000 rows, so past that point the sum falls short for a second reason. - Keep both numbers on the same property, date range and search type, and work out the share for clicks and impressions separately. - On very large sites, treat the result as an upper bound. The API returns at most 50,000 rows per day per site and search type, so part of the gap can be rows lost to that cap rather than anonymized queries. [![Search Console totals for the same three months, without a query filter and with a regex query filter that matches every query](https://gscpap.com/images/guides/google-search-console-anonymized-queries.webp)](https://gscpap.com/images/guides/google-search-console-anonymized-queries.webp) The same three months without a query filter, and with a Query filter that matches every query (1). Any query filter leaves out anonymized queries, so the gap between the two totals is your anonymized share, no API needed. Recreated with example data for a made-up site. ## What to do about anonymized queries You can't recover the words, but you can stop the gap from skewing your analysis. - Report traffic from totals, and label query reports as partial. Property and page totals include anonymized traffic. A query-level report describes only the named part, so say so and nobody will expect it to add up. - Measure the gap page by page. Filter the Performance report to one page (not to a query): its chart total still includes anonymized queries, while its Queries tab lists only the named ones. The pages with the biggest gap are the ones earning the most rare searches. - Treat the named queries as clues. The queries Google does show for a page are your best evidence of what the hidden ones are about, though they are not proof. - Track the share over time. Rerun the measurement every month, so a change in the share shows up as a trend rather than a surprise. - For row-level data at scale, use BigQuery bulk export. It isn't limited by the daily row cap and keeps anonymized rows with an empty query field, so you can count that traffic by day and by the other fields in the row. It needs a Google Cloud project with billing, only a property owner can set it up, and it exports only from the day you turn it on. ## Measuring your anonymized query share with Claude The prompt works in any client connected to GSC PAP. Not set up in Claude yet? [Connect GSC PAP to Claude](https://gscpap.com/integrations/claude-ai-connectors) ### The scenario Your monthly report shows organic clicks from Search Console. A colleague exported the query table, added it up, and got a smaller number, and now someone is asking whether tracking is broken. You want to explain the gap with numbers: how much of last month's traffic came from queries Google doesn't name, and whether that share moved from the month before. ### The prompt ```prompt Use the gsc-pap MCP. For https://example.com, measure how much of my search traffic comes from anonymized queries. For the last 28 days: (1) call get_performance_overview for the property's total clicks and impressions; (2) call search_analytics_query with dimensions ['query'] and row_limit 25000, paging with start_row until a page comes back empty, and sum clicks and impressions across all rows; (3) report the total, the named sum and the difference for clicks and impressions, with the difference as a percentage of the total. Then repeat for the 28 days before that and tell me whether the share moved. ``` ### What happens 1. #### Claude gets the property's true total get_performance_overview asks Search Console for the period with no dimensions, which is the same total the Performance report shows above its chart. Anonymized queries are counted in it. 2. #### Claude pulls every named query search_analytics_query returns query rows, up to 25,000 per call. If there are more, Claude requests the next page with start_row and keeps going until Google returns nothing. The interface would have stopped at 1,000 rows. 3. #### Claude does the subtraction Claude sums the query rows, subtracts them from the total, and reports the gap for clicks and impressions separately, both as raw numbers and as a share of the total. 4. #### Claude compares the two periods Running the same steps on the previous 28 days shows whether the share is steady or moving. If it jumped, Claude says which metric moved: the total, the named queries, or both. ### Outcome You end up with two numbers to put next to your query reports: the share of clicks and the share of impressions that came from queries Google doesn't name. That settles the tracking question, tells readers how much of your traffic a query-level report can describe, and gives you a baseline to check against next month. ### Where to take it next - Run the same check for one page: ask Claude for the page's daily clicks with search_analytics_query (grouped by date, filtered to that page) and its named queries with get_search_by_page_query at a high row_limit, then compare the two sums. - Ask for the share month by month across the last 16 months to see whether it is stable for your site. - Keep query-level reports honest: label them as named queries only, and take the headline traffic number from get_performance_overview. ## Frequently asked questions ### Why don't my Search Console query clicks add up to the total? Because the total counts anonymized queries and the query rows don't. In the interface there is a second reason: the table shows at most 1,000 queries. On very large sites, Google's daily row limits can drop some rows as well. ### Can the Search Console API show anonymized queries? No. The API applies the same privacy filter as the interface, so anonymized queries never come back as rows. It does return far more named queries than the interface: up to 25,000 rows per request instead of 1,000. ### Does BigQuery bulk export include anonymized queries? It includes their clicks and impressions, as rows with an empty query field, but never the query text. It is also not limited by the daily row cap. It needs a Google Cloud project with billing and a property owner to set it up, and it only exports data from the day you turn it on. ### Can GSC PAP reveal anonymized queries? No. GSC PAP reads Search Console through Google's API with read-only access, so it receives exactly what Google releases. What it can do is measure how much of your traffic is anonymized in one question, and return up to 25,000 named queries per request instead of the interface's 1,000. ### Are anonymized queries bad for SEO? No. The anonymization happens in reporting, after the search. The impressions and clicks are real and count in your totals; you just can't see the words. If your anonymized share is large, lean on page totals (filter by page, not by query), which still include that traffic. ## Other guides [All guides](https://gscpap.com/guides) [ ### AI queries in Google Search Console: how to tell people, AI Mode and agents apart Search Console mixes AI Mode follow-ups, AI agent searches and scripts into your query report. How to spot each one, with regex filters and real data. 14 min read ](https://gscpap.com/guides/ai-queries-in-google-search-console)[ ### Good position, no clicks: find the SERP features eating your CTR Ranking third and getting no clicks usually means something sits above you: an AI Overview, a featured snippet or a map pack. How to check which, query by query. 7 min read ](https://gscpap.com/guides/low-ctr-at-good-position-serp-features)[ ### Find the pages quietly losing organic traffic, before the rankings go Content decay is slow enough to miss on a dashboard. How to find the pages whose clicks keep sliding, tell decay from seasonality, and decide what to refresh. 7 min read ](https://gscpap.com/guides/find-pages-losing-organic-traffic)[ ### Traffic changed: how to compare two Search Console periods and find out why Clicks are down 18% and nobody knows why. How to compare two periods properly, avoid the three traps that fake a drop, and find the queries and pages behind it. 7 min read ](https://gscpap.com/guides/compare-search-console-date-ranges)[ ### GSC clicks vs GA4 sessions: why they differ and how to tie clicks to conversions A Search Console click and a GA4 session measure different things. Why the numbers never match, what gap is normal, and how to compare and combine them page by page. 11 min read ](https://gscpap.com/guides/correlate-organic-clicks-to-ga4-conversions)[ ### Audit Core Web Vitals across your site with AI Audit Core Web Vitals with Claude through a hosted PageSpeed Insights MCP server: Lighthouse lab data and real-user CrUX field data for your top pages. 7 min read ](https://gscpap.com/guides/audit-core-web-vitals-with-ai)[ ### Google Search Console historical data: how to keep it past 16 months Google Search Console keeps 16 months of historical data, then deletes it. Here is what it includes and how to keep it longer, from BigQuery to an archive. 8 min read ](https://gscpap.com/guides/recover-search-console-history-past-16-months)[ ### Build a weekly SEO health report with Claude Automate a weekly SEO report with Claude: one saved prompt pulls Search Console changes, quick wins, decaying pages, GA4 conversions and Core Web Vitals. 8 min read ](https://gscpap.com/guides/weekly-seo-health-report-via-claude)[ ### Bulk URL inspection in Google Search Console: diagnose indexing issues at scale Search Console inspects one URL at a time. The URL Inspection API allows 2,000 checks a day per property. How to inspect in bulk and find indexing issues. 8 min read ](https://gscpap.com/guides/diagnose-indexing-issues-bulk-url-inspection)[ ### Track keyword rankings in Google Search Console, past the 16-month limit See a keyword's position history in Google Search Console, what that average really measures, and how to keep ranking history past the 16-month limit. 6 min read ](https://gscpap.com/guides/track-keyword-rankings-over-years)[ ### How to find striking distance keywords in Google Search Console Striking distance keywords rank just off page one of Google. Find them in Search Console, pick the ones worth fixing, and learn what to change on the page. 8 min read ](https://gscpap.com/guides/find-seo-quick-wins)[ ### How to find keyword cannibalization in Google Search Console Check for keyword cannibalization in Google Search Console: find queries where your pages compete, judge whether it hurts, and fix the cases that do. 8 min read ](https://gscpap.com/guides/detect-keyword-cannibalization) ### Tools that automate this workflow The MCP exposes 36 tools across 9 categories. These are the ones most relevant to this page: - [get_performance_overview](https://gscpap.com/tools#get_performance_overview) · High-level performance snapshot for a site: clicks, impressions, CTR, position over the last N days. - [search_analytics_query](https://gscpap.com/tools#search_analytics_query) · Run any Search Analytics query with full dimension and filter support, identical to what you'd hit the GSC API for, but inline in chat. - [get_search_by_page_query](https://gscpap.com/tools#get_search_by_page_query) · Drill into a specific page to see which queries drive its traffic, impressions, and average position. [Browse all 36 tools](https://gscpap.com/tools) ### Connect your Google account in 60 seconds One Google sign-in, one bearer token, one config paste. That's the entire setup. We do the OAuth dance, encrypt your refresh token, and call the Search Console API on your behalf. Your AI client only ever sees the tools. [Sign in with Google](https://app.gscpap.com/login) Read-only Search Console scope, revoke anytime Want a guide for a workflow we have not covered? Email [support@gscpap.com](mailto:support@gscpap.com).