Google confirms there is no exclusive structured data for appearing in AI Overviews
Google Search Central's documentation on AI Overviews and AI Mode is direct: there is no exclusive schema, meta tag, or technical signal for entering these responses. What exists are controls to limit or allow what is already indexed.
- Reading
- 7 min
- Tables
- 1
Google confirms there is no exclusive structured data for appearing in AI Overviews
Editor's note: this article originally cited the update date of the Google Search Central documentation as December 31, 2025. The original source states "Last updated 2025-12-10 UTC," that is, December 10, 2025. This date error does not affect the other technical claims in the text, which were verified and confirmed in the documentation, but it is recorded here for transparency with the reader.
Google Search Central's documentation on AI Overviews and AI Mode is direct: there is no exclusive schema, meta tag, or technical signal for appearing in these responses. What exists are controls to limit or allow what is already indexed.
Google Search Central's documentation on AI Overviews and AI Mode is direct: there is no exclusive schema, meta tag, or technical signal for appearing in these responses. What exists are controls to limit or allow what is already indexed.
Google Search Central's documentation on AI Overviews and AI Mode is direct: there is no exclusive schema, meta tag, or technical signal for appearing in these responses. What exists are controls to limit or allow what is already indexed.
The sentence that sums up the whole page
The "AI features and your website" page, from Google Search Central, tries to answer a question every technical SEO team has been asking since AI Overviews started appearing in a relevant share of searches: is there any specific markup for appearing in these AI-generated responses? The answer, stated bluntly in the documentation itself, knocks down much of what circulates as promise-filled "GEO optimization":
There are no additional technical requirements.
Google Search Central
The full sentence that precedes this conclusion is even more important than the conclusion itself: to appear as a supporting link in AI Overviews or AI Mode, a page only needs to be indexed and eligible to be shown in Search with a snippet, meeting Google Search's standard technical requirements. In other words: what is already good for ranking is what is already good for being cited by the AI.
How the AI response chooses what to cite
The documentation explains that AI Overviews and AI Mode can use a technique called "branching query distribution" (query fan-out in the original): instead of answering from a single search, the system fires multiple searches related to different subtopics and data sources to assemble the final response. In practice, this means a page can be pulled into the response not by the literal query the user typed, but by one of the branches the model generated internally.
This detail changes the way you think about content coverage. It's not enough to optimize a page only for the main keyword of a topic: if the fan-out generates sub-searches about comparison, history, or use case, only pages that also cover these secondary angles in crawlable text get cited. Google reinforces that AI Overviews only appears when its internal systems determine that it adds value over traditional search results, which explains why the feature doesn't appear on every query.
The technical requirements are the same as always
The list of best practices Google recommends for AI Overviews and AI Mode is, deliberately, the same list of technical SEO fundamentals that already existed before generative AI arrived in search results:
- Making sure crawling is allowed in
robots.txtand by any CDN or hosting infrastructure in front of the site; - Making content accessible through internal links within the site itself;
- Offering a solid page experience for whoever arrives via the click;
- Making sure important content exists in text form (not only in image or video);
- Accompanying the text with quality images and videos, when it makes sense;
- Making sure structured data matches the visible text on the page;
- Keeping Merchant Center information and business profile up to date, when applicable.
The point most often misread by people working in SEO is the one about structured data. The documentation does not ask for a new schema, such as FAQPage or something equivalent custom-built for AI: it asks for consistency between the markup and what is visible on the page. Structured data that describes something the rendered text does not support is the kind of signal that undermines the system's trust, not something that guarantees presence in the response.
How to control what appears (and what trains models)
Since AI is integrated into Search and uses the same Googlebot crawling, the controls for limiting what appears are the same directives as always, now repurposed for this context. To restrict what is shown from a page in Google Search, including in AI responses, the documentation lists four commands:
| Directive | Effect |
|---|---|
nosnippet | Prevents any text excerpt or video preview of the page |
data-nosnippet | Blocks a specific piece of HTML from being used as a snippet |
max-snippet | Limits the size of the snippet that can be shown |
noindex | Removes the entire page from indexing and, consequently, from any AI response |
These four controls decide whether the page appears in Search as a whole; they are not a separate switch just for AI Overviews. A page using noindex stays out of everything, including AI-generated responses; a page using nosnippet can still be listed as a link, but without the text being reused as a citation.
For those who want to separate this from another issue, allowing or not content to feed training for other Google AI systems, the documentation points to the Google-Extended control, handled separately from the snippet controls. These are two different decisions: one is about appearing in today's search response, the other is about becoming training data for future models.
Where this appears in Search Console (and why the click profile changes)
For those measuring results, the news is that there is no separate report for AI Overviews or AI Mode within Search Console. These clicks go into regular organic search traffic, within the performance report, under the "Web" search type. This means a drop or rise in impressions/clicks caused by changes in AI Overviews appears mixed in with the rest of Search, requiring period comparison and, when possible, cross-referencing with Analytics data to isolate the effect.
One qualitative data point the documentation itself brings is worth the attention of anyone tracking the funnel: Google states it observes that clicks coming from search results pages with AI Overviews tend to be of better quality.
We've found that clicks from search results pages that include AI Overviews are of higher quality, meaning that users tend to spend more time on the site.
This is a claim from Google itself, with no public benchmark attached on this page, but it's a good reason to look at session time and bounce rate segmented by period, not just click volume, when assessing the impact of AI Overviews on a specific site.
Troubleshooting: when content disappears even with the right directives
The documentation also covers the reverse scenario: the site implemented nosnippet, noindex, or similar directives, and the content still appears in AI features. The suggested diagnostic routine is straightforward: first, confirm the directive is correct and visible to Googlebot using the URL inspection tool, which shows the HTML received during crawling. Then, allow time: Google warns that recrawling can take days or months, depending on how often its systems decide that page needs to be updated, 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 forum. There is no SLA or guaranteed response time in this documentation: it's community support, not a direct Google support channel.
What remains open
The documentation, updated on December 10, 2025, leaves out a point that many people in technical SEO would like to see answered with numbers: what is the citation rate of pages by niche, how much real weight does consistent versus inconsistent structured data carry in the decision to cite, and how to isolate AI Mode measurement within the "Web" report without access to its own segmentation.
Until Google opens up that level of detail, the best GEO strategy remains the most boring one to sell on a slide: ensure crawling is open, indexing is clean, markup is faithful to visible text, and measurement is recurring via Search Console, without waiting for a shortcut that the source itself says doesn't exist.
Translated from the Brazilian Portuguese original · Read the original
Llms.txt v2 in Practice: How to Generate, Validate and Monitor the File for Generative AI
The llms.txt specification has a version 2, with companion markdown pages and standardized HTTP headers. See the roadmap for migrating a Brazilian site, and what, honestly, still can't be proven about whether AI bots actually read it.
