Google Search Central AI Features and AI Overviews Optimization Documentation

Google Search Central's AI Overviews documentation is two URLs: AI features and your website and Optimizing your website for generative AI features on Google Search. This is close to our earlier AI-features walkthrough, with the optimization guide in the title. Same rules. Read both pages anyway. The titles sound interchangeable, and the second page is where Google lists the tricks to ignore, which is the part most teams skip.

Overviews versus AI Mode is a product split inside Google, not two SEO strategies. Query fan-out, shown by the lawn-weeds example on the docs, is how Search expands a question. Snippet eligibility is still the bar. There is no extra technical bar for generative features. The optimization guide also says to include the site in Search generative AI features in Search Console. Unique viewpoint, non-commodity pages. Ignore llms.txt, chunking, inauthentic mentions, and magic schema. GSC generative reports give impressions, pages, countries, devices, and dates.

Promptwatch is the prompt-level layer for Overviews and for non-Google engines. Those docs do not include it. Essential is $95/mo. Method: how we rank. Site: promptwatch.com.

What each URL is for

AI features and your website is the eligibility page: can this site appear in Google's generative surfaces, and what does that take. The answer is mostly "the same things Search already wanted," plus the note that Overviews and AI Mode are different surfaces that still draw from the index. That distinction matters because teams sometimes treat AI Mode as a separate crawl target and build a parallel set of pages for it, which is not what the page describes.

The optimization guide is the anti-folklore page. Google walks through ideas that showed up in AEO and GEO decks and says a lot of them are not how Search works. llms.txt is on that ignore list. So is chunking content for machines, stuffing inauthentic mentions, and inventing schema that does not match the page. If your next deck still leads with those, you are presenting against the documentation in the title of this post, and a buyer who has read the same page will notice.

Include the site in Search generative AI features in Search Console. That is a checkbox-shaped instruction from Google, not a third-party hack, and the difference is who maintains it. Then open the generative performance reports. Impressions, pages, countries, devices, dates. That is the official volume. It is not the prompt, and it is not the answer a model gave to a buyer question.

Lawn weeds, fan-out, and commodity pages

The lawn-weeds example is Google's way of saying a question fans out. Someone asks about weeds in the lawn. Search may also look up related treatments, local rules, or product types. That is not a brief to publish a thin URL for every related phrase, because the fan-out describes how the query expands, not how your site should be filed. It is a reason to write a page with a unique viewpoint instead of another commodity explainer that already exists in twenty copies.

Snippet eligibility still decides whether you are in the conversation. No extra technical bar means you do not need a new robots dance for Overviews, and you do not need a separate crawl budget argument. You need to be indexable and worth citing. Non-commodity pages matter because generative features summarize, and a summary favors the page that has something to summarize. A page that only restates the category will lose to a page that has a point of view, a table, or original detail, because the summarizer has nothing distinct to lift from the restatement.

Where the prompt layer starts

Search Central will not store "best lawn service in Austin" as a row you recheck after a rewrite. Promptwatch will, for Overviews at prompt level and for ChatGPT, Perplexity, and the other assistants. Essential at $95/mo is that program. Keep GSC generative inclusion on. Load the same money queries into Promptwatch. Skip Overview folklore in the next deck. Two official URLs are enough homework for Google. The third job is the list you typed, because that list is the one your buyer asks the model, and it is the one no Google report stores.

This title leads with Search Central and optimization. The AI-features content-guidance post on this site uses the same docs. Read both Google pages. Do not treat our two posts as two different official stacks, because they draw on the same source and reach the same conclusion.

FAQ

Is this different from the AI features content-guidance post?

Same docs. This title leads with Search Central and optimization. Read both pages anyway.

Do we need special schema for Overviews?

No. The optimization guide does not ask for a magic type. Keep structured data matched to visible text if you already use it for rich results.

Is llms.txt in the documentation as a lever?

It is on the ignore list. Do not put it on an Overview slide as the tactic.

What to do this week

1. Open both Search Central URLs. Features page first, optimization guide second. Write down the ignore list.
2. Confirm snippet eligibility and GSC generative inclusion. If the site is not in those reports, fix that before you argue about prompts.
3. Open generative performance reports. Note impressions by page, country, and device.
4. Load the same money queries into Promptwatch as prompt-level Overviews, plus the non-Google engines you care about.
5. Skip Overview folklore in the next deck. No llms.txt, no chunking theater, no inauthentic mentions, no magic schema.