OuterciteOutercite

Google Search Console

What the Search Console connector brings in, what it does not, and what to do with the disagreements between search and AI visibility.

The Search Console connector puts Google's own search performance data beside your AI citation data. The value is in the disagreements.

What you'll learn

  • What flows in, and what access is requested
  • What it cannot tell you
  • The three disagreements worth acting on

What flows in

Impressions, clicks and query-level performance for the property you connect. It is Google's data, with Google's own lag and sampling, joined against your own pages in the platform.

Access requested is read-only Search Console data. Nothing else on your Google account is touched.

For the setup steps see connect Google Search Console.

What it cannot tell you

Nothing in Search Console says whether an AI engine cited you. Google does not report AI Overview appearances as a citation, and the other six surfaces are not Google at all.

This is why the two data sets sit side by side rather than being blended into a single score. A blended number would hide exactly the thing you want to see.

The three disagreements

  1. Ranks well, never cited. The most common and the most useful. Ranking proves crawlers can reach the page, so the problem is usually extraction: the answer is implied across the page rather than stated, or the content only renders after JavaScript. See Readiness.
  2. Cited, does not rank. A page engines lean on that Google does not favour. Protect it, and work out what shape it has that your other pages do not.
  3. Clicks falling, citations steady. The zero-click pattern. Your content is being used and the visit is not happening. It is the clearest possible argument for measuring citations rather than referral traffic.

Which plans

The Search Console connector is a plan feature. See plans and limits.

Keeping it healthy

Google's authorisation ends when access changes on the property. The connector shows a broken connection rather than serving stale data, so reconnect from connectors when that happens.

Try this in Outercite

After the first sync, pick your highest-impression page and check whether it appears in Sources. If it does not, that is your first structure job.

Was this helpful?

Last updated on