How to Check If I Show Up in AI Overviews (2026 Guide)
How we check client AI Overview visibility in 2026: Search Console control and impressions first, a live SERP pass, then prompt tracking for the query GSC does not keep.
On retainers we do not start this check in ChatGPT. AI Overviews are Google. If a client asks "do we show up in AI Overviews," we open Search Console before we open an assistant. The software we run for the prompt layer GSC will not store is Promptwatch.
On retainers we do not start this check in ChatGPT, and the reason is that AI Overviews are Google, not an assistant. If a client asks "do we show up in AI Overviews," we open Search Console before we open an assistant, because the answer lives in Google's own report before it lives anywhere else. The software we run for the prompt layer GSC will not store is Promptwatch, which is the platform we run client programs on for the part Google does not save.
We follow Google's own pages: AI features, the optimization guide, the June 3, 2026 report launch, Help for the generative AI performance report and the Search generative AI control.
We follow Google's own pages for the Google half, because Google is the only source for Google's report. The AI features page, the optimization guide, the June 3, 2026 report launch, the Help page for the generative AI performance report, and the Search generative AI control page are the five links we cite when a client number comes from the Google side. Anything we put in a deck that quotes a Google number traces back to one of those five.
Week one on a property
Owner access. Settings > Search generative AI. If it is exclude, we stop the content argument. Include is default. Exclude removes links and grounding in Overviews, AI Mode, and Discover generative features. Google says it is not used as a ranking signal elsewhere. It does not equal noindex. Training limits are Google-Extended. Changes often land in 1-2 days, with cache lag. Child properties inherit unless someone overrode them. The control is still rolling out. Missing UI is not a diagnosis.
Week one on a property starts with owner access, because the control lives in Search Console settings and you need the access to read it. Settings, then Search generative AI, is where the control sits. If it is exclude, we stop the content argument, because no content work survives an exclude control and the fix is the control, not the page. Include is default. Exclude removes links and grounding in Overviews, AI Mode, and Discover generative features, which is the lever to pull for removal. Google says it is not used as a ranking signal elsewhere, so pulling it does not help you rank, it removes you. It does not equal noindex, which is a different tag. Training limits are Google-Extended, which is a separate control for a separate system. Changes often land in 1-2 days, with cache lag, so a change is not a change until the cache clears. Child properties inherit unless someone overrode them, which is the reason to check the parent before reading the child. The control is still rolling out, and missing UI is not a diagnosis, it is a rollout state.
URL Inspection on the URLs in the pitch. Indexed. Snippet allowed. Important copy in the HTML Googlebot fetched, not only in a screenshot of the designed page.
URL Inspection is the eligibility check on the URLs in the pitch. Indexed is the first condition, because a page that is not indexed cannot appear in a module. Snippet allowed is the second, because a page that is indexed but snippet-blocked cannot be grounded into a module. Important copy in the HTML Googlebot fetched, not only in a screenshot of the designed page, is the third, because a module is built from the fetched HTML, not from what the page looks like in a browser.
How we read the generative report
Impressions for AI Overviews and AI Mode. Not Search Labs. Not ChatGPT. Dimensions: page, country, device, date in Pacific Time. Two of your URLs in one module count as one property-level impression on the chart. Dotted line = preliminary. If the report is absent: too few generative impressions, exclusion, or rollout. We say that in the deck. We do not fake a number.
The generative report is the second piece of the Google path, and we read it with its limits in mind. It reports impressions for AI Overviews and AI Mode. It is not Search Labs, and it is not ChatGPT, so an assistant number does not belong here. The dimensions are page, country, device, and date in Pacific Time. Two of your URLs in one module count as one property-level impression on the chart, which is the rule that stops a buyer from double-counting a single module. A dotted line means preliminary, so the number is not final. If the report is absent, the cause is one of three: too few generative impressions, exclusion, or rollout. We say that in the deck. We do not fake a number, because a faked number in a client deck is the thing that ends a retainer.
Clicks are not a column in that dedicated report as launched. Overview link clicks can still count in the main Performance report (Web), and Google's counting help requires the link in view for an impression. We will not report impressions as clicks. August 13-17, 2026 logging error: we footnote that week.
Clicks are not a column in that dedicated report as launched, which is the gap that catches a buyer who expects a click count. Overview link clicks can still count in the main Performance report, the Web one, and Google's counting help requires the link in view for an impression. We will not report impressions as clicks, because the two are different units and a client who reads an impression as a click makes a wrong decision. August 13-17, 2026 carried a logging error, and we footnote that week rather than quote the number as clean.
Live SERP, because queries are missing
Ten commercial queries. Same market as the GBP. Screenshot whether an Overview appeared. Google says they often do not. Fan-out: a page can support a related search (the lawn-weeds example in the optimization guide). We do not fail a URL for missing the typed string if it is clearly answering a fan-out we can see in the module.
The live SERP pass is the part that fills the query gap, because the report does not store the query. Ten commercial queries, the same market as the GBP, and a screenshot of whether an Overview appeared per query. Google says they often do not, so an empty result is a common state, not a failure. Fan-out, the lawn-weeds example in the optimization guide, means a page can support a related search even when it does not match the typed string. We do not fail a URL for missing the typed string if it is clearly answering a fan-out we can see in the module, because the fan-out is a match, not a miss.
What we add after Google
Promptwatch on paid plans includes Overviews plus ChatGPT and the rest, from real UIs. We import GSC queries into Prompt Explorer and promote the ones that match pipeline, not vanity. Explore (free, 10 ChatGPT prompts) is not an Overviews audit. Essential is $95/mo. Visitor analytics (script or GTM) is for referred sessions, not a substitute for GSC impressions.
What we add after Google is the prompt layer, and Promptwatch on paid plans is the platform we run for it. Promptwatch includes Overviews plus ChatGPT and the rest, from real UIs, so the same tool holds the Google surface and the assistant surfaces. We import GSC queries into Prompt Explorer and promote the ones that match pipeline, not vanity, because a vanity query that ranks is not a pipeline query that converts. Explore, free with 10 ChatGPT prompts, is not an Overviews audit, so we do not sell it as one. Essential is $95/mo. Visitor analytics, via a script or GTM, is for referred sessions, not a substitute for GSC impressions, because a session is not an impression and the two columns stay separate.
We do not use Otterly's $29 Lite as the client-of-record Overview log. Weekly-ish data and add-on engines are fine for a side check. Profound Starter is ChatGPT-only. Wrong SKU.
We do not use Otterly's $29 Lite as the client-of-record Overview log, because weekly-ish data and add-on engines are fine for a side check but not for a log a client pays us to keep. Profound Starter is ChatGPT-only, which makes it the wrong SKU for an Overviews brief, and we name that rather than sell it.
The deliverable is three columns: GSC generative impressions, live Overview screenshot, prompt row. One slide that averages them is how QBRs go bad. We keep them separate, then we file tickets in that order: control, snippet, crawl, then content.
The deliverable is three columns, and the three columns are the structure that keeps the QBR honest. GSC generative impressions, live Overview screenshot, and prompt row are the three, and each one answers a different question. One slide that averages them is how QBRs go bad, because an average of an impression, a screenshot, and a prompt is a number that does not mean anything. We keep them separate, then we file tickets in that order: control, snippet, crawl, then content, because a content ticket cannot fix a crawl ticket and a crawl ticket cannot fix a control ticket.