How to appear in Google AI Overviews and AI Mode: what Google's own guidance says
By Thomas Lovas Lokoy · Published 23 October 2026 · 6 min read
There is no special trick to appearing in Google's AI Overviews or AI Mode, and Google says so in writing. Its guidance for site owners states that "there are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary", and that a page has to be indexed and eligible to be shown in Google Search with a snippet to be used as a supporting link. Everything else is ordinary search work done well. This guide sets out what Google's page actually says, what that means for a blog article, and the handful of things worth checking this week.
What Google means by "AI features"
Google's documentation for site owners, "AI features and your website", covers two products in Google Search: AI Overviews, the generated summary that appears above some results, and AI Mode, the conversational search experience. Both show links to the web pages they draw on, which Google calls supporting links.
The page also describes a technique both features may use, called query fan-out: "issuing multiple related searches across subtopics and data sources" to build a response. In practice that means one question from a user can turn into several searches behind the scenes, and a page can be cited for a sub-question it answers well even if it would not rank first for the user's original wording.
The eligibility rules, in full
There are only two technical conditions in Google's guidance for being shown as a supporting link:
- The page must be indexed.
- The page must be eligible to be shown in Google Search with a snippet.
Google adds that meeting these requirements does not guarantee that a page will be crawled, indexed or served. That is the same caveat that applies to normal results.
Just as important is what is not on the list. Google states: "You don't need to create new machine readable files, AI text files, or markup to appear in these features." No special schema type, no dedicated AI file, no separate sitemap. If you have read advice that a particular file or markup is required for AI Overviews, Google's own page contradicts it. We look at one of those files, llms.txt, in a separate guide.
What Google recommends instead
The best-practice list on the same page is the fundamentals of search, applied to AI features:
| Google's recommendation | What to check on a blog | | --- | --- | | Allow crawling in robots.txt and by any CDN or hosting infrastructure | Your CDN or firewall is not blocking Googlebot; robots.txt does not disallow your articles | | Make content easy to find through internal links | Every article is linked from at least one other relevant page | | Provide a good page experience | The article is readable on a phone, without intrusive pop-ups in the way | | Keep important content available as text | Key facts are in the text, not only in images or video | | Support text with relevant images and video | Images illustrate the point and carry useful alt text | | Make structured data match the visible text | Article markup matches the headline, author and dates the reader sees | | Keep Merchant Center and Business Profile information current | Relevant for shops and local businesses |
None of these is new, which is the point. Our guides on internal linking, image alt text and Article structured data cover several of them in detail.
How to write articles that answer the sub-questions
Query fan-out suggests a practical writing habit, though Google does not prescribe one: make each section of an article answer one clear question, completely, near the top of that section. A reader who arrives from a fan-out search for a sub-topic should find the answer without reading the whole piece.
Three habits help:
- Lead with the answer. Put the direct answer in the first sentence or two of the article, and of each major section.
- Use descriptive headings. A heading such as "How long does a core update take to roll out?" tells a reader, and a search system, exactly what the section answers.
- Back specific claims with sources. Numbers, dates and rules should link to where they came from. Our guide on how to cite sources in a blog post covers the format.
This is also what Google's people-first guidance asks for, which we summarise in helpful content. The AI features do not have a separate rulebook.
Controlling what appears
If you would rather a page, or part of one, did not appear in AI features, Google points to the same controls that govern snippets in ordinary search:
- nosnippet stops a snippet being shown for the page.
- data-nosnippet on an HTML element keeps that part of the page out of snippets.
- max-snippet limits snippet length.
- noindex removes the page from Search altogether.
Robots.txt rules for Googlebot control crawling. Google's page also notes a separate control, Google-Extended, for limiting the use of content for training and grounding in some of Google's other AI systems. It is worth reading the exact wording before you use any of these, because a nosnippet set to keep a page out of AI Overviews also affects its ordinary result.
Measuring traffic from AI features
There is no separate AI Overviews report. Google's page says sites appearing in AI features are included in the overall search traffic in Search Console and are reported in the Performance report under the "Web" search type. You cannot isolate AI Overview clicks there.
Google also says, in the same guidance, that clicks from these features are "higher quality (meaning, users are more likely to spend more time on the site)", and suggests looking beyond clicks at conversions and time on site in your analytics. Treat that as Google's claim rather than a measured result for your site; your own analytics are the only way to see whether it holds for you.
Three myths worth dropping
"You need special markup or a special file." Google's page says the opposite, in so many words: no new machine-readable files, AI text files or markup are needed. Structured data still helps ordinary results, and Google asks that it match the visible text, but there is no AI-only schema.
"AI features only cite the number one result." Google's description of query fan-out says these features issue several related searches across subtopics, and that this lets them show a wider set of supporting links than a classic search. A page that answers one sub-question clearly has a reason to be there.
"You can opt out of AI Overviews without affecting anything else." The controls Google lists, nosnippet, data-nosnippet, max-snippet and noindex, are the same ones that shape your ordinary result. Decide with both in mind.
A one-week checklist
- Confirm indexing of your important articles with the URL Inspection tool in Search Console.
- Check snippets are allowed: no stray nosnippet or very short max-snippet on articles you want cited.
- Check your CDN and firewall are not blocking Googlebot.
- Rewrite your top five articles' openings so the first two sentences answer the title's question directly.
- Audit headings on those five so each section answers one clear question.
- Add internal links from related posts to any article that has none.
- Match structured data to the page: headline, author and dates.
Where AI Orbit fits
AI Orbit drafts long-form articles with a direct answer up front, descriptive headings and a sources section, which is the shape this guide recommends. It does not and cannot guarantee a place in AI Overviews; nothing can. What it can save is drafting time, which you can spend on the checks above and on fact-checking the draft before it goes live. Plans and credits are on the pricing page.