Skip to main content
Google Search Console is a free web service offered by Google that helps you monitor, maintain, and troubleshoot your site’s presence in Google Search results. It provides insights into how your website performs in search results, including data on clicks, impressions, click-through rates, and search queries.

​
Configuring Google Search Console as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Google Search Console option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need to authorize Nekt to access your Google Search Console data. The following configurations are available:
  • Site domain: The site domain or URL to extract data from. Supports both domain properties (e.g., sc-domain:example.com or example.com) and URL-prefix properties (e.g., https://example.com/). The connector automatically normalizes and matches the provided value against available properties in your account.
  • Start date: The earliest date from which records will be synced. Used for the first run or when no previous state exists. Format: YYYY-MM-DD.
  • Lookback window (days): (Default: 3) Fixed window to reprocess data to ensure recent data from past days is processed in its entirety.
The authenticated Google account must have access to the configured site domain.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select all streams or only specific ones.
Tip: You can quickly find streams by typing their names.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
You need at least one successful source run to see the table in your Catalog.

​
Streams and Fields

Below you’ll find all available data streams from Google Search Console and their corresponding fields:
Daily Search Console performance aggregated by date.Key fields:
Daily performance segmented by user country.Key fields:
Daily performance segmented by device type.Key fields:
Daily performance segmented by page URL.Key fields:
Daily performance segmented by search query.Key fields:

​
Implementation Notes

  • All streams use incremental replication by date. On the first run (or when no replication state exists), the connector automatically falls back to the configured Start date to extract data.
  • Primary keys include stream dimensions plus site_url.
  • The connector validates that the configured domain or URL exists in the authenticated Google Search Console account before running. It automatically resolves the input by matching it across available domain properties and URL-prefix properties, stripping out protocols and prefixes when validating.
  • The connector applies the configured lookback window on every run to backfill recent days.

​
Skills for agents

Download Google Search Console skills file

Google Search Console connector documentation as plain markdown, for use in AI agent contexts.