Google Search Console (Edge)

Configure Google Search Console as a Source in your Pipeline

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

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

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

4. On the Select Destination Type page, select the type of Destination you want to use.

5. On the Select Pipeline Type page, click Edge, and then click Continue.

   

   This page appears only if the selected Destination type is supported in Edge and your Team has an existing Google Search Console Pipeline with the same Destination type. Otherwise, you can proceed to create an Edge Pipeline.

6. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, Google Search Console Source.

   • In the Connect to your Google Search Console account section, click Authenticate With Google Search Console, log in to your Google account, and grant Hevo access to your account.

   • From the Sites sync mode drop-down, select whether Hevo syncs data for all sites accessible to the authenticated account, or only specific ones:

     

     • Sync all sites: Hevo syncs data for all properties accessible to your authorized Google account, including any properties added later.

     • Sync specific sites: Hevo syncs data only for the properties you select from the Sites to sync drop-down.

       

   • Historical Sync Duration: From the drop-down, select the duration for which you want to ingest existing data from the Source. This cannot be changed after the Pipeline is created. Default value: 12 months.

7. Click Test & Continue to test the connection to your Google Search Console Source. Once the test is successful, you can proceed to set up your Destination.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

Hevo ingests the following types of data from your Source objects:

• Historical Data: The first run of the Pipeline ingests historical data for the selected objects, based on the Historical Sync Duration specified when configuring the Source, and loads it into the Destination.

• Incremental Data: Once the historical load is complete, new and updated records for objects are ingested as per the sync frequency.

For the Sitemap object, Hevo ingests the entire data in subsequent Pipeline runs. For all other objects, Hevo ingests only the incremental data in subsequent Pipeline runs.

Google Search Console enforces a rate limit on the number of calls that can be made to its API in a given time period. If these limits are exceeded, a rate limit exception occurs. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records to the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

---