Case study: how a gaming brand found 40% more query data in Search Console
A mid-size online gaming property discovered that 40% of its impressions were hidden in Google Search Console. Here is how SearchVault surfaced them and what changed when the team used complete numbers.
A mid-size online gaming property was running monthly SEO reports from Search Console data. The keyword table showed a CTR of 18% and a steady upward trend. The team was satisfied. Then they ran the same data through SearchVault.
The discovery
SearchVault reads Google's sentinel aggregate rows alongside the query-level detail. For this property, the sentinel row recorded 142,000 impressions for the period. The keyword table showed 85,000. That is a 40% gap: 57,000 impressions that Google attributed to the property but did not surface in the query breakdown.
The reported CTR of 18% came from dividing clicks by the 85,000 visible impressions. The real property-wide CTR, using the sentinel total, was 10.8%. The team had been reporting a number that overstated their click-through rate by nearly 70%.
Where the hidden impressions came from
- Long-tail queries below Google's disclosure threshold: thousands of unique searches that each generated one or two impressions. Individually small, collectively they accounted for 33% of the gap.
- Privacy-filtered queries: searches Google deemed too identifying to disclose at the keyword level. These still counted toward the property total.
- Branded misspellings and fragments: queries like partial brand names that Google grouped internally but did not surface in the export.
What changed
The team rewrote their monthly report using the sentinel-aware CTR. The board presentation went from "CTR is 18% and climbing" to "CTR is 10.8%, here is the gap, and here is what we are doing about the long tail." The conversation shifted from self-congratulation to strategy.
- Content planning prioritized long-tail clusters that were generating impressions but no visible clicks.
- Budget forecasts dropped from inflated CTR projections to realistic click estimates, which ironically made the wins look more impressive when they arrived.
- The 57,000 hidden impressions became a standing item in the monthly review, tracked for movement over time.
The takeaway
The data was always there. Google collected it, attributed it, and stored it in the property totals. The only thing missing was a tool that read the complete row instead of the truncated table. For the full methodology, see the SearchVault data methodology page or try the free CTR calculator to check your own gap.
Forty percent of this property's search visibility was invisible in Search Console. Not because Google hid it maliciously, but because the query table was never designed to be a census.
See it in action
Want to check your own data accuracy gap? Upload your Search Console export to the free CTR calculator for an instant estimate, or sign up for SearchVault to see the exact numbers using Google's own sentinel rows.