Skip to main content

Google search console

Prerequisites

  • A verified property in Google Search Console
  • Enable Google Search Console API for GCP project at GCP console
  • Credentials to a Google Service Account (or Google Service Account with delegated Domain Wide Authority) or Google User Account
note

Since Google has deprecated certain OAuth workflows, OAuth isn't supported for this connector at this time.

Setting up the Google search console connector

NoItemRequiredExampleNotes
1Website URL PropertyYeshttps://example1.com/
sc-domain:example2.com
The URLs of the website property attached to your GSC account. Read more here.
2Start DateYes2021-01-01UTC date in the format 2017-01-25. Any data before this date will not be replicated.
3End DateNo2021-12-12UTC date in the format 2017-01-25. Any data after this date will not be replicated. Must be greater or equal to the start date field.
4Authentication TypeYes
5Custom ReportsNoA JSON array describing the custom reports you want to sync from Google Search Console. See the docs for more information about the exact format you can use to fill out this field.

Tables in the Google search console connector

NoTable NameColumnsPrimary KeysRead ModeInc. Sync KeysAPI Info
1search_analytics_by_country8Full Refresh, Incrementaldate
2search_analytics_by_page8Full Refresh, Incrementaldate
3search_analytics_by_date7Full Refresh, Incrementaldate
4search_analytics_by_device8Full Refresh, Incrementaldate
5search_analytics_by_query8Full Refresh, Incrementaldate
6sitemaps9Full RefreshAPI Reference
7sites2Full RefreshAPI Reference
8search_analytics_all_fields11Full Refresh, Incrementaldate

Table: search_analytics_by_country

NoColumn NameTypeNotes
1dateVARCHARIncremental sync key
2ctrDOUBLE
3countryVARCHAR
4site_urlVARCHAR
5clicksINTEGER
6impressionsINTEGER
7positionDOUBLE
8search_typeVARCHAR

Table: search_analytics_by_page

NoColumn NameTypeNotes
1dateVARCHARIncremental sync key
2ctrDOUBLE
3site_urlVARCHAR
4clicksINTEGER
5pageVARCHAR
6impressionsINTEGER
7positionDOUBLE
8search_typeVARCHAR

Table: search_analytics_by_date

NoColumn NameTypeNotes
1dateVARCHARIncremental sync key
2ctrDOUBLE
3site_urlVARCHAR
4clicksINTEGER
5impressionsINTEGER
6positionDOUBLE
7search_typeVARCHAR

Table: search_analytics_by_device

NoColumn NameTypeNotes
1dateVARCHARIncremental sync key
2ctrDOUBLE
3site_urlVARCHAR
4clicksINTEGER
5impressionsINTEGER
6positionDOUBLE
7search_typeVARCHAR
8deviceVARCHAR

Table: search_analytics_by_query

NoColumn NameTypeNotes
1dateVARCHARIncremental sync key
2ctrDOUBLE
3site_urlVARCHAR
4queryVARCHAR
5clicksINTEGER
6impressionsINTEGER
7positionDOUBLE
8search_typeVARCHAR

Table: sitemaps

NoColumn NameTypeNotes
1pathVARCHAR
2lastSubmittedVARCHAR
3contentsVARCHAR
4warningsVARCHAR
5isPendingBOOLEAN
6typeVARCHAR
7lastDownloadedVARCHAR
8isSitemapsIndexBOOLEAN
9errorsVARCHAR

Table: sites

NoColumn NameTypeNotes
1permissionLevelVARCHAR
2siteUrlVARCHAR

Table: search_analytics_all_fields

NoColumn NameTypeNotes
1dateVARCHARIncremental sync key
2ctrDOUBLE
3countryVARCHAR
4site_urlVARCHAR
5queryVARCHAR
6clicksINTEGER
7pageVARCHAR
8impressionsINTEGER
9positionDOUBLE
10search_typeVARCHAR
11deviceVARCHAR

External Resources

Zipstack Cloud features a powerful SQL querying engine on top of many types of connectors, including those from Trino, some custom connectors and connectors from the open source Airbyte project. Some Zipstack cloud connectors are designed to utilize and expand upon Airbyte's connector protocol, but they do not use Airbyte's EL core. Additionally, some parts of the documentation for these connectors have been adapted from the connector documentation found in Airbyte's open source project.