Google AI Overviews and AI Mode Links and Citations: Official Documentation
Official Search Central docs on AI Overviews and AI Mode links: snippet eligibility, query fan-out, GSC impressions. We rank Promptwatch for the prompt GSC does not store.
Google AI Overviews and AI Mode links and citations are documented on Search Central, not on a GEO vendor homepage. The official pages are AI features and your website and Optimizing your website for generative AI features on Google Search. This post restates those docs, then ranks what still sits outside Search Console. The reason for the split is that Google documents its own surfaces, and its own surfaces are a subset of the places a buyer now gets an answer. Reading the docs first keeps the rest of the stack honest about what it can and cannot claim.
What Google says about links
AI Overviews give a gist and a jumping-off set of links. They fire when Google thinks they add something beyond classic results. They often do not fire. AI Mode is the longer comparison surface. Both may use query fan-out: extra related searches that pull more supporting pages. Google's lawn-weeds example fans out into herbicides, chemical-free removal, and prevention. A supporting link can match a fan-out, not the typed query. That detail matters for anyone tracking citations, because a page that earns a link on a fan-out sub-query will look like it ranked for a query nobody typed, and it did, on the fan-out.
Overviews and AI Mode may use different models, so the links will not always match. A page that appears in an Overview can be absent from AI Mode on the same typed query, and the reverse is also true, which means a single check is not a measurement of either surface.
Eligibility: the page must be indexed and eligible to appear in Search with a snippet. The AI features page says there are no additional technical requirements. The optimization guide also says a site must be included in Search generative AI features in Search Console to be eligible for those features. The two statements sit on different pages and describe different halves of the same gate, so both have to hold for a page to show up.
There is no special Overview schema. Structured data still helps rich results when it matches visible text. Search does not use llms.txt. Google says you can ignore chunking, synonym farms, and inauthentic mention campaigns for Search. The "ignore" list is as useful as the "do" list, because it names the tactics that waste time and do not move the Overview needle.
Google also says clicks from result pages that include Overviews have been higher quality (people spend more time on the site). That is Google's wording. It is not a CTR series in that documentation. Treating it as a number is the mistake, because the documentation gives a qualitative claim and not a series you can plot.
Official measurement vs the prompt row
| What you want | Official Google source | In the June 2026 announcement list? | |
|---|---|---|---|
| Impressions in Overviews / AI Mode / generative Discover | Generative AI performance reports | Yes | |
| Pages, countries, devices (Search), dates | Same report | Yes | |
| Clicks, CTR, the query, competing URLs in the module | Not in that announcement list | No | |
| ChatGPT / Perplexity / Gemini-app citations | Not Google | No |
The table is the honest version of what GSC does and does not store. The rows marked No are the rows a GEO program still needs, and they are the rows that have to come from somewhere other than Search Console. Reading the table row by row is how you avoid the two opposite errors: expecting GSC to give you the query (it does not), and expecting a tracker to give you Google impressions (it cannot).
Preview controls: nosnippet, data-nosnippet, max-snippet, noindex. robots.txt for Googlebot is the crawl control. Google-Extended is not a surgical Overview off-switch. The distinction is that Google-Extended governs whether your content trains Gemini, not whether it appears in a Search Overview, and conflating the two produces a robots.txt that blocks the wrong thing.
After the docs, what this directory ranks
GSC remains the impression system of record for Google. For the prompt-level citation log, including ChatGPT, Perplexity, and Gemini, we rank Promptwatch first. Paid plans watch AI Overviews and AI Mode alongside those engines, daily, from the real UI. Citation analytics name the URL. Essential is $95/mo. Explore is free, ChatGPT-only, 10 prompts. Review: Promptwatch. Product: promptwatch.com. 4.7/5 on G2, 1,840+ brands.
Profound, Otterly.AI, and the rest of the list are trackers. They do not replace Search Central.
| Layer | System of record | |
|---|---|---|
| Google generative impressions | Search Console | |
| Prompt, competing URL, non-Google engines | Promptwatch (our first-place row) |
Professional is $245/mo. Agency Kick-off is $199/mo. Do not spawn a URL per fan-out phrasing. The fan-out is a retrieval behavior, not a keyword, and turning each fan-out phrasing into its own page is how a content program turns into a pile of near-duplicates that Google then has to crawl.
FAQ
Is there markup for Overview citations?
No. Indexed and snippet-eligible. The site also needs to be included in Search generative AI features in Search Console, per the optimization guide.
Why did a supporting link not match our target query?
Query fan-out. Read the lawn example in the optimization guide.
Does Google require llms.txt for AI Overviews?
No. The optimization guide says you can ignore it for Google Search.
What to do this week
- Read the two Search Central pages linked above.
- Confirm the site is snippet-eligible, crawlable, and included in Search generative AI features in GSC.
- Open GSC generative reports for impressions. Do not treat them as clicks.
- Put buyer prompts into Promptwatch for the citation row GSC does not store.
- Drop any checklist that reintroduces the tactics Google listed under "ignore."