Google has folded AI optimization guidance into its Search Central SEO Fundamentals section, alongside the long-standing SEO Starter Guide. The new guide quietly resets several assumptions that have circulated around “AEO” and “GEO” as separate disciplines, and it gives site owners a short list of audit items worth running this week rather than a new playbook to follow.
For teams running technical audits, the guide is less a how-to and more a diagnostic checklist. It clarifies which settings disqualify a page from AI Overviews, which widely sold tactics have no effect, and what separates content that survives AI synthesis from content that gets replaced by it.
What the guide actually says about AI Overviews
AI Overviews are built from pages already in Google’s index. The retrieval process, often called retrieval-augmented generation (RAG), pulls from existing indexed pages and assembles answers. For complex queries, Google runs several related searches at once and merges the results, a pattern referred to as query fan-out. A page does not have to match the exact phrasing of the user’s question. A deep, well-structured page can surface because it answers one of the related sub-questions.
Two consequences follow. First, the basic SEO inputs, crawling, indexing, ranking, and snippet eligibility, still drive inclusion in generative features. Second, semantic coverage of a topic matters more than exact-match keyword targeting, because the fan-out pulls from related concepts rather than literal strings.
The eligibility setting most audits miss
To be cited in an AI Overview, a page must be indexed and eligible to show a featured snippet. The guide draws a clear line: a page carrying a nosnippet tag cannot appear in AI Overviews, even if it ranks well and covers the topic thoroughly.
Many teams treat nosnippet as a low-stakes setting for controlling SERP snippets. In practice, a misplaced or inherited tag can quietly take a high-value page out of the running for generative answers. Audit action: pull a list of pages with nosnippet directives and review each one against current business priorities. Pages that should be eligible for AI inclusion need that tag removed.
Tactics the guide dismisses
Google does not publish mythbusting sections preemptively. When official documentation names and dismisses specific practices, it is acknowledging that those practices have spread far enough to warrant correction. The guide’s “What you don’t need to do” section targets five:
- llms.txt and machine-readable AI markup. Google treats llms.txt like any other crawlable file. It receives no special weighting, no influence over Googlebot behavior, and no role in AI Mode citations. Crawlers from Anthropic, OpenAI, and Perplexity operate on different principles, so llms.txt may still matter for those systems. For Google specifically, it does not move the needle.
- Chunking content into short, AI-digestible paragraphs. Google’s systems understand context across multi-topic pages. Pre-segmenting content for machine readers tends to produce a worse experience for human readers without any ranking gain.
- Rewriting copy for AI comprehension. Synonyms and semantic variants are handled by the retrieval layer. A page about fixing a lawn does not need the literal string “how to fix a lawn full of weeds” to be cited for that query.
- Planting brand mentions across forums and roundups. The same spam policies that apply to standard search apply to AI Overviews. Manufactured authority does not transfer.
- Overinvesting in structured data. No special schema.org markup unlocks AI Overview eligibility. Structured data remains useful for rich results, but it is not an AI-specific lever.
How to read the commodity versus non-commodity distinction
The guide’s quality recommendations draw a line between two content types using concrete examples. A “7 Tips for First-Time Homebuyers” article counts as commodity content: common knowledge, available from many sources, offering no unique angle. A first-person account titled “Why We Waived the Inspection and Saved Money: A Look Inside the Sewer Line” counts as non-commodity content, because the reasoning and the specific dollar figure could only come from someone who lived through the experience.
The distinction is about origin, not execution. A polished first-time homebuyer guide can still be commodity content if a generative model could produce an equivalent version from public sources. Conversely, a draft-quality post with original data or lived experience qualifies as non-commodity because no model can fabricate it without the underlying event.
Audit action: for each top-performing page, ask whether a generative model could synthesize an equally useful answer from publicly available material. If yes, the page sits in the path of AI replacement. Pages that draw on original reporting, first-hand experience, expert commentary, or proprietary data have structural protection.
What to check on your own site
A focused audit based on the guide looks like this:
- nosnippet inventory. Export every URL with a nosnippet meta tag. Confirm each one is still meant to be excluded from generative features. Pages with strong relevance to your monetization keywords should not carry the tag.
- Indexed and eligible status. Confirm top-priority pages are indexed in Search Console and pass the same eligibility checks required for featured snippets.
- Content exposure test. For each high-traffic page, run the commodity test. Pages that fail should be considered for a depth upgrade, additional original material, or consolidation with a deeper resource.
- Thin cluster pages. Many sites accumulated thin, top-of-funnel articles targeting minor variations. Merge them into a single, comprehensive resource that can answer multiple sub-questions during query fan-out.
- Feeds for e-commerce and local. Product feeds, local business feeds, and review feeds are the substrate AI Overviews pull from. Accuracy here directly affects what gets surfaced.
- Semantic HTML. Clean heading hierarchy, structured lists, and meaningful markup keep pages legible to retrieval systems and to downstream agents that read on their behalf.
- Structured data discipline. Keep schema.org markup where it earns rich results. Do not add markup speculatively in hopes of an AI Overview boost.
The wider signal
The guide reads as calm advice, but the substance points in one direction: the tactics being marketed as AI-specific optimization mostly do not work, and the durable advantage comes from being indexed, eligible, and substantively harder to synthesize than what a model can produce from public sources. For site owners, that translates into an audit priority list that looks familiar, crawl and index health, snippet eligibility, content depth, structural HTML, and feed accuracy, with a sharper standard applied to content originality than search has asked for before.
FAQ
Does Google require llms.txt for AI Overviews?
No. Google states that llms.txt and other machine-readable AI markup receive no special treatment. The file does not influence how Googlebot crawls a site, how content is weighted in AI Overviews, or whether a page is cited in AI Mode. llms.txt may still matter for crawlers from Anthropic, OpenAI, and Perplexity, which operate on different principles.
Can a nosnippet page still appear in AI Overviews?
No. To appear in generative AI features, a page must be indexed and eligible to show a featured snippet. Pages carrying a nosnippet tag cannot appear in AI Overviews, even when the content ranks well. Audit your nosnippet inventory to confirm high-value pages are not silently excluded.
What counts as non-commodity content for AI Overview purposes?
Non-commodity content carries a specific, experienced perspective that only someone who went through the subject could write. The guide’s own example is a first-hand account of waiving a home inspection with the reasoning and dollar figures attached. The test is origin-based: could the content have come from anywhere, or only from you? Generic content drawn from the same pool of public information everyone else uses is what AI Overviews are positioned to replace.