Google's Own Tools for AI Search Visibility: What Search Console Shows and What It Can't

Google's first-party answer to "how am I doing in AI search" lives in Search Console. As of October 2026 it has two parts: a generative AI performance report and an AI features inclusion control. Neither has an API. Everything else Google offers is a crawl or index control you already know from classic SEO.

That follows from how Google defines eligibility. Its AI features documentation says a page must be "indexed and eligible to be shown in Google Search with a snippet" to appear as a supporting link in AI Overviews or AI Mode. It adds: "There are no additional technical requirements." The same page warns that "Indexing and serving isn't guaranteed."

Google's AI optimization guide goes further. It says you don't need to create new machine readable files, AI text files, markup or Markdown to appear in Google Search, including its generative AI features. So the useful Google toolset for AI visibility is short: Search Console, URL Inspection, robots.txt and robots meta tags.

The practical consequence: there is no separate "Google AI SEO tool" to install. The work is reading the two new Search Console features correctly and keeping your pages eligible.

The generative AI performance report shows impressions for your pages in AI Overviews and AI Mode. Google announced it on June 3, 2026. The documented dimensions are pages, countries, dates and devices. Google described additional metrics only as a future intention.

A few facts shape how you read it:

• It counts impressions and nothing else. There is no click, CTR or position metric in the report.
• It sits outside the Search Analytics API. You can't pull it into a dashboard automatically, which is why AI visibility tools can't read it. Export it by hand.
• Availability has been uneven. Google's help page still describes a rollout to a subset of website owners, while the report itself completed global rollout around August 11, 2026. If it's absent from your account, see why the generative AI report may be missing.

The report answers one question well: did Google show any of my pages inside an AI Overview or AI Mode answer, on which dates, in which countries, on which devices. For a step-by-step walkthrough of the screens, use the generative AI report playbook.

The gaps matter more than the numbers, because they decide what you can claim to your boss or client.

• Whether AI visibility produced traffic. With impressions only, Google's own report can't connect an AI Overview appearance to a visit.
• Where you appeared in the answer. There is no position data. Google also says third-party tools don't have access to its internal ranking data, so no one has ground truth to validate an "AI rank" against.
• Which searches triggered you. Queries are not among the documented dimensions. Check whether Search Console shows the searches behind AI Overview impressions before building a report around them.
• What the answer said about you. An impression doesn't show whether the AI stated your price, product or category correctly.
• The Gemini app. The report covers AI Overviews and AI Mode. The Gemini app is a separate product with separate controls.
• Other engines. ChatGPT, Perplexity, Claude and Copilot are outside Google's tools entirely.

Data quality is a gap too. A confirmed Google-side bug depressed impressions in both the Search and generative AI performance reports from roughly August 12 to 13, 2026. Any trend that spans that window needs a check before you trust it. If your line fell then, start with why AI impressions can drop suddenly.

What it means: treat the report as a presence signal, not a performance measure.

The second Search Console feature is a switch, and it's the one that can quietly cost you everything.

Inclusion is opt-out. Google describes it as the default control for all properties, so no action is needed to be eligible. The control covers AI Overviews, AI Mode and generative AI features in Google Discover, and Google says it expects to update that list over time. Like the report, it's rolling out to a subset of owners, so many properties don't show a toggle yet.

Three details make it risky:

1. Child properties inherit. The default for a child property is to inherit the parent's setting. One opt-out on a parent can remove several sites from AI features at once.
2. It's invisible from outside. No crawler can see it. Only someone with Search Console access can check it.
3. It overrides everything else. A property that is opted out stays out of AI Overviews and AI Mode no matter how well its pages are built.

Google says the control isn't used as a ranking or inclusion signal for other parts of Search. It's also separate from training, which Google-Extended governs. Opting out of display doesn't stop Google using your content to power Search as a whole, for example to understand the language of queries.

There is no robots.txt token for AI Overviews or AI Mode. Google treats AI as built into Search, so Googlebot directives are the crawl control. For the full picture, see what you can and can't block in Google AI Mode.

Google's AI surfaces respond to the same levers as Search, and all of them work by removing blocks. None of them adds visibility.

