Why can't AI visibility tools pull Search Console's AI report?

Google built the generative AI report into the Search Console interface and stopped there. As of October 2026, no endpoint returns it. The Search Analytics API, which tools use to pull classic Search clicks, impressions, CTR and position, does not expose the AI Overviews or AI Mode surface.

So an AI visibility tool has three options for Google's AI surfaces:

• Ask you to export the report by hand and upload it.
• Run its own queries against Google and record what appears, which measures the prompts the tool chose, not your real traffic.
• Show a number it modelled and label it as Google data. That last one is the one to watch for.

The report itself is also narrow. It shows impressions for AI Overviews and AI Mode. It does not show clicks, CTR or position. Google announced the report on 2026-06-03 and described extra metrics only as a future intention. If you want the full tour of what the screen shows, see our walkthrough of the generative AI report.

The report answers one question well: did Google show pages from this property inside an AI Overview or AI Mode answer, and how often. You can slice that by four dimensions.

That gap matters. Google's own first-party AI reporting cannot tell you whether AI visibility produced a visit. We cover the click question in whether you can see AI Overview clicks in Search Console, and the query question in whether Search Console shows which searches triggered AI Overview impressions.

Keep the two surfaces apart in your head too. Google's AI features documentation says AI Overviews and AI Mode "may use different models and techniques" and can return different links. A blended impressions number hides that. The report also does not cover the Gemini app, which Google governs through a separate control, Google-Extended.

Until Google ships an API, a repeatable manual routine is the honest substitute. Do it on a fixed schedule so periods line up.

1. Open Search Console and select the property. If you can't find the report, check why the generative AI report may be missing.
2. Open the generative AI performance report and set a fixed date range, for example the last full calendar month.
3. Work through each dimension tab: pages, countries, dates, devices. Each tab is a separate table.
4. Use the report's export option if your view offers one. If not, copy each table into a spreadsheet.
5. Name files with property, dimension and date range, and store them in one folder.
6. Repeat for every property you own, including child properties.

Then note anything unusual about the window. Google confirmed a bug that depressed impressions in both the Search and generative AI performance reports from roughly 2026-08-12/13. Any trend that crosses those dates needs a flag. Our page on sudden AI impression drops covers how to tell a reporting fault from a real change.

A clean export of zero impressions has several possible causes, and only some of them are about content.

• Not eligible. Google's AI features page says a page must be "indexed and eligible to be shown in Google Search with a snippet" to appear as a supporting link. noindex, nosnippet or max-snippet:0, documented in Google's robots meta tag specification, all remove that eligibility.
• Opted out. Inclusion in Google's generative surfaces is the default, but a Search Console control can switch it off. Child properties default to inheriting from the parent, so a property can be excluded without anyone touching it. Run an audit of inherited AI controls before you trust a zero.
• No trigger. AI Overviews often do not appear for a query at all. Zero can simply mean Google rarely showed an AI answer for the searches that reach you.

None of these show up in an API pull even if one existed. Each is a thing to check, not a finding.

Treat the manual export as your one first-party Google AI signal and stop paying for numbers that claim more.

• Export monthly and keep raw files, so you can rebuild any trend later.
• Reject AI rank figures for Google. No position data exists in Google's report, so nothing can validate them.
• Add Bing. Bing Webmaster Tools' AI Performance report shows citations and grounding queries for Copilot. It is also interface-only for now, as covered in whether Bing's AI Performance report has an API. First-party counts can see far more than prompt samples: in Otterly's 2026 experiment, Microsoft's report credited one site with 42,817 citations while Otterly's prompt tracker logged 3,934, though the time windows may not match.
• Use APIs where they exist. ChatGPT, Claude and Perplexity APIs expose retrieved and cited sources, which you can log separately.

For a quick outside view, the free checker on this site shows whether AI engines name you for up to three buyer questions. It is a snapshot, not a replacement for your own Search Console export.