Skip to content
regensbot
DEV-AIF-02Should2 of 6 in AIF

Spend no effort on llms.txt, AI text files or AI-specific markup for Google

Level
Should

Recommended: skip it only for a reason you can name.

Documentation

Documented

At least one cited Google document states or supports it.

Covered

Automatic

Decided from one URL.

Why it matters

Google's guide says new machine-readable files, AI text files or special markup are not needed to appear in Search, which ignores them, so they neither help nor harm. Structured data is not required for generative AI search either, though it remains worth using for rich results, and the same processed markup feeds classic results and AI answers. Google repeated it on serving day: AI Overviews and AI Mode are standard search features, not rich results, and need no structured data to function.

How to meet it

Do not build llms.txt or AI-only endpoints for Google; invest instead in documented structured data types (DEV-SDA-03) and crawlable, server-rendered content. If llms.txt is published for other tools, make it answer 200 (Lighthouse's optional llms.txt audit flags a server error), and do not publish markdown copies of HTML pages for agents: a community speaker warned they are duplicates, possibly even a cloaking risk. The same speaker cited a study of almost 40,000 sites in which 97% of llms.txt files got no AI agent hits in a month; Ahrefs' published study (June 2026) reports the same 97%.

How to test it

The backlog has no tickets for llms.txt or AI-only markup aimed at Google.

How Regensbot covers it

AutomaticNeedsOne URL

Decided from one URL.

An audit reads the response, the headers, the HTML, robots.txt, the sitemaps and the structured data, and the finding shows the evidence it saw.

How verdicts workWhat you connect

Sources

Google documents03

  1. 01Optimizing your website for generative AI features on Google SearchGoogle Search Central (opens in a new tab)
  2. 02AI features and your websiteGoogle Search Central (opens in a new tab)
  3. 03llms.txtChrome for Developers (opens in a new tab)

Claims in the knowledge base15

  1. D1-C061SourceHow Search works and where's AI?Google's documentation
  2. D1-C054ConfirmedHow Search works and where's AI?Shown on screen
  3. D2-C480SourceWhat is Structured Data and why we need it on the internet.Google's documentation
  4. D2-C476ConsistentWhat is Structured Data and why we need it on the internet.Said on stage
  5. D2-C479n/aWhat is Structured Data and why we need it on the internet.The author's interpretation
  6. D3-C325ConfirmedHow Search results are bornSaid on stage
  7. D3-C326SourceHow Search results are bornGoogle's documentation
  8. D3-C328n/aHow Search results are bornThe author's interpretation
  9. D1-C271ConsistentLightning session A: Automation and AISaid on stage
  10. D1-C272ConsistentLightning session A: Automation and AISaid on stage
  11. D1-C454ConfirmedQ&ASaid on stage
  12. D1-C455ConsistentQ&ASaid on stage
  13. D1-C460SourceQ&AGoogle's documentation
  14. D1-C473ConsistentQ&ASaid on stage
  15. D1-C505n/aLightning session A: Automation and AIThe author's interpretation

Claim IDs refer to the Search Central Live 2026 knowledge base. The knowledge base (opens in a new tab)

Confirmed
Google's documentation states the same thing.
Consistent
Google's documentation supports it without stating it.
Source
The claim is the cited document itself.
n/a
Nothing to verify: a quotation, framing, opinion or analysis.

Audit

Check it on your site.

One audit checks a URL against all 138 requirements and returns one finding for each, with its source. One URL decides 66; for each of the others, the finding says which source to connect.