What it shows
Search Console gives two kinds of totals:
- Daily totals: all clicks and impressions of the property for each day.
- Dimension totals: the sum of the query rows that Search Console shows.
Search Console does not show all queries in its query rows. Thus, the query rows usually add up to less than the daily totals. Sampling Impact shows how large this difference is.
When to use it
- Before you use query reports for a decision, to know how much of the traffic they show.
- When the query totals in a report do not match the property totals.
How to use it
- Open Optimize → Sampling Impact.
- Check the date range and search type. The default is Last 28 days and Web.
- Compare Daily Total Clicks with Dimension Clicks.
- Read Click Coverage and Impression Coverage.
- Read the Interpretation panel.
How to read the result
| Card | Meaning |
|---|---|
| Click Coverage | Dimension Clicks ÷ Daily Total Clicks × 100. If the daily total is zero, the coverage shows 100%. |
| Impression Coverage | The same calculation for impressions. |
| Unsampled Clicks | Daily Total Clicks − Dimension Clicks. These clicks have no query row. |
| Total Queries | The number of query rows in your range. |
The tool marks coverage of 95% or more as good, and 80% to less than 95% as a warning. Less than 80% is low.
Example
All data is fictional. For example.com in 28 days:
- Daily Total Clicks: 10,000
- Dimension Clicks: 6,000
- Click Coverage = 6,000 ÷ 10,000 × 100 = 60%
- Unsampled Clicks = 10,000 − 6,000 = 4,000
Thus, query reports show 60% of your clicks. A query report can show a trend correctly, but its totals are lower than your property totals.
Limits
- The tool does not show the hidden queries. No tool can get them back from Search Console.
- The tool does not tell you the cause of the difference. Hidden queries, row limits, and other Google rules can all add to it.
- The App calls the difference “Unsampled”. It is the traffic without a query row, not the result of a sample that Kong Metrics takes.