All articles
Data Accuracy
6 min readOctober 29, 2026

The CTR accuracy gap: why Google Search Console overstates your click-through rate

Google Search Console hides low-volume queries from its keyword table, inflating CTR. SearchVault uses sentinel rows to compute the real property-wide click-through rate, including the dark traffic GSC never shows you.

If you have ever divided your Search Console clicks by impressions and compared the result to the CTR that Google displays, you may have noticed they match. That is because Google computes CTR from the same truncated keyword table you see. The number is correct for the rows shown. It is wrong for your property.

Where the gap comes from

Google Search Console exports up to about 1,000 queries per day. Every query below a privacy or volume threshold is withheld. The impressions tied to those withheld queries still exist: Google counted them, attributed them to your property, and rolled them into the property-level total. But they are excluded from the keyword-level breakdown.

When you compute CTR from the keyword table, you divide clicks by a denominator that is missing every withheld impression. The result is mathematically higher than the real click-through rate. On a brand-heavy site, the keyword-table CTR can be 30% while the true property-wide rate is closer to 5%. That is not a rounding difference. It is a 6x overstatement.

Dark traffic: the queries Google counts but does not show

The gap between the property total and the sum of visible rows is what we call dark traffic. It is not bot traffic and it is not spam. It is real user queries that Google chose not to disclose, usually because the individual query volume was too low or because the query was privacy-sensitive.

  • A property with 100,000 daily impressions might show only 40,000 in the keyword table. The other 60,000 are dark.
  • Those 60,000 impressions still generated some clicks, but those clicks are also hidden at the keyword level.
  • The keyword-table CTR ignores 60% of the denominator and an unknown share of the numerator.

The larger the property, the bigger the gap tends to be. Enterprise sites with thousands of long-tail queries see the highest overstatement because a larger share of their traffic falls below Google's disclosure threshold.

Sentinel rows: the complete picture

Google Search Console stores a separate set of rows that are not queries. They are property-level daily totals, sometimes called sentinel or aggregate rows. SearchVault labels them __ALL__ (total across all queries) and __PAGE_AGG__ (total per page). These rows carry the complete clicks and impressions that Google attributed to the property for that day, including every withheld query.

SearchVault defaults to computing CTR from these sentinel rows: total clicks / total impressions, where both numbers include dark traffic. The result is lower than what GSC's keyword table shows, and it is the real rate. For a deeper look at how sentinel and detail rows interact, see how GSC data really works.

A practical example

Consider a property where GSC's keyword table shows 5,000 clicks on 20,000 impressions. The keyword-table CTR is 25%. But the sentinel row for the same day records 6,200 clicks on 85,000 impressions. The sentinel CTR is 7.3%. The difference is the 65,000 impressions (and 1,200 clicks) that Google attributed to queries it did not disclose.

Both numbers are real. The keyword-table figure answers "of the queries Google showed me, what share got clicked?" The sentinel figure answers "of all the queries my property appeared for, what share got clicked?" The second question is almost always the one that matters for planning.

Why it matters for decisions

  • Content ROI: if your CTR is 25%, every new ranking looks profitable. If it is 7%, the math changes.
  • Benchmarking: comparing your inflated CTR against an industry average computed from complete data makes you look better than you are.
  • Forecasting: projecting traffic from a CTR that excludes dark impressions overstates expected clicks.
  • Reporting: presenting a CTR to stakeholders that is 3-6x higher than reality creates a credibility risk when the numbers are eventually reconciled.

How SearchVault handles it

SearchVault offers a CTR mode toggle in Settings. The default mode (sentinel-aware) uses the complete property totals. The alternative mode (GSC-equivalent) reproduces the keyword-table calculation for users who need to compare directly with Search Console. Both are labelled, so there is no ambiguity about which number is on screen.

The Data Health page also surfaces the variance between sentinel totals and detail-row sums. When the gap exceeds 15%, it flags the property and explains the cause. A 20-40% variance is typical for large properties. A variance near zero means the property is small enough that Google discloses nearly all queries. For a full methodology, see the SearchVault data methodology page.

The most dangerous metric is the one that looks right. A CTR computed from an incomplete denominator is accurate for the data shown and misleading for the property.

If you are building reports or forecasts on Search Console data, it is worth checking whether the numbers you are using include the complete picture or only the visible subset. The difference is not academic. It changes the decisions.

Beyond CTR: the full data picture

CTR accuracy is one piece of the puzzle. SearchVault also pulls Link Intelligence from Google's Links API (noting that Google samples backlink data heavily), runs URL Inspection checks to surface indexing issues, and detects traffic anomalies using z-score analysis against your own 90-day baseline. The Site Health dashboard ties all of these together into a weighted composite score so you can see at a glance where your property stands. For the full technical details, see the methodology page.

Check your own gap

Upload your Search Console queries export to the free CTR calculator to see your estimated data accuracy gap instantly, or sign up for SearchVault to get exact sentinel-based numbers for all your properties.

See it with your own Search Console data

Request access and we will set up an account built around the properties you already own.