AI Signal 489
llms.txt proposed as AI-readable site guide, but no major AI platform confirms usage
llms.txt is a voluntary Markdown file intended to guide AI crawlers to a site’s most important pages, yet no major AI provider has confirmed that it reads or acts on the file.
Adoption remains low, with roughly one in ten sites hosting llms.txt and AI crawlers making only a few hundred requests among hundreds of millions of bot events. Implementing the file costs little and can help uncover site-structure issues, but engineers should not depend on it for AI-driven traffic or citations.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
About 10% of domains have llms.txt, and only one of the fifty most AI-cited domains includes the file.
AI crawlers rarely request llms.txt, with only a few hundred hits observed in over 500 million bot events, and no major AI company has committed to using it.
Creating the file takes roughly twenty minutes, can reveal duplication or orphaned content, and serves as a low-cost optional bet on future agentic routing.
THE READ
What the cluster adds up to.
llms.txt is proposed as a simple Markdown file placed at the root of a website that lists the most important pages for AI systems to prioritize. The file is not an official standard and no major AI platform has publicly confirmed that it reads or acts on its contents. Its purpose is to give agents a machine-readable overview of a site’s authoritative content. Unlike robots.txt, it does not restrict access but merely suggests what to read first.
Adoption data show limited uptake: an SE Ranking study of 300,000 domains found a 10.13% prevalence, and among the fifty domains most often cited by AI, only one had the file. Monitoring of over 500 million AI bot events by Limy.ai recorded only a few hundred direct requests to /llms.txt over a 90-day window. The overwhelming majority of crawler traffic still targets HTML pages instead. These figures indicate that the file is largely ignored by current AI agents.
Despite the low usage, creating an llms.txt file requires only about twenty minutes of effort. The process forces teams to write concise descriptions of their top pages, which can surface duplication, orphaned content, or pages that lack substantive information. Several teams report gaining more value from this audit than from the file itself. The file also represents a cheap optional position should agentic routing ever standardize on such a machine-readable surface.
However, the file stops working as a reliable signal because major providers such as Google have explicitly stated they do not support llms.txt and have likened it to the discredited keywords meta tag. A significant share of existing files are junk defaults generated by plugins rather than curated lists, further diluting any potential benefit. Engineers should prioritize improving crawl access, content quality, and answer structure before investing time in llms.txt. Relying on the file for AI citation or traffic gains is not supported by the available evidence.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER
↗