How is it different from robots.txt and sitemap.xml?
- llms.txt curates background information and important links so an agent can find more detailed, preferably machine-readable pages when needed.
- robots.txt states crawling rules. llms.txt does not replace it and does not block access to a page.
- sitemap.xml lists pages for discovery and indexing. llms.txt is usually shorter and explains which pages matter for a topic.
What should the file contain?
Proposal v2 permits /llms.txt at the site root or a scoped file such as /docs/llms.txt. Begin with one H1 naming the site or project. A short summary, additional context, and links grouped under H2 headings help readers decide what to open next. For example:Example Store
Official product information, policies, and support resources.
Products
- Product catalog: Current product pages and availability.
Help
- Shipping policy: Regions, costs, and delivery times.
- Contact: How to ask about a product or order.
How to test its usefulness
- Open the target URL and confirm it returns the intended Markdown, not a login or error page.
- Follow several links and confirm they still work and contain accurate information.
- Test a real agent that uses llms.txt with specific questions: can it find the right page and cite the underlying content?
- To assess business outcomes, examine server logs, site analytics and each clearly defined GEOly metric separately. A crawler request, citation in an AI answer, referral session and conversion are different signals.