Supermetrics Support Forum

Discrepancies in Google Search Console results

In addition to the information below, Google also changed the data freshness of the Google Search Console UI to be much faster as of Sept 23, 2019. They explicitly note that this change currently does not affect the API in their announcement article, and that will be something they will work on going forward. 

This means that recently fetched data as shown by Supermetrics, as it comes from the API, probably will not match the UI. You may have to wait several days to verify results due to the lag still present in their API. That data may also still be affected by the information below, so if you continue to have discrepancies in older results, please read on.


Usually differences in results between Supermetrics and Google Search Console are caused by the fact that Supermetrics returns all search data (web, image, video) by default, whereas Search Console displays web search only. 


If this is the case then the solution would be adding a filter: Search type EQUALS WEB


Still see a difference to expected results?

The way Google Search Console aggregates clicks and especially impressions is quite opaque. It is known that aggregation level affects the total counts heavily. These counts are meant to be interpreted as estimations.

Google has their reasons for this kind of aggregation:
- Privacy. Some queries are filtered out because they contain identifiable information.
- Technical differences between tools. We are using the Search Console API which processes data differently from the Search Console UI.
- Computation time. To get an estimate quickly, Google changes the sampling algorithm based on what dimensions you split the data with.

Sources:
- "Data discrepancies" under https://support.google.com/webmasters/answer/7576553
- "Why do I lose data when asking for more detail?" under https://developers.google.com/webmaster-tools/search-console-api-original/v3/how-tos/all-your-data


Example when filtering results:

- When filtering by page or query, the "matches" and "does not match" totals might not add up to the unfiltered total. For example, adding the totals for "Queries containing:mouse" and "Queries not containing:mouse" might not equal the total values when no query filters are applied. This is because anonymized queries are omitted, and data is truncated due to serving limitations.

Read about it on this page: https://support.google.com/webmasters/answer/7576553?hl=en


All in all, these are Google's limitations, which we can’t go around unfortunately.


Please note that this is a feature of the Search Console products only. Other Supermetrics connectors should be perfectly in line with data from native UIs.


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.