The snippet controls are documented in Google's robots meta tag specification. Google-Extended is documented on its common crawlers page, which says it doesn't affect inclusion in Google Search.

What you don't control: whether an AI Overview triggers for a query, which eligible page Google picks, and whether an indexed page gets served at all. One thing you can skip worrying about on Google: Googlebot renders JavaScript, so client-side rendering matters less here than it does for most other AI crawlers.

Work from the gates that can exclude you to the numbers that describe you.

1. Confirm index eligibility. Run URL Inspection on your money pages: pricing, product, comparison and about. The URL Inspection API allows 2,000 queries a day per property if you need scale.
2. Look for accidental suppression. Search templates and headers for noindex, nosnippet, max-snippet:0 and data-nosnippet. These often arrive from a template someone edited to hide a banner.
3. Check the inclusion control on every property. Include parent properties, and note which children inherit.
4. Check robots.txt for Googlebot. Decide on Google-Extended separately, knowing it governs Gemini training and grounding, not AI Overviews.
5. Read the generative AI report monthly. Record which pages earn impressions, by country and device. Mark the mid-August 2026 bug window on any chart.
6. Fill the gaps Google leaves. Google can't show you what the answer says or how other engines describe you. The free checker on this site runs up to three buyer questions as a one-off snapshot, which is a quick way to see that side.

When you present the results, label which numbers are Google's measurements and which are estimates. The guide to reporting AI visibility to your CEO shows how to frame impressions without overstating them.

• Reading impressions as traffic. An AI Overview impression proves you were shown. It says nothing about visits or revenue.
• Trusting a trend across August 2026 without checking. The Google-side bug from around August 12 to 13 can look like a loss you didn't suffer.
• Quoting the help page on availability. It still says "subset" while the report rolled out globally around August 11, 2026.
• Blocking Google-Extended to leave AI Overviews. It doesn't do that. Use the inclusion control, or Googlebot and snippet directives.
• Forgetting inheritance. A child property can be excluded by a parent setting nobody remembers changing.
• Adding schema or an llms.txt to get into the report. Google says structured data isn't required for generative AI search, and its guide says Search ignores AI text files. Ahrefs' matched-control test found AI Overviews citations fell 4.6% on pages after adding schema. Existing markup does no harm, but it isn't a lever for AI answers.
• Buying an "AI position" metric for Google. Google exposes impressions only, so no position data exists to check such a number against.

Can I pull the generative AI report through the Search Console API? Not as of October 2026. The Search Analytics API covers classic Search performance (impressions, clicks, CTR, position and query) but not the generative AI surface. The generative AI report lives in the Search Console interface only. If you need the data in a dashboard, export it manually on a fixed schedule, for example monthly, and keep the raw exports so you can recheck any period affected by a Google-side reporting bug.

Will opting out of AI features hurt my normal Google rankings? Google says the inclusion control isn't used as a ranking or inclusion signal affecting other parts of Search. Opting out removes your property from AI Overviews, AI Mode and Discover generative AI features. It does not stop Google using your content to power Search as a whole, such as understanding the language of queries. It is also separate from training, which Google-Extended controls.

Does blocking Google-Extended remove my site from AI Overviews? No. Google-Extended controls whether your content is used for training and grounding in Gemini Apps and Vertex AI. Google states it does not affect a site's inclusion in Google Search and is not a ranking signal. AI Overviews and AI Mode are part of Search, so the controls there are Googlebot directives in robots.txt, noindex and snippet directives, and the Search Console inclusion control.

How can I see AI Overviews for specific queries if Search Console won't show them? Third-party SERP tools can capture the AI Overview Google shows for a given query, location and language. That's a sample of what Google displays, not Google's internal data, and an AI Overview doesn't appear on every results page. 99Visibility's free [AI Overview Checker](https://www.99visibility.com/tools/ai-overview-checker) shows whether one appears for a query and which sources it cites. Use it alongside the Search Console report, not instead of it.

Does the generative AI report include the Gemini app? No. The report covers AI Overviews and AI Mode in Google Search. The Gemini app is a separate Google product, governed by different controls, including Google-Extended for training and grounding. Google also states that AI Overviews and AI Mode may use different models and techniques, so even within Search the two surfaces can cite different pages for similar questions.