Google Search Console

Follow our setup guide to connect Google Search Console to QUANTI:

Pre-built tables and definition

---

Prerequisites

To connect Google Search Console to QUANTI, you need access to a Google Search Console account with at least one verified property.

---

Setup Instructions

1

Authorize Google Connection

• Click on Connect to Google

• You will be redirected to Google's authorization page

• Log in with your Google account credentials

• Review and accept the requested permissions

• Click Continue to grant access

2

Configure Connector

• Connector Name: Name your connector. It must be unique.

• Dataset ID: Define the ID of the dataset. It must not exist yet, as it will be created and data will be sent there.

3

Select Account(s)

• Choose the Google Search Console property (or properties) you want to sync

• Click Next

4

Select Pre-built Tables

• Review the available pre-built tables (see section below for details)

• All tables are selected by default — you can deselect tables you don't need

• Click Next

5

Finish Setup

• Define a sync period and a lookback window — Click Save

• For the first sync, you have the following options:

  • Activate auto-sync for recurring syncs based on your sync settings by clicking the switch button

  • Launch a historical data recovery by choosing your desired dates in the historical data tab

  • Launch a manual sync immediately by clicking the Sync now button

• Wait for the sync to complete. Then navigate to your data warehouse to verify that tables are populated

• Check the connector dashboard for sync status and any potential errors

---

Pre-built Tables

site_report_by_page : Search traffic data for the site. Each record shows how the site appeared in search results on a given day, with metrics aggregated by Page. Dimensions include:

• Date

• Country

• Device

• Search Type (web / image / video / news / discover / googleNews)

site_report_by_site : Search traffic data for the site. Each record shows how the site appeared in search results on a given day, with metrics aggregated by Property. Dimensions include:

• Date

• Country

• Device

• Search Type (web / image / video / news / discover / googleNews)

site_report_by_page and site_report_by_site share the same dimensions but use different aggregation methods (byPage vs byProperty). Google computes metrics differently between the two — totals may vary slightly for the same date and filters.

page_report : Search traffic data for individual pages. Each record shows how a specific page appeared in search results on a given day. Dimensions include:

• Date

• Country

• Device

• Page

• Search Type (web / image / video / news / discover / googleNews)

keyword_site_report_by_page : Search traffic data for the site based on the queries users searched for on Google. Each record shows how the site appeared for a specific search query, with metrics aggregated by Page. Dimensions include:

• Date

• Country

• Device

• Query

• Search Type (web / image / video / news / discover / googleNews)

keyword_site_report_by_site : Search traffic data for the site based on the queries users searched for on Google. Each record shows how the site appeared for a specific search query, with metrics aggregated by Property. Dimensions include:

• Date

• Country

• Device

• Query

• Search Type (web / image / video / news / discover / googleNews)

keyword_site_report_by_page and keyword_site_report_by_site share the same dimensions but use different aggregation methods. The same note on metric discrepancies applies as for the site reports above.

keyword_page_report : The most granular table — search traffic data for individual pages based on the queries users searched for on Google. Each record shows how a specific page appeared for a specific search query on a given day. Dimensions include:

• Date

• Country

• Device

• Page

• Query

• Search Type (web / image / video / news / discover / googleNews)

sitemap : Dimension table containing sitemap file metadata. Each record represents a sitemap submitted in Google Search Console, including its path, type, last submission and download dates, and the number of submitted vs. indexed URLs.

---

Pre-built tables and definition

---

Notes

• Data Availability Delay: Google Search Console data is typically available with a 2 to 3 day delay. The most recent days will not be populated immediately after a sync — this is a Google API limitation. It is recommended to configure a lookback window of at least 3 days to ensure complete and finalized data is retrieved.

• No Real-Time or Fresh Data via API: The Search Analytics API only returns finalized data. The "fresh data" available in the Google Search Console web interface (including the 24-hour view) is not exposed through the API and therefore not available in QUANTI.

• Data May Retroactively Change: Data for the last few days before finalization can change slightly as Google continues processing. This is expected behavior — the lookback window ensures these days are re-synced and updated automatically.

• byPage vs byProperty Aggregation: Google computes metrics differently depending on the aggregation type. byPage and byProperty tables for the same date and dimensions may show slightly different numbers for clicks, impressions, and position. Refer to Google's documentation for details on how each method calculates data.

• Historical Data Limit: The Search Analytics API provides data for up to 16 months of history.

• API Rate Limits: Google enforces quotas on API requests. QUANTI automatically manages these limits to ensure reliable data extraction.