> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adriel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to connect

> How to connect the Google Search Console data source to Adriel: authorize a Google account, select a verified property, and import organic search performance.

Google Search Console exposes organic search performance for a verified domain — clicks, impressions, CTR, and average position. Connecting it brings that data into Adriel dashboards, broken down by query, page, country, device, or search appearance, queried live against the Google Webmasters API on dashboard load.

## Before you connect

The following are required:

* A Google account with verified access to the target Search Console property.
* At least one Search Console property already verified on that account — either a domain property or a URL-prefix property.

## Connect Google Search Console

<Steps>
  <Step title="Authorize a Google account">
    On the **Data Sources** page, search for **Google Search Console** and select it. Click **Sign in with Google** in the pop-up and sign in with the account that owns or is delegated to the target Search Console property. Grant every requested permission on the Google consent screen and click **Continue** — skipping a permission prevents the property list from loading.
  </Step>

  <Step title="Select the property">
    On the data source settings, select one verified property from the **Domain Name** dropdown. Both domain properties (`sc-domain:`) and URL-prefix properties (`url:`) appear, with their prefixes stripped for readability. Each data source maps to a single property; connect additional domains as separate data sources.
  </Step>

  <Step title="Submit">
    Click **Submit** to complete the connection. Initial data availability can take one to three business days due to Search Console's own pipeline lag.
  </Step>
</Steps>

## What gets imported

The connector imports four core metrics under the `searchConsole:` prefix — clicks, impressions, CTR (clicks divided by impressions), and position (average position of the topmost result) — along with non-date breakdowns for query, page, country, device, and search appearance. One non-date breakdown plus an optional date granularity can be combined per query.

For the complete list of metrics, breakdowns, and limits, see the [Google Search Console data reference](/data-sources/g-n/google-search-console/data-reference).

## Troubleshooting

<AccordionGroup>
  <Accordion title="Recent days appear empty or incomplete">
    Google Search Console has a one-to-three-day reporting lag at the top of any date range. Missing data for the last few days is expected and resolves on subsequent refreshes — no action is required.
  </Accordion>

  <Accordion title="Older historical data is missing">
    Google Search Console retains roughly 16 months of data through both the UI and the API. Queries beyond that window return no rows.
  </Accordion>

  <Accordion title="A property is missing from the dropdown">
    Only properties verified on the authorized Google account are listed. Verify ownership in the Search Console UI first, then reconnect.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Google Search Console data reference" href="/data-sources/g-n/google-search-console/data-reference">
    Metrics, breakdowns, and limits for Google Search Console.
  </Card>

  <Card title="Google Search Console FAQs" href="/data-sources/g-n/google-search-console/faqs">
    Common questions and expected behaviors for the Google Search Console data source.
  </Card>

  <Card title="How to connect Google Analytics 4" href="/data-sources/g-n/google-analytics-4/how-to-connect">
    Connect owned website and app analytics from GA4.
  </Card>

  <Card title="How to connect Google Ads" href="/data-sources/g-n/google-ads/how-to-connect">
    Connect paid search, display, video, and shopping campaigns.
  </Card>
</CardGroup>