How do you appear in Google AI Overviews?
Google publishes the answer. Be indexed and eligible for a snippet, keep your content crawlable, use semantic HTML, give the page a clear structure, and write something that is not a commodity. It also lists what does not help, and llms.txt is on that list.
The failure Google's guide does not cover is the common one. Our own site shipped 133 characters of text to a crawler that does not run JavaScript, while showing 8,368 to a browser — the entire argument was invisible to the assistants it was written about.
Our own measurement: measured on upai.lat before and after prerendering, September 2026.
What does Google say to do?
Publish content with a point of view, structure it with real headings, keep it crawlable, use semantic HTML, and make sure the page is eligible to show with a snippet.
It also points at JavaScript SEO practice, which matters more than the sentence suggests — see the last section.
For commerce and local businesses it adds two more: keep Merchant Center feeds accurate and keep your Business Profile current. And it points at Search Console's generative AI performance report as the place to measure — first-party, free, and limited to Google.
What does Google say not to bother with?
Five things, named directly: llms.txt and other special files, chunking content into fragments, rewriting pages for machines, overfocusing on structured data, and pursuing inauthentic mentions across the web.
| What people do | What Google says |
|---|---|
| Publish an llms.txt | Search ignores it; it will neither harm nor help |
| Break content into small chunks | Not required |
| Rewrite pages specifically for AI | Not required |
| Add structured data everywhere | Not required for generative AI search |
| Buy or seed mentions across the web | Listed as something not to do |
"You don't need to create new machine readable files, AI text files, markup, or Markdown to appear in Google Search (including its generative AI capabilities), as Google Search itself doesn't use them."
What does the guide leave out?
The most common technical reason a page is never read: it only exists after JavaScript runs. Googlebot executes JavaScript, so Google's own guidance can afford to treat this as solved. The other assistants' crawlers are widely reported not to.
We found this on our own site. A request without a browser returned 133 characters of text — an empty shell — while a browser saw 8,368. Every figure, every source and every argument existed only after the page had run its JavaScript. Our robots.txt explicitly invited fifteen AI crawlers into a room with nothing in it.
Check yours before changing anything else: request your own page without a browser and count the text that comes back. If the answer is a few hundred characters, nothing else on this list matters yet.
Questions people ask next
- Does structured data help?
- Google says not to overfocus on it and that it is not required for generative AI search. It does not hurt and it helps other surfaces, so it is worth having and it is not the lever.
- Where do I measure this?
- Search Console has a generative AI performance report. It is free and first-party, and it covers Google only — which is the catch, because Google is one of four surfaces your buyers use.
- Does any of this apply to ChatGPT?
- No, and be careful with anyone who says it does. Google's guidance is about Google Search. The other assistants publish far less about how they choose sources, which is exactly why measuring all four is the only way to know where you stand.
Sources
Last updated 2026-09-25.