Connect Google Search Console

What Search Console adds

The tracking script sees every visit that reaches your site, including the ones that came from Google. What it cannot see is the search that happened before the click — the query, how often you appeared for it, and where you ranked. That lives in Google Search Console, and connecting it closes the gap.

Once connected you get:

• The SEO page in the dashboard: organic clicks, impressions, average CTR and average position, your top queries and top pages, and the trend over time.
• A `gsc_query` tool for the Assistant and your MCP endpoint. It groups performance by query, page or date and can scope to one page or to queries containing a phrase — which is how the analyst answers "which searches bring people to /pricing?"
• SEO in Insights. The daily analysis reads your search data alongside your first-party traffic.

Connect it

1. Open Connections, expand the Google Search Console card under Recommended integrations, and click Connect Google. The SEO page’s Connect Search Console button starts the same flow. 2. Sign in with the Google account that can see your site in Search Console, and approve read-only access. 3. You land back in the dashboard with the card connected.

The connection asks Google for the read-only Search Console scope. It stores the refresh token server-side and keeps it current; you never paste a token.

Check the property

Search Console organises data by property — a URL-prefix property like https://www.example.com/ or a domain property like sc-domain:example.com. On connect we list the properties your Google account can see and pick one automatically.

If your Google account can see more than one site, check that it picked the right one. Expand the Search Console card in Connections: the property field shows what is being read, and you can correct it there. A domain property covers every subdomain and protocol, so prefer it when you have one.

Using the data

Open SEO in the sidebar for the report. Every KPI there is labelled with its source, and the page reads Search Console’s own figures — we do not re-derive them from the tracker, because the two measure different things (a search impression is not a visit).

The questions it answers best are the ones that combine sources. Ask the Assistant, for example:

• "Which queries bring people to our pricing page, and what is their average position?"
• "Which pages rank on page two for queries we get impressions on but few clicks?"
• "Did organic clicks change after we rewrote the homepage?"

The analyst pulls Search Console for the search side and the first-party analytics for what those visitors did next, and cites both.

If the SEO page stays empty

• The card says connected but the report is blank. The property is probably wrong or has no data yet — check it as above. A newly verified property takes a few days to accumulate data in Search Console itself.
• You signed in with the wrong Google account. Disconnect the card, which revokes the token, then connect again with the account that owns the property.
• The report shows an "unavailable" notice. Google refused the call — usually a revoked or expired grant. Use the notice’s link to check the connection and reconnect.

For everything else Connections can add, see Managed connectors.