llms.txt: a useful map, not a magic switch

Give the reader a map

The llms.txt proposal describes a Markdown file that introduces a site and links to useful information. Its August 2026 revision also describes links between web pages and clean Markdown versions. Think of it as a curated starting point rather than a copy of every page.

For a service business, our suggested map would point to the service description, coverage area, request process and important policies. Keep the summary short enough to navigate. Put the detailed rules on the relevant pages, where people can check them too.

Keep one set of facts

Suppose a restaurant changes its catering notice from two days to three. Updating only a text file while leaving the menu page unchanged creates conflicting sources. An assistant may encounter either version, and a customer may reasonably rely on the one they see.

The operational job is to maintain an approved source of facts and keep published formats aligned. Assign someone to review changes, record when a policy was verified and test a few representative questions. Adding a file is the small part; keeping it accurate is the continuing work.

Understand the limits

llms.txt is a proposal, not a universal requirement or an access-control mechanism. Google says its AI search features do not require special AI text files. Do not buy a guarantee of discovery based on one filename.

The file also should not contain private customer data, invitation tokens or internal notes. It is published website content. Our recommendation is to use it where it creates a clearer path through reliable information, alongside ordinary pages and working links. Then inspect whether the agents you test actually follow that path.

Sources & further reading

Sources checked 2026-10-12. Recommendations and examples reflect Welvia’s approach; they do not imply a partnership or guaranteed result.