AI Overviews and AI Mode are the AI answers a growing share of searchers see, because they sit right inside Google Search. The good news is that Google has published exactly what it takes to show up, and it is shorter and far less exotic than the AEO hype suggests.
The one-sentence version
Google is blunt about this: “There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary.” The features are “rooted in our core Search ranking and quality systems.” So being eligible for Google’s AI answers is the same job as being good at Search. A page has to “be indexed and eligible to be shown in Google Search with a snippet, fulfilling the Search technical requirements.”
That is the whole gate. Everything below is how you clear it.
What actually gets you in
- Be crawlable and indexed. Google’s generative AI uses publicly accessible, crawlable content. If Googlebot cannot reach a page, or the page is not indexed, it cannot appear in an AI answer. Start with crawler reachability and a clean XML sitemap.
- Stay snippet-eligible. The page must be able to show with a snippet. A
noindexornosnippetdirective takes it out of the running. - Write something only you could write. Google’s exact words: “Don’t just recycle what others on the internet have already said, or could easily be produced by a generative AI model.” The test it hands you is simple: “Is this content that my visitors would find satisfying?”
- Structure it so an engine can lift it. Clear headings, direct answers, self-contained passages. See writing content AI can quote.
The myths Google tells you to skip
This is where Google is unusually direct, and where most AEO advice gets it wrong. Google’s own guidance says these tactics do not get you into its AI features:
- Creating
llms.txtor other AI text files. - Adding special schema.org markup for AI.
- Chunking your content into tiny pieces.
- Rewriting existing content specifically for AI systems.
- Chasing inauthentic “mentions” of your brand.
A note on honesty, because this library covers some of those techniques elsewhere. llms.txt, markdown variants, and JSON-LD each have their uses; they help other engines and agentic tooling, and structured data still helps Google understand who you are. But for Google’s AI features specifically, Google says they are not the lever. Do not build them expecting an AI Overview placement.
The controls, and one that trips people up
You control appearance through the same tools you already have: robots.txt for Googlebot, and nosnippet, data-nosnippet, max-snippet, or noindex to control whether and how a page can show.
Google-Extended is different, and worth understanding because sites block it by mistake. It governs whether your crawled content is used for AI training and grounding in some of Google’s other systems (this is the Gemini control). Here is the part that matters: Google states that Google-Extended “does not impact a site’s inclusion in Google Search nor is it used as a ranking signal.” So blocking it will not remove you from AI Overviews, because those run on Search. It only affects the other systems.
Products and local businesses
If you sell products or run a local business, Google surfaces that information in AI responses through Google Merchant Center and your Google Business Profile. Keep both current and accurate.
Where to start
Almost every miss here is a crawl, index, or snippet problem, and those are exactly what your Free Scan report checks. Fix the readable half first, then work on being the clearest answer worth citing. To watch whether it moves, Google Search Console is the free first stop; the measuring AI visibility guide covers what else to track.