Google documentation confirms: AI Overviews does not require its own structured data markup

The document that brings technical SEO back down to earth

The AI features and your website page from Google Search Central was updated in December 2025 and remains Google's official reference on how sites appear in AI Overviews and AI Mode. This isn't recent news: nearly a year has passed since the last revision. But it answered a question that still circulates widely among SEO teams in Brazil: is there a specific structured data markup, a new schema.org, or a special tag to "get into" Google's AI?

The documented answer is no. And that answer changes the priorities of whoever manages a site's technical side.

There's just one technical requirement, and it already existed

The most direct passage in the documentation is also the most underrated:

To be eligible to be shown as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown in Google Search with a snippet, fulfilling the Search technical requirements. There are no additional technical requirements.

Google Search Central, AI features and your website documentation

In other words: if a page is already indexable, crawlable, and eligible to appear with a snippet in traditional search, it already meets the technical requirement for AI Overviews and AI Mode. There's no AI-specific itemtype, no robots.txt attribute dedicated to generative search engines, and no meta tag that unlocks this type of result.

Why the "schema for AI" myth persists

The misunderstanding is understandable. GEO (generative engine optimization) tools emerged selling the idea that AI-generated responses have their own rules, and part of the market read that as "I need new markup." Google's documentation undoes that reading by listing the practices that apply to AI Overviews and AI Mode: they're exactly the same as fundamental SEO, with no technical addendum.

In short: what changes between appearing in classic search and appearing in an AI-generated response isn't the page's markup, it's the retrieval process Google runs behind the scenes, called query fan-out. In this process, the system fires off multiple related searches across subtopics and data sources while assembling the response, and uses models to identify additional supporting pages, displaying a wider and more diverse set of links than a classic search would show.

In practice, this means the pool of pages that could appear in an AI response tends to be larger than that of a classic search; what the documentation doesn't detail is which types of pages are favored by this expansion.

What the documentation lists as practices that still apply

Google's list of best practices for AI Overviews and AI Mode is, point by point, the same technical SEO agenda that should already be on any checklist:

• Making sure crawling is allowed in robots.txt and by any CDN or hosting infrastructure
• Making content easy to find through internal links
• Providing a good page experience (Core Web Vitals signals fall here)
• Making sure important content is available in textual form
• Supporting textual content with high-quality images and videos, when it makes sense
• Making sure structured data matches the visible text on the page
• Keeping Merchant Center and Business Profile information up to date

The item about structured data deserves extra attention in this context. The requirement isn't new, but the documentation is explicit in recommending that schema match the visible text on the page, without detailing what the practical consequence of an inconsistency would be in the context of AI Overviews and AI Mode. In the absence of that specification, the safest approach is to treat the recommendation as even more relevant when the page can serve as a grounding source for a generative model, and not to assume what the exact effect of failing to follow it would be.

How to measure before and after in Search Console

The documentation is explicit about where to look for the numbers: sites that appear in AI Overviews and AI Mode are included in Search Console's overall search traffic, reported in the Performance report, within the "Web" search type. There's no separate "AI clicks" report; the signal is mixed in with the rest, which requires comparing periods and cross-referencing with Google Analytics to isolate behavior patterns.

Google itself records a qualitative observation, with no number attached: clicks originating from result pages with AI Overviews tend to be higher quality, in the sense that users spend more time on the site after clicking. It's a directional reading, not a settled metric, and it's worth treating as a hypothesis to test in your own dashboard before it becomes a claim in an internal report.

