Google's Agentic Browsing Lighthouse Scoring Factor: The llms.txt File

Part 3 of the AI Visibility Series. The honest truth about llms.txt: what it is, who actually reads it, and whether your business needs one right now.

In Part 1 we met the accessibility tree, and in Part 2 we kept the page from jumping. This time we are looking at the most confusing item on the whole list, the one with a name that sounds technical and a story full of mixed messages: llms.txt.

Here is the honest version, which is exactly what makes this worth reading. Google's own teams cannot agree on whether this file matters. One part of Google says you do not need it. Another part of Google now checks your site for it. Let me untangle that, because once you see it clearly, the decision for your business gets easy.

What llms.txt actually is

An llms.txt file is a plain text file you place at the root of your domain, at yourname.com/llms.txt. It is written in Markdown, which is just simple text with a few light formatting marks. Think of it as a short, hand-made map of your site, written for AI instead of for people.

A sitemap lists every URL for a search crawler. An llms.txt file does something gentler. It points an AI to the handful of pages you most want it to read and understand, with a sentence about each one. It does not block anything or grant access, the way robots.txt does. It simply says, here is who we are, and here are the pages that matter most.

The format was proposed in September 2024 by Jeremy Howard, and the full spec lives at llmstxt.org. It is short enough to read in a few minutes, which is rare for a web standard.

Why it is on the AI readiness list at all

This is the third factor in Google's new agentic browsing score in Lighthouse. The idea is about efficiency. When an AI agent lands on your site with no map, it has to crawl around and guess at your structure, which wastes its limited attention. Google's own note on the audit says it plainly: without this file, agents may spend more time crawling your site just to work out what it is and what matters.

So the promise is simple. A clean llms.txt hands the AI a cheat sheet, so it spends its effort understanding your best pages instead of wandering through your menu.

The honest part: two worlds, one confusing file

Here is where most articles go quiet, and where you deserve the straight story.

Google Search has said, clearly and more than once, that you do not need llms.txt to show up in its AI features like AI Overviews and AI Mode. In its own guide on optimizing for generative AI, Google lists special AI text files among the things you do not need to create. One of Google's own people, John Mueller, compared the file to the old keywords meta tag, a tag that stopped mattering many years ago. As of now, the major AI providers have not confirmed that they use these files, and server logs show their bots are mostly not even asking for them.

And yet, at the same time, a different team at Google built the new Lighthouse agentic browsing audit, and that audit checks whether your llms.txt exists and whether it is well formed.

So the same company both shrugs at the file and grades you on it. That is not a trick question, it is just two teams looking at two different jobs. The Search team is talking about ranking and showing up in AI answers, where the file does not help. The Chrome team is talking about agents that browse and act on your site, where a map can save time. Same file, two worlds, two honest answers.

What this means for you: an llms.txt will not lift your Google rankings, and it will not magically get you cited in ChatGPT. What it can do is help the next generation of browsing agents find their footing faster, and it clears one check on an audit your clients and competitors are starting to run.

What a well-formed file looks like

If you do make one, the Lighthouse audit does not just check that it exists. It also checks that it is built correctly. A file that is there but broken still fails. Per the published spec and the audit, a good file has a clear shape.

The order matters, and so does restraint. The spec is strict about what belongs and what does not. No images, no HTML, no tables, no code blocks, and no extra headings inside your link sections. Plain Markdown text and Markdown link lists only. The simpler you keep it, the more reliably it gets read.

Here is a short, well-formed example for a sample business.

# Riverside Dental

> A family and cosmetic dental practice in Yakima, Washington, welcoming new patients of all ages.

Riverside Dental offers cleanings, fillings, crowns, and cosmetic care. Use the links below to learn about services, booking, and visiting the office.

