Documentation Index

Fetch the complete documentation index at: https://docs.supermetrics.com/llms.txt

Use this file to discover all available pages before exploring further.

Good to know about Google Search Console

Prev Next

This article outlines recommendations and notes certain limitations imposed by the data source API, which you may need to consider when building your queries.

If you are connecting to this data source, please follow the instructions in our connection guide, and the available fields for this connector are listed in the metrics and dimensions documentation.

Request limit: See Google’s documentation for usage limits

API delay: 2 days

Recommended refresh window: 4 days

Historical range

With the Google Search Console data source connector, the data is available for the last 16 months.

Accounts in Google Search Console

In the Google Search Console connector, each Site is considered a separate account within the connection.

Your Supermetrics subscription determines the number of data source accounts you can use simultaneously.

Things to consider

Inconsistencies in Google Search Console and Supermetrics

In several cases, the main part of the table details in the Google Search Console UI does not align with the API. However, if you check the pop-up that appears when you hover on the graph, those daily details are correct and match the API. We’re not clear why this is the case, but if there are discrepancies with no other explanation, validate against the pop-up version of the data rather than the table view. If that matches, report the UI issue to Google to resolution.

Using the Path dimension changes impression aggregation

The Path dimension can produce different impression totals than what you see in Google Search Console.

This happens because Path strips out URL parameters, or everything after the "?", before aggregating the data. Google Search Console's Pages report, on the other hand, shows the full URL. For example, if www.foo-bar.com?utm_source=google&utm_medium=cpc has its own impressions in Google Search Console, that traffic gets folded into the homepage path (/) when you aggregate by Path. As a result, the impression count for / can end up higher than what Google Search Console shows for the homepage alone.

More resources