The controls that actually exist (and aren't about markup)

Whoever wants to limit or adjust a site's presence in these features has four documented levers, none of them an AI schema:

1. robots.txt for Googlebot, which controls the general crawling used by Search (and, by extension, by AI features, since they're an integral part of Search)
2. nosnippet, data-nosnippet, and max-snippet to limit the text displayed from the page
3. noindex to remove the entire page from indexing, including its use as a supporting link in AI
4. Google-Extended, a separate control, specific to limiting the use of content for training and grounding in other Google systems

The distinction between the third and fourth points is the detail that causes the most confusion: noindex removes the page from Search and from the AI features within Search, but not necessarily from the use other Google products make of the content to train or ground models. For that, the correct control is Google-Extended, applied separately.

Troubleshooting: when the control doesn't work in practice

The documentation also offers a diagnostic roadmap for those who implemented a preview control and still see content appearing in AI features. First, confirm that the control is correct and visible to Googlebot, using the URL Inspection tool to check the HTML the bot actually received. Second, allow time for recrawling: Google notes the process can take anywhere from days to months, depending on how often the system determines the page needs refreshing, and that it's possible to request a new crawl manually. If the problem persists after these two steps, the recommended channel is the Google Search Central help community.

What actually changes for those running a Brazilian site

The operational conclusion is uncomfortable for those expecting a new list of tags: there's no specific technical shortcut to appearing in AI Overviews or AI Mode. The work is the same as always, done with more rigor, because fan-out widens the pool of candidate pages and the documentation recommends redoubling attention to the fidelity between schema and visible text.

Whoever already maintains healthy Core Web Vitals, a clean robots.txt, accessible textual content, and structured data faithful to what the page shows doesn't need any markup changes: they just need to keep measuring through the Performance report, "Web" type, comparing periods before and after specific technical changes, since there's no separate breakdown for AI traffic within Search Console.

Source 1: Google Search Central — AI features and your website (https://developers.google.com/search/docs/appearance/ai-features)

Skip to main content

Search Central

English

Deutsch

Español

Español – América Latina

Français

Indonesia

Italiano

Polski

Português – Brasil

Tiếng Việt

Türkçe

Русский

العربيّة

हिंदी

ภาษาไทย

中文 – 简体

中文 – 繁體

日本語

한국어

Sign in

Documentation

Search Console

Home

Send feedback

AI features and your website

This guide covers how AI features like AI Overviews and AI Mode work in Google Search from a site owner's perspective and how to approach your content's inclusion in these experiences.

How AI features work in Search

As with Search overall, the AI features AI Overviews and AI Mode surface relevant links to help people find the information they're looking for quickly and reliably, as well as to help them explore content they may not have discovered before. These features offer unique opportunities for more types of sites to appear.

AI Overviews help people get to the gist of a complicated topic or question more quickly, and provide a jumping off point to explore links to learn more. They were designed to show up on queries where they can add additional benefits beyond what people might already get on Search. With AI Overviews, people have been visiting a greater diversity of websites for help with more complex questions.

AI Mode is particularly helpful for queries where further exploration, reasoning, or complex comparisons are needed. People can ask nuanced questions that might have previously taken multiple searches — from exploring a new concept, to comparing options, and beyond — and get a comprehensive AI-powered response with links to supporting websites.

Both AI Overviews and AI Mode may use a "query fan-out" technique — issuing multiple related searches across subtopics and data sources — to develop a response. While responses are being generated, our advanced models identify more supporting web pages, allowing us to display a wider and more diverse set of helpful links associated with the response than with a classic web search, enabling new opportunities for exploration.

AI Mode and AI Overviews may use different models and techniques, so the set of responses and links they show will vary. AI Overviews are only shown when our systems determine that it is additive to classic Search, and as such, often don't trigger.

How to appear in AI features

You can apply the same foundational SEO best practices for AI features as you do for Google Search overall: making sure the page meets the technical requirements for Google Search , following Search policies , and focusing on the key best practices , such as creating helpful, reliable, people-first content .

Technical requirements for appearing in AI features

To be eligible to be shown as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown in Google Search with a snippet, fulfilling the Search technical requirements . There are no additional technical requirements.

SEO best practices

While specific optimization isn't required for AI Overviews and AI Mode, all existing SEO fundamentals continue to be worthwhile, for example:

Ensuring that crawling is allowed in robots.txt, and by any CDN or hosting infrastructure

Making your content easily findable through internal links on your website

Providing a great page experience for users

Making sure that important content is available in textual form

Supporting your textual content with high-quality images and videos , when applicable

Making sure your structured data matches the visible text on the page

Checking that your Merchant Center and Business Profile information is up-to-date

To discover and diagnose potential technical issues quickly, verify your site in Search Console .

Measuring the performance of your site

Just like the rest of the search results page, sites appearing in AI features (such as AI Overviews and AI Mode) are included in the overall search traffic in Search Console . In particular, they're reported on in the Performance report , within the "Web" search type . Learn more about how AI Overviews and AI Mode are counted towards the overall data in Search Console, how to analyze traffic changes overall, and how to combine Search Console and Analytics data .

In addition to Search Console, you could also track conversions and time spent on your site in other tools, such as Google Analytics. We've seen that when people click from search results pages with AI Overviews, these clicks are higher quality (meaning, users are more likely to spend more time on the site).

Controlling your content in AI features in Search

AI is built into Search and integral to how Search functions, which is why robots.txt directives for Googlebot is the control for site owners to manage access to how their sites are crawled for Search. To limit the information shown from your pages in Search, use nosnippet , data-nosnippet , max-snippet , or noindex controls.

To limit AI training and grounding in some of Google's other systems, read more about Google-Extended .

Troubleshooting preview controls

If you implemented preview controls and you're still seeing your content appear in AI features on Search, try the following steps:

Make sure that the preview control is correct and visible to Googlebot. To test if your implementation is correct, use the URL Inspection tool to see the HTML that Googlebot received while crawling the page.

Allow time for Google to recrawl and process the change in preview controls. Remember that crawling can take anywhere from several days to several months, depending on how often our systems determine a page needs to be refreshed. If you've made changes, you can request that Google recrawl your pages .

If you tried the troubleshooting steps and still find issues, post in the Google Search Central Help Community .

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-12-10 UTC.