Google AI Overviews and AI Mode: What Google Actually Says You Need to Do

Short answer: Google says there are no additional requirements to appear in AI Overviews or AI Mode, and no special optimization beyond normal SEO. A page has to be indexed and eligible to be shown in Google Search with a snippet; there are no further technical requirements. You need no new file format, no llms.txt and no special markup. Nobody can promise that a page is shown, because Google says indexing and serving are never guaranteed. So spend your time on the basics: allow crawling, link your pages internally, and keep the important content in the HTML as text.

What are AI Overviews and AI Mode?

Both are AI features inside Google Search, and Google documents them together on one page, AI features and your website. According to that page, AI Overviews help people get to the gist of a complicated topic quickly and give them links to learn more. AI Mode is meant for questions that need more exploration, reasoning or comparison, and answers with links to supporting websites.

Two details from Google's description matter for site owners:

• They may use "query fan-out". Instead of one search, the system can issue several related searches across subtopics and data sources to build a response. Our reading, not a Google statement: a page that answers a clear sub-question well has more than one way to be found.
• They do not always appear. Google says AI Overviews are only shown when its systems decide that they add something to classic Search, and that they often do not trigger. AI Overviews and AI Mode may use different models and techniques, so the answers and the links they show vary.

Pages are shown as supporting links. The visibility is counted like the rest of Search: Google reports sites that appear in these features within the overall search traffic in Search Console, in the Performance report under the "Web" search type.

Do you need anything special to appear in AI Overviews?

No. Google's wording is plain: there are no additional requirements to appear in AI Overviews or AI Mode, and no other special optimizations are necessary. The best practices for SEO remain relevant.

The technical requirement is the same one that applies to Search overall. To be eligible as a supporting link, a page must be:

1. Indexed. Google has crawled it and stored it in its index.
2. Eligible to be shown in Google Search with a snippet. A page that opts out of snippets gives up this eligibility: Google's robots meta tag documentation says that nosnippet also prevents the content from being used as a direct input for AI Overviews and AI Mode.

That is the whole list. Google adds a caveat that is easy to skip: even a page that meets all requirements and follows all policies is not guaranteed to be crawled, indexed or served.

What the fundamentals look like in practice

Google lists examples of SEO fundamentals that continue to be worthwhile. Here are five of them, with a way to check each one:

Nothing in this table is new. That is the point of Google's statement: the work for AI features is the work you would do for Search anyway.

What you do not need

Google says you do not need to create new machine-readable files, AI text files or markup to appear in these features. It also says there is no special schema.org structured data that you must add.

This answers a question many site owners ask: do I need an llms.txt for AI Overviews? Google's guidance says no new AI text files are needed. In addition, reports from Google events say Google does not support llms.txt and does not plan to (second-hand reports, see our article What is llms.txt?). The file may still be a harmless extra for other assistants, but a benefit is not proven.

A caution about the scope: these statements are about Google Search. Other assistants have their own crawlers and their own rules. OpenAI, for example, documents separate bots for training, for search in ChatGPT and for user-requested fetches, and says a page that blocks OAI-SearchBot does not appear in ChatGPT's search answers (see the OpenAI documentation and our article on robots.txt for AI crawlers). Do not take Google's "nothing special needed" as a statement about every assistant.

What you can control

If you want to limit how your content appears, Google names these tools:

Google writes that AI is built into Search, which is why the controls for Search are the controls for these features. On that page it names no switch that applies to AI Overviews alone.

Here is how the preview controls look in a page:

<meta name="robots" content="nosnippet">
<meta name="robots" content="max-snippet:100">

<p>This sentence may appear in a snippet.
<span data-nosnippet>This part stays out of snippets.</span></p>

Use one of the two meta lines, not both: they are alternatives. After you change a preview control, allow time. Google says recrawling can take anywhere from several days to several months, depending on how often its systems decide a page needs a refresh.

Google-Extended is not the switch

The token Google-Extended in robots.txt is often mistaken for the control of AI Overviews. It is not. Google describes it as a separate product token that controls whether content crawled by Google may be used to train future Gemini models and for grounding in Gemini Apps and Vertex AI. It does not affect inclusion in Google Search and it is not a ranking signal. See Google's list of common crawlers.

