llms.txt is a proposed standard file that gives AI crawlers a clean, simple map of your site’s most important content, helping them understand and use your pages. Think of it as a guide written for large language models rather than search engines. It is new, its adoption is still uncertain, and it takes about five minutes to add.
This explainer covers how llms.txt works, its honest adoption status, how to create one for WordPress, whether you should bother, and how it differs from robots.txt and your sitemap.
How llms.txt works
The idea behind llms.txt is simple. It is a plain text file, written in readable Markdown, that you place at the root of your site so it lives at a predictable address like yoursite.com/llms.txt. Inside, you list your most important pages with short descriptions, giving an AI model a clean, curated overview of what your site offers and where the key information sits, without the clutter of navigation, ads, and scripts that fill a normal page.
The format is meant to be easy for a language model to parse: a title, a short summary of your site, and organized lists of links to your best content, each with a brief note on what it covers. There is also a proposed fuller variant, sometimes called llms full txt, which can include more complete content rather than just links, giving models even more to work with.
The whole point is to hand AI systems a tidy, machine friendly summary of your site so they can find and represent your content accurately.
The honest adoption status
Here is where honesty matters, because llms.txt is still a proposal rather than an established, universally used standard. It was suggested as a helpful convention, and some sites have adopted it, but it is important to be clear that not all AI companies confirm they read or use it. Support is mixed and evolving, and there is genuine debate in the community about whether major AI systems actually consume the file today or ignore it.
This uncertainty is the heart of the discussion. Supporters argue it is a sensible, low effort step that could help as AI adoption grows, while skeptics point out that without confirmed use by the big AI providers, it may currently do little. Both views are reasonable.
Because this is moving quickly, you should verify the current adoption status yourself before relying on it, since which companies support it can change from month to month. Treat any claim that a specific AI definitely uses llms.txt with caution and check the latest position.
What the evidence now says, specifically
When this guide first said support was mixed and evolving, that was accurate. Enough data has since arrived to be far more specific, and the picture is not encouraging.
Google has stated its position outright. Its May 2026 guidance on optimising for AI surfaces lists llms.txt among the things site owners can ignore.
The reasoning is that AI Overviews and AI Mode draw on the same Search index as ordinary results, so a separate file has nothing to add to how Google sees you.
John Mueller has been blunter, comparing llms.txt to the keywords meta tag, noting that no AI services were using it and that bots were not even requesting the file.
The keywords meta tag comparison is a pointed one. That tag also seemed sensible, cost nothing, and was ignored for years while people kept filling it in.
The usage data supports him. An Ahrefs study of 137,000 sites found 97 percent of llms.txt files received no traffic at all in May 2026. Separate monitoring of over 500 million AI bot visits found only a few hundred requests for the file.
And the adoption picture is the most telling part. An SE Ranking study of 300,000 domains found about 10 percent had the file. Among the fifty domains cited most often by AI, only one did.
In other words, the sites actually winning at AI citation are almost entirely sites without an llms.txt. Whatever is earning those citations, it is not this file.
No major provider has committed either. OpenAI, Anthropic, Google, Meta and Mistral have none of them publicly said they use it as a signal in their production answer surfaces.
So should you still add one?
The earlier framing of a cheap bet with no downside was fair when nobody knew. It reads differently now that we do.
For AI search visibility, no. Not because it is harmful, but because the evidence that it does nothing is now substantial and comes from the search engine itself.
Time spent on it is time not spent on the things that are demonstrably earning citations, which is the only real cost involved.
There is one case where it still makes sense. If you run documentation and you want an AI agent, an internal tool or a developer integration to find a clean, structured route through it, a curated Markdown index is genuinely useful.
That is a different job from search visibility. It is a convenience for systems you or your users deliberately point at the file, not a signal to crawlers you hope will find it.
If you already have one, leave it. It costs nothing to keep and it may yet be adopted, in which case you are already set up.
Just do not count it as work done on AI visibility, and do not let it displace the content and citation work that the same evidence shows actually moves the needle.
How to create one for WordPress
Adding an llms.txt file to a WordPress site is straightforward, with two main routes. The manual method is to create a plain text file named llms.txt, write your site title, a short description, and organized lists of your most important pages with brief notes, then upload it to the root directory of your site so it is reachable at yoursite.com/llms.txt.
You can do this over your hosting file manager or by SFTP, the same place your other root files live.
The easier route for most people is a plugin. A growing number of WordPress plugins can generate and maintain an llms.txt file for you, pulling in your key pages automatically and keeping the file updated as your content changes, which saves you editing it by hand.
If you prefer not to touch files directly, search the plugin directory for a current, well reviewed llms.txt option and follow its setup. Either way, once the file is live, check it loads correctly in your browser at the root address. Keep it focused on your genuinely important content rather than listing every page.
Should you bother?
The practical question is whether it is worth your time, and the honest answer weighs a small effort against an uncertain payoff. The case for is compelling in its simplicity: it takes about five minutes, there is a possible upside if AI systems increasingly use it, and there is essentially zero downside, since a well formed llms.txt file does not harm your SEO or your site.
If you like being an early mover on emerging standards, it is a cheap bet.
The case against is equally honest: because consumption by major AI providers is not confirmed, you may be adding a file that little currently reads, so it could do nothing for now. Neither view is wrong. Given the tiny effort and the lack of any downside, a reasonable position is to add it if you can do so quickly, treat it as a low risk experiment rather than a guaranteed benefit, and keep an eye on whether adoption grows.
Do not expect miracles, and do not skip more proven work to do it.
llms.txt vs robots.txt vs sitemap
These three files are often confused, so here is what each actually controls. Robots.txt tells crawlers which parts of your site they may or may not access, acting as a set of rules about what is off limits. Your XML sitemap lists your pages to help search engines discover and index all of your content, acting as a complete directory for crawling.
Llms.txt is different from both: it does not block anything and is not a full index, but instead offers AI models a curated, human chosen summary of your most important content in a clean, readable format. In short, robots.txt controls access, the sitemap aids discovery of everything, and llms.txt guides AI to your best content. They serve different purposes and can coexist, so adding llms.txt does not replace or conflict with the other two.
Verdict
Our recommendation is pragmatic. llms.txt is a sensible, low effort idea whose real world impact is still unproven, since major AI providers have not all confirmed they use it. Because it takes only minutes, carries no downside, and might help as AI search grows, adding one is a reasonable early mover move, especially with a plugin that maintains it for you.
Just keep your expectations realistic, do not neglect proven SEO to do it, and verify the current adoption status yourself, since this space is changing fast.
For the bigger picture on optimizing for AI, see our guide on how to rank in Google AI Overviews.
Frequently asked questions
Does Google use llms.txt?
Google has not confirmed that it uses llms.txt as part of how it crawls or ranks content, and support among AI providers generally is mixed and evolving. Because this can change, you should verify the current position rather than assume any specific company reads the file. Treat llms.txt as an emerging proposal with uncertain consumption today, not a confirmed Google requirement or ranking factor.
Where do I put llms.txt?
Place llms.txt in the root directory of your site so it is accessible at yoursite.com/llms.txt, the same location as robots.txt. On WordPress you can upload it via your hosting file manager or SFTP, or use a plugin that creates and serves it for you. After adding it, check that it loads correctly in your browser at the root address to confirm it is in the right place.
Does llms.txt block AI crawlers?
No, llms.txt does not block AI crawlers. It is not an access control file; instead it offers AI models a curated map of your important content. If you want to control or block crawler access, that is the job of robots.txt and related directives. llms.txt is about guiding AI to your best content in a clean format, not restricting what crawlers can reach.
Is llms.txt the same as robots.txt?
No, they are different. Robots.txt tells crawlers which parts of your site they may access and is a widely established standard. llms.txt is a newer proposal that gives AI models a readable summary of your most important content, without controlling access. They serve different purposes, do not conflict, and can both exist on your site at the same time, each doing its own job.
Is it still worth creating an llms.txt file?
Not for AI search visibility. An Ahrefs study of 137,000 sites found 97 percent of llms.txt files received no traffic at all in May 2026, and an SE Ranking study of 300,000 domains found that among the fifty domains cited most often by AI, only one had the file.
No major provider has committed to using it either. It still has a genuine use as a curated Markdown index for documentation that agents or developer tools are deliberately pointed at, which is a different job from search visibility. If you already have one, keeping it costs nothing.