Skip to main content

Google Search Console

This connector captures data from Google Search Console into Flow collections via the Google Search Console API.

It is available for use in the Flow web application. For local development or open-source workflows, provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.

This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system. You can find their documentation here, but keep in mind that the two versions may be significantly different.

Supported data resources

The following data resources are supported:

  • Search analytics: all fields
    • This resource contains all data in for your search analytics, and can be large. The following five collections come from queries applied to this dataset.
  • Search analytics by country
  • Search analytics by date
  • Search analytics by device
  • Search analytics by page
  • Search analytics by query
  • Sitemaps
  • Sites

By default, each resource is mapped to a Flow collection through a separate binding.

Custom reports

In addition to the resources listed above, you can add custom reports created with the Google Analytics Search Console integration. You add these to the endpoint configuration in the format {"name": "<report-name>", "dimensions": ["<dimension-name>", ...]}. Each report is mapped to an additional Flow collection.


Custom reports involve an integration with Google Universal Analytics, which Google will deprecate in July 2023.


There are two ways to authenticate with Google when capturing data from Google Search Console: using OAuth2, and manually, by generating a service account key. Their prerequisites differ.

OAuth2 is recommended for simplicity in the Flow web app; the service account key method is the only supported method using the command line.

Using OAuth2 to authenticate with Google in the Flow web app

You'll need:

You'll use these credentials to log in to Google in the Flow web app.

Authenticating manually with a service account key

You'll need:

  • A Google service account with:
    • A JSON key generated.
    • Access to the Google Search Console view through the API.

Follow the steps below to meet these prerequisites:

  1. Create a service account and generate a JSON key You'll copy the contents of the downloaded key file into the Service Account Credentials parameter when you configure the connector.

  2. Set up domain-wide delegation for the service account.

    1. During this process, grant the OAuth scope.


You configure connectors either in the Flow web app, or by directly editing the catalog specification file. See connectors to learn more about using connectors. The values and specification sample below provide configuration details specific to the Google Search Console source connector.



The properties in the table below reflect the manual authentication method. If you're working in the Flow web app, you'll use OAuth2, so many of these properties aren't required.

/credentials/auth_typeAuthentication TypeSet to Service for manual authenticationstringRequired
/credentials/service_account_infoService Account JSON KeyThe JSON key of the service account to use for authorization.Required
/credentials/emailAdmin EmailThe email of your Google Workspace administrator. This is likely the account used during setup.
/custom_reportsCustom Reports (Optional)A JSON array describing the custom reports you want to sync from Google Search Console.string
/end_dateEnd DateUTC 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.string
/site_urlsWebsite URLThe URLs of the website properties attached to your GSC account.arrayRequired
/start_dateStart DateUTC date in the format 2017-01-25. Any data before this date will not be replicated.stringRequired


/streamStreamGoogle Search Consol resource from which a collection is captured.stringRequired
/syncModeSync ModeConnection method.stringRequired


This sample specification reflects the manual authentication method.

auth_type: Service
service_account_info: <secret>
start_date: 2022-03-01

- resource:
stream: sites
syncMode: full_refresh
target: ${PREFIX}/sites