How to Tell If You Appear in Google AI Overviews

01Does Search Console have an AI Overviews report yet?

Yes, and it is not quite the report people keep asking for. Google announced the Search generative AI performance report on 3 June 2026 and the help documentation now notes that the insights reached all websites worldwide on 31 August 2026, but what it gives you is impressions grouped by page, country, device and date, with no query dimension, no clicks, and no separation between AI Overviews and AI Mode.

That matters more than it sounds. The question people ask is some version of am I in the AI answer for the things my buyers ask. The new report answers a different one: which of my pages did Google's AI features link to, and how often. Both are worth knowing. Only one is now free and first party.

The launch announcement lists exactly four dimensions: pages, countries, devices and dates. If you have been waiting for a query filter that isolates Overviews the way the featured snippet filter isolates snippets, it is not in this release, and Google has not said it is coming.

02What does the generative AI report actually prove?

It proves coverage. Read as a list of pages sorted by impressions, it tells you which of your URLs Google's AI features link to at all, a fact you previously had to infer. That list is the useful artefact: it describes what Google already treats as answer material on your site.

A few mechanics matter before you read too much into a number. Google's help page for the report states that its data comes from the Web search type inside the ordinary performance report, so these impressions are already inside your overall totals. It is a view carved out of numbers you had, not a new pool of traffic. The usual limits apply too: the same thousand row cap, the same Pacific time dates, the same canonical URL assignment, and an export button for chart and table.

Chart and table totals can disagree, and that is expected rather than a bug. The chart aggregates by property, so two of your pages inside one AI answer count once, while the table grouped by page counts each. Building from the export, pick one aggregation and stay with it.

What is missing is the part that turns coverage into strategy. No query, so you cannot map an impression to a question. No click or CTR, so you cannot price the visibility. And Overviews and AI Mode are pooled as generative AI features, so you cannot tell which surface produced the number. If separating those two is what you need, how each triggers and cites is covered in our guide to AI Overviews versus AI Mode.

03Why does the low CTR workaround answer a different question?

Before the report existed, the advice was to infer Overview presence from the main performance report. It is still the most upvoted answer whenever the question comes up, and still the only query level signal available.

The workaround is sound as a trigger and unsound as a conclusion, and the reason sits in Google's own definition of position. Its documentation on impressions, position and clicks says an AI Overview occupies a single position in the results and every link inside it is assigned that same position, and that the position you see reported is the topmost position your page held, averaged across queries.

Put those two rules together and one symptom covers two opposite events.

• You are cited inside the Overview. The Overview sits above the blue links, so your reported position moves toward the top while your CTR collapses, because most people read the answer and stop.
• You are absent from the Overview. It sits above your unchanged blue link and absorbs the clicks. Your position barely moves and your CTR collapses.

Same chart, opposite meanings. One says your content is working and the click is what you lost. The other says a competitor is being read instead of you. Acting on the wrong one is expensive: you rewrite a page Google already trusts, or you celebrate a position gain that was never a ranking gain.

This is the ambiguity the new report resolves, and the honest reason to open it. It counts only pages a generative AI feature actually linked to. If the page with the collapsed CTR shows impressions there, you are in the answer. If it shows none while CTR keeps falling, you are underneath one. Use the main report to find suspects and the generative AI report to decide which story is true.

04Does an impression mean you were cited?

An impression means a link to your page was shown to someone inside a generative AI feature. Google confirms that clicking an external link in either an AI Overview or AI Mode counts as a click, and that standard impression rules apply to both. Nothing in that definition says the sentence above your link came from your page.

That distinction is the one practitioners tracking this seriously insist on, and they have language for it: cited and recommended are two outcomes, tracked separately per question. An answer that lists you third of five has cited you. One that says use this has recommended you. Search Console sees neither, only the link.

It is also worth knowing how noisy this measurement was before Google reported on it. One widely referenced experiment recruited the search community to trigger a specific Overview, logged 867 impressions, and found a click through rate of 13.5 percent from participants who had been instructed to click the citation. That write up on AI Overview tracking in Search Console is one of the few attempts to test the counting rules directly rather than assume them.

One more counting rule matters if you work with AI Mode: a follow up question inside it is treated as a new query. Multi turn conversations fragment into many small records rather than one session, and none carry the wording that produced them.

05What does the report leave you to log yourself?

The questions. Everything commercially interesting about AI visibility is phrased as a question by a buyer, and the question is exactly the field Google withholds. So the second instrument is one you run, and the method that keeps surfacing is deliberately unglamorous.

Three words in that are load bearing. Fixed, so the set does not drift toward questions you already win. Fresh, so your own history does not flatter the result. And over time, because one answer is a sample, not a rank. Practitioners in the same threads describe running a query fifteen or twenty times before believing a presence rate.

Citations are also sensitive to wording in a way rankings are not. One practitioner described a page cited for an exact error message query and absent from a near identical rephrasing. If your set contains only the phrasings you would write, you are measuring your own vocabulary rather than your buyers.

A log that supports both instruments needs six columns and no more: the question, the engine, the date, whether your domain appeared, which URL was cited, and who else was named. Add a seventh for recommended versus merely present if you sell into a comparison heavy category. For choosing what goes in the set in the first place, we wrote a longer method for picking the prompts worth tracking.

06How do you know whether any of this matters?

Nobody in these threads has solved this, and pretending otherwise would be dishonest. The most clear eyed comment on it is also the most deflating.

The page is the only join you have. The report gives impressions per URL, analytics gives conversions per URL, and that is enough to ask whether the pages carrying AI visibility ever produced anything. It will not attribute a signup to an Overview, and a tool claiming that attribution is describing a model, not a measurement.

There is also a misconception worth clearing, because it shapes how people budget for this work. It surfaces whenever someone asks whether we need a Search Console for AI answers.

That is not how it works, and the consequence is practical. Search Console is Google's record of Google surfaces. Assistants outside Google retrieve from their own indexes, which is why teams find themselves present in one engine and absent from another for the same question. If you rank on Google and still cannot find yourself in AI answers, the mismatch is itself the diagnosis, and we unpacked it in why you rank on Google but AI does not cite you.

07The smallest setup that actually works

Five steps, in this order, and the whole thing fits in an afternoon plus twenty minutes a week.

• Export the generative AI report today. History starts when the report starts, so your earliest export is your baseline. There is no archive to recover later.
• Save the pages tab as a list. These are the pages Google's AI features already link to. Their shape is your template.
• Write fifteen to twenty buyer questions. In the words a buyer would use, including the comparison and alternative phrasings where you are most likely to be replaced.
• Run them weekly in fresh sessions. Log appearance, cited URL and who else was named, and repeat each question several times before believing a presence rate.
• Join the two once a month. Ask whether the pages with AI impressions are the pages answering the questions you lose. If they are not, that gap is the work.

None of this is clever. It is two instruments pointed at two questions, kept honest about which one each can answer. The trap is treating either as the whole picture. For the content side of the same problem, see our guide to showing up in Google AI Overviews.

Frequently asked questions