Google Search Console

Google Search Console enables you to analyze your sites’ search performance metrics. Once you have your sites’ performance data in a warehouse, you can monitor the performance and plan changes to improve your sites’ rank on Google Search.

Hevo replicates the data to your Destination in the form of report dimensions and facts. You can then use tools of your choice for monitoring, reporting, and analytics these.

Note: Hevo uses Google Search Console’s APIs to replicate the data and is subject to limits and quotas on it.

For creating Pipelines using this Source, Hevo provides you a fully managed BigQuery data warehouse as a possible Destination. This option remains available till the time you set up your first BigQuery Destination irrespective of any other Destinations that you may have. With the managed warehouse, you are only charged the cost that Hevo incurs for your project in Google BigQuery. The invoice is generated at the end of each month and payment is recovered as per the payment instrument you have set up. You can now create your Pipeline and directly start analyzing your Source data. Read Hevo Managed Google BigQuery.


  • One or more properties are added to the Google Analytics account. In Google Analytics, a property can be a website, mobile application, or blog that you want to track data for. A Google Analytics account can contain one or more properties.Please ensure that you have added the properties to your account. Please refer to this guide.

  • One or more permissions mentioned here are granted.

Configuring Google Search Console as a Source

Perform the following steps to configure Google Search Console as the Source in your Pipeline:

  1. Click PIPELINES in the Asset Palette.

  2. Click + CREATE in the Pipelines List View.

  3. In the Select Source Type page, select Google Search Console.

  4. In the Configure your Google Search Console Account page, Select an existing Google Search Console account or click + ADD GOOGLE SEARCH CONSOLE ACCOUNT.

    GSC account

  5. Select the Google account linked to the Google Search Console data, and click ALLOW to authorize Hevo to read and ingest the data.

  6. In the Configure your Google Search Console Source, specify the following:

    Google Search Console Settings

    • Pipeline Name: A unique name for your Pipeline.

    • Properties: Select the properties/sites whose performance you want to analyze.

  7. Click TEST & CONTINUE.

  8. Proceed to configuring the data ingestion and setting up the Destination.

Data replication

Default Pipeline Frequency Minimum Pipeline Frequency Maximum Pipeline Frequency Custom Frequency Range (Hrs)
1 Hr 15 Mins 48 Hrs 1-48

Note: The custom frequency must be set in hours, as an integer value. For example, 1, 2, 3 but not 1.5 or 1.75.

Objects List

Hevo ingests data for the following dimensions and facts:


  • sites

  • pages


  • site_overview_report

  • page_overview_report

  • site_report

  • page_report

  • keyword_site_report

  • keyword_page_report

  • search_appearance_site_report

  • search_appearance_page_report

  • keyword_search_appearance_site_report

  • keyword_search_appearance_page_report

Note: The position of each object is 3 days before the current day.

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination:

GSC ER Diagram

Field List

Field Name Data Type Description
__hevo_id String Hash of other fields in the table. These fields together represent a unique record in the table. E.g in page_report table, __hevo_id(date, site_id, page_id, search_type, country, device) is the hash of date, site_id, page_id, search_type, country and device. For all practical purposes, __hevo_id can be considered as a composite primary key of these fields.
average_ctr Float Click-through rate: the click count divided by the impression count.
average_position Float The location of the property or its page on the Google search results page is called its position.
clicks Integer Any click that sends the user to a page outside of Google Search is counted as a click.
country String The country where the search came from; E.g, Canada or Mexico.
date Timestamp The date for which the data was collected.
device String The type of device on which the user is searching: desktop, tablet, or mobile.
impressions Integer A link URL records an impression when it appears in a search result for a user.
last_analyzed_ts Timestamp The date of the last time a page appeared in a search result.
last_downloaded_sitemap_ts Timestamp The timestamp of the last time the sitemap was downloaded for this property.
last_submitted_sitemap_ts Timestamp The timestamp of the last time the sitemap was submitted for this property.
page_id String Hash of the page_url.
page_url String The final URL linked by a Search result.
search_appearance String Special search result feature such as a rich result type or an AMP.
search_query String The query strings that users searched for on Google.
search_type String In Google search, you can search under 3 different search types: web, image, and video search.
site_id String Hash of the site_url.
site_url String The URL of the site or property in your Google Search Console account.


  • The timestamps last_downloaded_sitemap_ts and last_submitted_sitemap_ts are not supported for Domain type properties. This is due to a limitation in the Google Search Console API.

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Oct-25-2021 NA Added the Pipeline frequency information in the Data Replication section.
Last updated on 07 Sep 2022

Tell us what went wrong