Connect Google Search Console

Search Console tells you what happened in traditional search. Outercite tells you what happens in AI answers. The interesting part is where they disagree, and that only shows up when both are in one place.

What you'll learn

• What connecting gives you, and what it does not
• How to connect, and what access is requested
• The three disagreements worth looking for

Before you start

You need to be verified as an owner or a full user of the property in Search Console. Read-only access is all Outercite asks for, but Google requires you to already have standing on the property to grant it.

Connect it

1. Open connectors.
2. Start the Google Search Console connection.
3. Authorise with Google. The access requested is read-only Search Console data, nothing else.
4. Pick the property. If you have both a domain property and a URL-prefix property, pick the domain property.
5. Wait for the first sync.

What flows in

Impressions, clicks and query-level performance from Search Console, joined against your own site data in the platform. It is Google's data, so it carries Google's own lag and sampling.

It is not an AI signal. Nothing in Search Console tells you whether an engine cited you, which is why the two data sets sit side by side rather than being blended into one score.

The three disagreements worth looking for

1. Strong in search, absent from AI answers. The most common and the most actionable. The page ranks, so access is fine, which points at Structure: the content is probably not extractable as a passage, or it only exists after JavaScript runs. See Readiness.
2. Cited by AI, invisible in search. A page an engine leans on that Google does not rank. Protect it, and understand what shape it has that the others do not.
3. Traffic falling while citations hold. The zero-click pattern. Your answers are being used and the visit is not happening. That is an argument for measuring citations, and an argument against judging AI visibility by referral traffic.

Keeping it healthy

Google's authorisation expires or gets revoked when someone changes access on the property. The connector will show the connection as broken rather than quietly serving stale data. Reconnect from the same page.

Try this in Outercite

After the first sync, find a page with strong Search Console impressions and check whether it appears in Sources. If it does not, you have found your first structure job.

Related