Google says llms.txt doesn't affect rankings — now what?

If you published an llms.txt in the last year, you have probably now read the headline: Google says it does nothing for rankings. That is true, and it is also less interesting than it sounds. The useful question is not whether Google reads the file — it is who does.

What Google actually said

In June 2026 Google updated its AI-features guidance and was unusually blunt: it is "completely fine if you decide to create and maintain LLMS.txt files (or other similar files) for other services or systems that use these files. Doing so won't harm (nor help) your visibility or rankings in Google Search, as Google Search ignores them" (Search Engine Land).

Google's own documentation makes the same point positively: "You don't need to create new machine readable files, AI text files, or markup to appear in these features" (Google Search Central). What it recommends instead is unglamorous and correct — crawlable pages, helpful text-based content, accurate structured data, current business information.

Read the sentence carefully, though. Three claims are in it, and only one is negative:

Why that is not the end of it

Search is one audience. It is no longer the only one that reads your site.

The honest state of adoption is small on both sides. About 8.7% of the top 1,000 websites had an llms.txt as of June 2026 (Rankability), and Ahrefs found that 97% of the llms.txt files it studied received zero requests in May 2026 (Ahrefs). Anyone telling you the file is already essential is guessing.

So the case for keeping one is not traffic. It is that the file costs almost nothing, carries no ranking risk by Google's own statement, and pays off in three places that have nothing to do with search:

1. Assistants that fetch your site directly when a customer asks about you by name.
2. Agentic browsers deciding which of your pages to open before they open any.
3. Your own assistant — a curated brief is the cleanest possible input to a knowledge index.

That third one is the quiet winner. The work of writing an llms.txt — deciding which five pages actually matter and stating your hours, area and prices in plain sentences — is the same work that makes your own assistant accurate. See the knowledge guide for how a source is indexed, and our own /llms.txt for the shape.

Change what you measure

Stop measuring it as SEO. Measure it as machine readability:

Monthly check — /llms.txt
[ ] Every fact still true: hours, prices, service area, contact  [CHECK]
[ ] Every link still resolves (no 404s, no redirects)            [CHECK]
[ ] Requests to /llms.txt in server logs, with user agents       [CHECK]
[ ] The pages it points at still answer the question they claim  [CHECK]
Not a metric: search rankings. Google ignores this file.

A stale file is genuinely worse than none, because assistants repeat what it says. That is the only real risk in the whole exercise.

Ask your AI assistant to audit yours

Fetch https://[your-site]/llms.txt and check it against the page it points to.
For each link: does it resolve, and does the target page still say what the note
claims? Then list every factual statement in the file — hours, prices, service
area, contact — and tell me which ones you cannot confirm from the live site.
Mark those [CHECK]. Finish with the three pages a customer asks about most that
the file does not mention.

What actually moves the needle

If you want AI systems to do more than read you, the next step is letting them act. WebMCP lets a page expose real actions — book, check an order, start a return — with the visitor confirming each one, and the page tools guide is the setup. Compared with a text file that search ignores, that is where the leverage now is.

For the file itself, our earlier piece has the copy-paste template: why your website needs an llms.txt. And if you would rather see an assistant answer from your pages than argue about file formats, build one from your URL — pricing starts small.