Google splits llms.txt guidance between Search and Lighthouse audits

Google is sending two different signals about llms.txt, and that is the story. Search guidance says you do not need extra files or special markup to show up in AI Overviews or AI Mode, while Lighthouse now treats llms.txt as part of an experimental agentic browsing audit.

Search says stay on the basics

If your goal is visibility in Google Search’s generative AI experiences, the message is blunt: no special llms.txt work is required. Google Search Central says there are no additional requirements to appear in AI Overviews or AI Mode, and its generative AI features guide says you do not need to create new machine-readable files, AI text files, markup, or Markdown to appear in generative AI search.

That lines up with Google’s May 21, 2025 Search Central blog post, which kept the advice simple: unique, valuable content, good page experience, and accessible technical foundations. In other words, the same SEO playbook still matters. Google’s own framing says the underpinnings of what it has long advised carry across to these AI experiences, so chasing a brand-new file format is not the lever to pull if you want Search visibility.

This is where a lot of teams get tripped up. llms.txt sounds like a neat switch for AI discovery, but Google Search’s guidance says it is not a prerequisite for Search surfaces. If you treat it like a universal AI optimization requirement, you risk spending time on a file that does nothing for the product you actually care about.

Lighthouse is talking about a different problem

Chrome’s Lighthouse is not making the same claim. Its llms.txt audit describes the file as an emerging convention for LLMs and AI agents, and it says providing the file is optional at the moment. That wording matters because it frames llms.txt as part of a machine-interaction workflow, not a Search ranking signal.

Lighthouse’s Agentic Browsing category goes even further into experimental territory. Google describes that category and WebMCP support as experimental and based on proposed standards. Instead of a traditional 0-to-100 score, Lighthouse uses deterministic audits and a fractional pass ratio. That is a very different kind of check from the signals SEO teams usually track, and it tells you exactly where Google is putting this work: browser-agent readiness, not Search indexing policy.

Chrome DevTools 148 added agent-related features too, including the new Agentic Browsing audit category in Lighthouse and WebMCP-related tooling. That makes llms.txt look less like a Search mandate and more like one piece of an emerging browser automation stack. If you only see the Search docs, you miss that parallel track. If you only see Lighthouse, you overstate the importance of a file that Google Search says is unnecessary for generative search visibility.

Why the split matters in practice

The practical risk here is simple: following the wrong interpretation wastes effort and creates false confidence. If you publish llms.txt expecting it to improve your presence in AI Overviews, Search Central’s guidance says that is not the right assumption. If you ignore it entirely because Search says it is unnecessary, you may miss an experimental audit that matters for agentic browsing workflows and future browser behavior.

That is why this is not really a contradiction in ranking logic. It is a product-specific split between Search visibility and browser-agent readiness. A search feature, a browser audit, and an agentic browsing environment are related, but they are not the same thing. Google can be skeptical about llms.txt as a Search requirement and still test it as a machine-interaction signal in Chrome tooling without changing its Search advice.

For site owners, the consequence is operational discipline. Do not treat any single Google surface as definitive policy for every other surface. Search guidance is about what helps content surface in AI experiences on Search. Lighthouse’s agentic browsing work is about whether a site is legible to emerging automated agents. Those are adjacent goals, and they deserve separate decisions.

What to do on your site right now

Start with the fundamentals Google keeps repeating, because that is the part tied to Search visibility. Keep content useful, specific, and original. Make sure pages load cleanly, crawl cleanly, and remain accessible to Googlebot and real users. If your technical foundation is weak, llms.txt will not save you.

Then evaluate llms.txt as a separate experimental layer. If your team is building for browser agents, automation flows, or future machine-interaction checks, it may be worth testing. If your only objective is AI Overviews or AI Mode visibility, the file is not the first thing to optimize.

A practical workflow looks like this:

• Document which Google surface you are targeting: Search, browser-agent testing, or both.

• Test llms.txt in a controlled way rather than assuming it helps.

• Compare behavior across surfaces instead of assuming one signal transfers everywhere.

• Keep your core SEO work centered on content quality, page experience, and technical accessibility.

That approach is more honest than the hype cycle around llms.txt. It also protects teams from turning a speculative convention into a budget line item with no measurable upside.

Google’s own timeline shows the split clearly

The current posture did not appear out of nowhere. John Mueller previously compared llms.txt to the old keywords meta tag and said no AI services were using it at the time. That was a clear signal that Search skepticism was already baked in.

Later, at Search Central Live Deep Dive Asia Pacific 2025 in Bangkok from July 23 to 25, 2025, Google’s crawling, indexing, and AI messaging stayed anchored in normal SEO. Coverage from that event reported that Gary Illyes reiterated Google would not crawl llms.txt for AI Overviews and that normal SEO was sufficient for Google Search surfaces. That is the same line Search Central has been pushing: no extra machine-readable file is required to win visibility in its generative Search products.

Put those pieces together and the picture is hard to miss. Search says stick to foundational SEO. Lighthouse says llms.txt is an optional, emerging convention inside an experimental agentic browsing audit. Those are not the same instructions, and pretending they are can send a team down the wrong path fast.

The smart move is to stop asking whether llms.txt is a magic visibility switch and start asking which Google surface you are actually trying to influence. That is the difference between chasing noise and building for the systems that matter.