How to check what Googlebot sees

You cannot optimize what you cannot see. Three checks take a few minutes:

1. Open the URL Inspection tool in Search Console. Google recommends it to see the HTML that Googlebot received while crawling a page. Check that the title, the main text and your preview controls are in it.
2. Read your robots.txt as Google does. The most specific matching rule wins, and a group written for Googlebot replaces the group for all bots instead of adding to it. So if you create a group for Googlebot, repeat every rule you need in it. The rules are defined in RFC 9309.
3. Compare the HTML you serve with what visitors see. Google runs JavaScript with a current Chromium, but pages are rendered in a queue after crawling, which can take seconds or longer. Google itself says that server-side or pre-rendering remains a good idea, in part because not all bots can run JavaScript. See Google's JavaScript basics.

How SEOgrinder helps with these checks

SEOgrinder is a free scanner: you enter the address of a public website and get a report without an account. These parts of the report fit this topic:

• Page on Google: title, meta description, canonical, robots directives, headings and URL quality.
• Technology & security: robots.txt, sitemap, redirect chains, compression, caching and soft-404 detection.
• Pages that build in the browser: SEOgrinder reports them as "The page is only assembled in the browser", with the note that many AI crawlers run no JavaScript and see an almost empty page.
• Website: internal links and images of the page are checked for broken targets, redirects and images that do not load. A crawl of the site reports orphan pages, click depth, duplicate titles and thin pages.
• Speed: Core Web Vitals from Google PageSpeed Insights (lab data) and from real visitors (CrUX).

SEOgrinder does not measure whether AI Overviews or any other assistant actually mention your pages. It checks the technical basis: can the pages be reached and read? Tools that track mentions do a different job.

Myths about AI Overviews

• "You need an llms.txt." Google's page says no new AI text files are needed. See above.
• "You need special schema.org markup." Google says there is no special structured data to add. Structured data you do use should match the visible text.
• "Block Google-Extended to stay out." It does not control AI Overviews, and it does not affect inclusion in Search.
• "There is a separate AI Overviews checklist." Google says the existing SEO fundamentals continue to be worthwhile.
• "If I meet the requirements, I will be shown." Google says indexing and serving are not guaranteed, and AI Overviews often do not trigger at all.

Common mistakes

• Treating AI Overviews as a separate discipline while a leftover noindex from a staging site or a robots.txt Disallow keeps pages out of Search.
• Blocking Googlebot at the CDN or host while robots.txt looks fine. Google names this explicitly.
• Using nosnippet across the whole site and expecting to appear as a supporting link. Google says nosnippet also keeps content from being used as a direct input for AI Overviews and AI Mode, and max-snippet limits how much of it may be used.
• A Googlebot group in robots.txt that drops your other rules. A bot with its own group ignores the group for all bots.
• Content that exists only after JavaScript runs. Google can render it, but other crawlers may not.
• Expecting an effect right after a change. Recrawling can take days to months.

FAQ

How do I appear in AI Overviews?

Meet the technical requirements for Search, follow Google's policies and focus on helpful, reliable content for people. There is no guarantee: Google says indexing and serving are never guaranteed, and AI Overviews do not appear for every query.

Do I need llms.txt for AI Overviews?

Google says you do not need new machine-readable or AI text files. A benefit of llms.txt for rankings or for AI citations is not proven.

Does blocking Google-Extended remove my site from AI Overviews?

No. Google-Extended is not the control for AI Overviews, and Google says it does not affect inclusion in Google Search. Use the controls described above.

Do the same rules apply to ChatGPT or Perplexity?

Not necessarily. Each provider documents its own crawlers. Check each provider's rules, and read our article on robots.txt for AI crawlers.

Your next step

Run the free scan on your site with SEOgrinder and work through the list from the top: indexing and crawling first, then internal links, speed and the HTML you serve. Then open the URL Inspection tool for your most important page and read what Googlebot received. If those basics are in order, you have done what Google says is required.