
By Ryan Law
Director of Content Marketing at Ahrefs
But what exactly is llms.txt, who’s using it, and—more importantly—should you care?
llms.txt is a proposed standard for helping LLMs access and interpret structured content from websites. You can read the full proposal on llmstext.org.
In a nutshell, it’s a text file designed to tell LLMs where to find the good stuff: API documentation, return policies, product taxonomies, and other context-rich resources. The goal is to remove ambiguity by giving language models a curated map of high-value content, so they don’t have to guess what matters.
In theory, this sounds like a good idea. We already use files like robots.txt and sitemap.xml to help search engines understand what’s on a site and where to look. Why not apply the same logic to LLMs?
But importantly, no major LLM provider currently supports llms.txt. Not OpenAI. Not Anthropic. Not Google.
Google included llms.txt in their Agent2Agent (A2A) protocol, launched in April 2025—but that's effectively adding a proposed protocol into another proposed protocol. Notably, Google hasn't committed to crawling it yet.
As I said in the intro, llms.txt is a proposed standard. I could also propose a standard (let’s call it please-send-me-traffic-robot-overlords.txt), but unless the major LLM providers agree to use it, it’s pretty meaningless.
That’s where we’re at with llms.txt: it’s a speculative idea with no official adoption.
Don’t sleep on robots.txt
Here’s what an llms.txt file looks like in practice. This is a screenshot of Anthropic’s actual llms.txt file:
At its core, llms.txt is a Markdown document (a kind of specially formatted text file). It uses H2 headers to organize links to key resources. Here’s a sample structure you could use:
# llms.txt
## Docs
- /api.md
A summary of API methods, authentication, rate limits, and example requests.
- /quickstart.md
A setup guide to help developers start using the platform quickly.
## Policies
- /terms.md
Legal terms outlining service usage.
- /returns.md
Information about return eligibility and processing.
## Products
- /catalog.md
A structured index of product categories, SKUs, and metadata.
- /sizing-guide.md
A reference guide for product sizing across categories.You can make your own llms.txt in minutes:
You can create it yourself or use a free llms.txt generator (like this one) to make it for you.
I've read about some developers also experimenting with LLM-specific metadata in their llms.txt files, like token budgets or preferred file formats (but there’s no evidence that this is respected by crawlers or LLM models).
We studied 137,000 domains in Ahrefs Web Analytics and found that 28% publish an llms.txt file—more than one in four sites—despite no major AI platform ever committing to read it. Adoption is being driven by speculation that AI tools might start consuming the file, not by any confirmation that they do.
Sidenote
You can also see a list of companies using llms.txt at directory.llmstxt.cloud—a community-maintained index of public llms.txt files.
Here are a few examples:
But what about the big players?
So far, no major LLM provider has formally adopted llms.txt as part of their crawler protocol:
This highlights an important point: creating an llms.txt is not the same as enforcing it in crawler behavior. Right now, most LLM vendors treat llms.txt as an interesting idea, and not something that they’ve agreed to prioritize and follow.
In my opinion, no, not yet.
There’s no evidence that llms.txt improves AI retrieval, boosts traffic, or enhances model accuracy. And no provider has committed to parsing it.
In fact, when we looked at who actually reads these files, the answer was almost nobody. Of the ~38,000 domains in our study with a valid llms.txt, 97% received zero requests for it in May 2026. No bots, no humans, nothing.
But it’s also very easy to set up. If you already have structured content like product pages or developer docs, compiling an llms.txt is trivial. It’s a Markdown file, hosted on your own website. There might be no observed benefit, but there’s also little risk (although there is some risk, like making it easier for competitors to scrape your website).
I think llms.txt is gaining traction because we all want to influence LLM visibility, but we lack the tools to do it. So we latch onto ideas that feel like control.
How to track AI visibility
But in my personal view, llms.txt is a solution in search of a problem. Search engines already crawl and understand your content using existing standards like robots.txt and sitemap.xml. LLMs use much of the same infrastructure.
Google itself has been sending mixed messages. In late May 2026, its new guide on optimizing for generative AI features told site owners—in a section literally titled “mythbusting”—that machine-readable files like llms.txt aren’t needed to appear in generative AI search. Days later, the Chrome team shipped an llms.txt check inside Lighthouse’s experimental audits.
When pressed on the contradiction, John Mueller explained that llms.txt is “not done for search”—it’s a “temporary crutch, perhaps to save some tokens” for AI coding tools parsing developer docs, not something most sites need to worry about.
He made a similar point earlier in a Reddit post, comparing llms.txt to the old keywords meta tag:

John Mueller, Search Advocate, Google

Ryan Law is the Director of Content Marketing at Ahrefs. Ryan has 13 years experience as a writer, content strategist, team lead, marketing director, VP, CMO, and agency founder. He’s helped dozens of companies improve their content marketing and SEO, including Google, Zapier, GoDaddy, Clearbit, and Algolia. He’s also a novelist and the creator of two content marketing courses.
Join 284K marketers for weekly news, useful reads, industry updates, and the memes you didn’t know you needed.
Explore what’s inside the newsletter →