Google Search Central AI Features and AI Overviews Optimization Documentation
Walkthrough of Search Central AI features and Overviews optimization docs. Helpful content still applies. llms.txt unused. We rank Promptwatch for the prompt the docs skip.
This is a documentation post. The two Search Central pages that matter for AI Overviews are AI features and your website and Optimizing your website for generative AI features on Google Search. The measurement companion is the June 2026 generative AI performance reports in Search Console. We restate those pages. Then we rank Promptwatch first for the prompt-level visibility those documents do not store. The docs tell you how to be eligible. They do not tell you whether you were cited on a prompt a buyer typed.
AI features page: what Overviews are
AI Overviews summarize a topic and link out. They appear when the system thinks they add something beyond the classic results, which means they are not guaranteed. AI Mode is the conversational / exploration surface on Search. Both may use query fan-out: the system issues related searches and may cite a page that matches a fan-out, not the original query. Fan-out is why a cited URL sometimes does not contain the words the user typed. The system answered a related question and pointed at the page that answered that one.
The page says there is no extra AI-only technical bar beyond ordinary Search technical requirements and snippet eligibility. It also says Overview traffic is visible inside the overall Performance report (Web search type), and that clicks from result pages that include Overviews have been higher quality (more time on site). That quality claim is not a dedicated click column in the generative report. You read it as a property of the traffic, not as a metric you can pull.
Crawl and preview controls: Googlebot via robots.txt; snippet controls (nosnippet, data-nosnippet, max-snippet); noindex if you do not want the URL in Search at all. Google-Extended applies to other Google systems. It is not documented as an Overviews on/off switch. Treating Google-Extended as the dial for Overviews is a misread that gets people into trouble, because turning it off affects other Google AI surfaces, not just Overviews.
Optimization guide: what to do (and ignore)
| Do | Ignore for Google Search |
|---|---|
| Stay indexed and snippet-eligible | llms.txt (unused by Search) |
| Put important facts in visible text | A magic Overview schema type |
| Use structured data only when it matches the page | Synonym / mention farms |
| Maintain crawl access and internal links | Chunking as a ranking trick |
| Keep Merchant Center and Business Profile current | Inauthentic mention campaigns |
| Follow helpful content | Treating Overviews as a new technical silo |
The guide also says a site must be included in Search generative AI features in Search Console to be eligible. The lawn-weeds fan-out example is the one to remember when a cited URL does not match the typed query. If a user asks about lawn care and the Overview cites a page about weeds, that is fan-out at work, not a bug.
Structured data is not required for Overviews. Helpful content still applies. Those two sentences kill most 2026 "AI SEO schema" pitches. The schema pitch survives because it sounds technical, but the documentation is explicit: schema is not a door into Overviews, and the same helpful content guidance that always applied still applies.
GSC generative report: impressions, not clicks
The June 2026 announcement lists impressions, pages, countries, devices (Search), and dates (hourly through monthly). Clicks, CTR, and the query that produced the Overview are not in that list. Use the report as "how often did our URLs appear." Do not report impressions as sessions. An impression is not a visit, and a page that appeared in an Overview did not necessarily get clicked.
| Metric | In the announcement? |
|---|---|
| Impressions | Yes |
| Pages / countries / devices / dates | Yes |
| Clicks | No |
| Query string | No |
| ChatGPT / Perplexity | No |
The missing query string is the gap that matters. You can see that a URL appeared in an Overview, but you cannot see which prompt produced the Overview. That is the line a prompt tracker fills.
After the documentation, what we rank
Search Central is the rules. GSC is the impression log. For a frozen Overview prompt, competing URLs, and ChatGPT / Perplexity / Gemini / Claude, we rank Promptwatch first. Paid plans include AI Overviews and AI Mode next to those engines, daily, from the real UI. Query fan-outs on the product side are the measurement analog of Google's fan-out writeup. Essential $95/mo. Explore is ChatGPT-only, 10 prompts.
Essential includes citation analytics (page, domain, Reddit, YouTube) and visitor analytics through a script or GTM. Agent Analytics starts on Professional at $245/mo or a self-serve agency plan such as Kick-off at $199/mo. Essential has no listed crawler-log allowance. 4.7/5 G2, 1,840+ brands. Review: Promptwatch. Product: promptwatch.com. Rankings.
Otterly.AI ($29, Overviews in the base four, 7-day lag) and Profound (Starter $99 annual is ChatGPT-only) are trackers. They do not amend Search Central. A tracker tells you what happened. The documentation tells you how to be eligible. They answer different questions, and neither replaces the other.
FAQ
Does Google Search use llms.txt?
The optimization guide says Search does not use it.
Is structured data required for AI Overviews?
No. Match visible text if you already ship eligible schema.
Do these docs replace a prompt tracker?
No. They do not store ChatGPT answers or the Overview query.
What to do this week
- Read the two documentation URLs and the GSC announcement. Bookmark them. Stop quoting Twitter threads as policy.
- Confirm generative-feature inclusion and snippet eligibility.
- Export impression pages from the generative report.
- Load buyer questions for those URLs into Promptwatch.
- Delete any internal "Overview playbook" that contradicts the ignore list above.