The one report only the owner can see.

What can Search Console tell you about AI visibility?

It is first-party, it is free, and it is the only place a business can see how its own pages performed in Google's surfaces rather than how somebody's sample said they performed. For anything that touches search exposure, it is the ground truth and everything else is an estimate.

The setting that has no external symptom

Google exposes a setting covering generative AI features. Turned off, a site can be removed from AI Overviews, AI Mode and generative surfaces while rankings, impressions and clicks continue exactly as before.

That combination is what makes it dangerous. Nothing on the website changed, so nothing on the website reveals it. No crawl finds it, no external audit finds it, no score moves. A site can pass every check anybody runs and still be excluded from the surfaces the work was paid to influence, and the only way to know is for somebody with owner access to look.

This is the strongest single argument for verified access being part of the engagement rather than a nice-to-have. It is also why an evaluation run from outside, including our own free one, has to describe its own blind spot instead of implying completeness.

What else is worth reading there

• Query drift. Not the ranking, the vocabulary. When the words people use to describe the problem stop matching the words the business uses to describe the answer, that shows here first.
• Coverage and indexing state for the pages that carry the answers, which is the difference between a page existing and a page being eligible to be retrieved.
• Which pages actually earn exposure, which is regularly not the ones the business assumes, and is the honest input to what to write next.

The caution that comes with it

Search Console reports Google. It says nothing about other assistants, and treating it as a complete picture of AI visibility is a category error in the other direction. It also cannot be read at all if verification lapses, which happens quietly during site migrations and hosting changes.

A verification that has lapsed is a blackout, not a low number, and it gets reported as one: not observable rather than zero. Restoring it is usually the highest-value ten minutes available on an account, because it turns a guess back into a measurement.

The day a site migrates, check this first

Verification lapses during exactly the events that most change visibility: a redesign, a host move, a domain change, an agency handover. Two details save most of the pain.

• A domain property is verified by DNS, and only by DNS. A file or a meta tag will verify a URL-prefix property and will not verify the domain-level one, so a business can hold verification that covers less than it appears to and lose it the moment a subdomain or protocol changes.
• The old property keeps the history. Removing it during a tidy-up throws away the only record of what performance looked like before the change, which is the one comparison the migration needs.

Neither is difficult. Both are usually discovered weeks later, when somebody asks whether traffic dropped and the answer is that nobody can tell.