## Main pages
- [Services](https://www.riversidedental.com/services): Cleanings, fillings, crowns, whitening, and emergency care.
- [Book an appointment](https://www.riversidedental.com/book): How to request a visit and what to expect.
- [New patients](https://www.riversidedental.com/new-patients): Insurance, forms, and first-visit details.
- [Contact and hours](https://www.riversidedental.com/contact): Address, phone, and office hours.

## Optional
- [Blog](https://www.riversidedental.com/blog): Dental care tips and practice news.

Notice what it is: one H1 with the business name, a one-line summary in a blockquote, a sentence of context, then short link lists with a plain description after each link. That is the whole craft.

How to check and create yours

The fastest check needs nothing but a browser. Type your domain followed by /llms.txt, like yourname.com/llms.txt. If you see plain text, you have a file. If you see a 404 page, you do not.

To see the official audit result, you run Lighthouse, the free tool from Google. This is the part that trips people up, because the feature is new and still rolling out. A short while ago you could only see these checks in a beta version of Chrome. That has changed. As of May 2026, the agentic browsing checks ship in the standard tool, and the easiest place to see them is PageSpeed Insights, a free Google website. Go to pagespeed.web.dev, enter your address, and look for the agentic browsing result next to the usual scores.

If you would rather run it in the browser itself, you need Chrome version 150 or newer, which is the regular, up to date Chrome that most people already have, not a beta. Open the developer tools, find the Lighthouse tab, and run the agentic browsing category. One honest note: Google still labels this category experimental and under development, so the exact wording and layout may look a little different by the time you try it.

A word of honest caution about the generators. It is easy to auto-create a giant file and forget it. A stale map that points to pages you have changed or removed is worse than no map. If you make one, keep it short, keep it true, and update it when your key pages change.

How to handle it in Webflow

Webflow does not let you drop a raw file at your domain root the way traditional hosting does, so there is a small trick to it. You have two clean options.

• Use a hosting rule or proxy. If your domain runs through a service like Cloudflare, you can serve a plain text llms.txt at the root through a rule or worker, while your Webflow site runs as normal. This is the most spec-correct route, since the file truly lives at yourname.com/llms.txt.
• Publish a page and point to it. You can create a simple page that outputs the content as plain text, though getting the exact root path and the right content type can be fiddly on Webflow. If the strict root path is not reachable, this is a reasonable fallback.

Honestly, for most local service businesses, this is a low priority fix, not a fire. It is a nice-to-have that clears one audit check. Do the accessibility tree and layout stability work first, because those help people, search, and AI all at once. Add the llms.txt when you have a calm afternoon.

If you would rather not handle any of this yourself, that is exactly what ongoing support is for. Keeping an llms.txt current, along with your accessibility and search health, is part of our monthly website support and maintenance. And if you are reading this on a platform that makes a simple file feel impossible, like WordPress, Wix, or Squarespace, that friction is telling you something. When the platform fights you on the basics, a website rebuild and platform takeover onto Webflow gives you a clean foundation where this kind of thing is simple.

Four myths worth retiring

• “llms.txt will get me into ChatGPT.” Not today. The major AI tools have not confirmed they use these files, and their bots are mostly not requesting them. It may help browsing agents, but it is not a ticket into any chatbot's answers.
• “It will boost my Google rankings.” No. Google Search has said you do not need it, and one of its own people compared it to the long-dead keywords meta tag. It is not a ranking signal.
• “More is better, so I should list every page.” The opposite. The whole point is a short, curated map of your best pages. A bloated file buries the very pages you want noticed.
• “I can generate it once and forget it.” A map is only useful if it is current. An out-of-date file that points to missing or changed pages does more harm than good. Keep it small enough to maintain.

The bottom line

llms.txt is a small, honest, low-cost file. It will not transform your visibility, and anyone selling it as a magic AI ranking trick is overselling. What it is: a tidy map that helps browsing agents find your best pages faster, and one clean pass on an audit that is becoming standard. Make a short, true one when you have time, keep it current, and put your real energy into the foundations that help everyone at once.

The web is being read by machines now, as well as people. A simple, honest map is a kind thing to leave for both.

See where your site stands

Want to know whether your site has a well-formed llms.txt, and how it scores on the rest of the AI readiness checks? Get a free AI Visibility Report from certified accessibility and Webflow specialists. We will manually check how your business shows up when people ask Claude for a recommendation, then explain your new Lighthouse agentic browsing scores in clear, plain language. You get a personalized report within 24 hours. No sales pitch, just value.

Request yours at gracefulwebstudio.com/ai-visibility-report.

Next in the series, Part 4: WebMCP, the frontier of the agentic web, and why labeling your forms and buttons for machines is the natural next step after labeling them for screen readers.

Written by Crystal Scott, Certified Professional in Web Accessibility (CPWA) and founder of Graceful Web Studio.