Google's Own Documentation Says AEO Hacks Don't Work — Prioritize SEO Instead
Google Search Central states there are no special technical requirements for AI features, no AI-specific schema, and no llms.txt needed.
3 min read
A growing vendor ecosystem sells "AEO" and "GEO" packages — special schema, llms.txt files, AI-specific markup, and citation-engineering playbooks. Google's published guidance says most of it is unnecessary at best and distraction at worst.
The sentence worth memorizing comes directly from Google Search Central: "From Google Search's perspective, optimizing for generative AI search is optimizing for the search experience, and thus still SEO."
The entire technical specification
Google's requirement for appearing in generative AI features is deliberately minimal:
- The page must be indexed.
- The page must be eligible to be shown with a snippet.
That is the complete technical specification. No additional files. No proprietary markup. No separate crawl directives for AI bots beyond standard Search policies.
Google follows this with explicit advice most vendors omit: "Prioritize effective SEO strategies over 'AEO/GEO hacks.'" The acronyms appear in quotation marks in Google's own text.
What Google says does not work
Google's documentation calls out four categories of ineffective tactics:
Special schema for AI features — Google states directly that structured data is not required for generative AI features and that no special schema.org markup exists for them. If someone sells an "AI schema package," they are selling something Google says does not exist.
llms.txt and similar files — Not part of Google's retrieval or ranking systems for AI features.
Separate optimization workflows — AEO and GEO are rebranded SEO aimed at answer engines, not distinct technical disciplines.
Citation manipulation at scale — Falls under spam policies now enforced in both classic results and AI Overviews.
What actually moves the needle
Google's generative features draw from the same corpus as traditional search: useful content, clear structure, E-E-A-T signals, technical health, and policy compliance. Since June 2026, Search Console includes Search Generative AI performance reports — dedicated views of impressions within AI Overviews and AI Mode — letting publishers measure AI surface visibility with first-party data.
That reporting exists because AI visibility is real and measurable. It does not exist because AI visibility requires a parallel optimization stack.
Implications for agencies and publishers
If your AEO strategy is a checklist of technical additions bolted onto thin content, Google's documentation is a direct rebuke. If your AEO strategy is better SEO — clearer answers, stronger entities, faster pages, honest authorship, and content that deserves citation — you are aligned with Google's stated approach.
The September 2026 spam update reinforces this convergence. Tactics engineered purely for AI citation without user value are spam in Google's framework — enforceable in AI Overviews, not just blue links.
A practical reframing
Stop asking "how do we optimize for AI search separately?" Start asking:
- Does this page answer the query better than competitors?
- Would a journalist cite it as a primary source?
- Is it indexed, crawlable, and snippet-eligible?
- Does it comply with spam policies across both classic and generative surfaces?
Google's documentation is not subtle. The companies selling AEO shortcuts are betting their customers never read it.
The publishers who win in AI-mediated search will look identical to the publishers who won in classic search — just with a new performance report to track.

Comments
Loading comments…