llms.txt
llms.txt is a proposal for publishing a Markdown file that describes a website, or part of it, and points to material useful for AI tools. It can live at /llms.txt and, under the current proposal, also in a subdirectory such as /docs/llms.txt.
What the file can contain
The file uses Markdown to briefly introduce a project, give guidance and link to detailed material. The current proposal recommends pointing to content that is easy for agents to read, such as Markdown versions of documentation. The description should help someone find an answer rather than repeat the promotional slogans from your homepage.
Check the scope and version of the format in the proposal’s documentation before implementing it. Using the name llms.txt says nothing about whether a particular app can read the file or does so automatically. Judge support for the tools you actually use instead of assuming all chatbots behave the same way.
Why it doesn’t replace robots.txt or a sitemap
robots.txt sets the rules for crawlers fetching content, and a sitemap lists URLs meant to be discovered. llms.txt is meant to help navigate your material. It doesn’t grant access permissions, remove server blocks or protect private documentation. These files can coexist, but they solve different problems.
Google says you don’t need any extra AI text files to appear in its AI features. So a missing llms.txt isn’t, on its own, evidence of a visibility problem. First check that your public pages are accessible, your content is clear and your pages link to each other in the usual way.
Common mistake: promising growth from adding the file
Publishing the file doesn’t confirm that a chatbot visited it, used it or recommends your brand more often. Distinguish technical possibility from an observed effect. If you’re considering it, define a specific use case, check support in the relevant tool and estimate the work needed to keep it updated. For a small website without documentation, this can be a lower priority than improving your service descriptions.
Example
A company that develops a software library publishes a short introduction and links to installation steps, examples and API documentation. A tool that supports the format can use it to find the right material, while other systems may still rely only on regular pages.
Key takeaway
Treat llms.txt as an optional way of organizing context, not a mandatory recipe for visibility. If you maintain one, keep the links current and the descriptions consistent with the documentation users see.