llms.txt is a Markdown file at the root of a website, at /llms.txt, that gives AI tools a short summary of the site and a curated list of links to its most useful pages. Jeremy Howard proposed it in September 2024, and Anthropic, OpenAI and Google publish one for their developer docs.
Who publishes it, who checks for it and what Google says about it.
Anthropic, OpenAI and Google publish llms.txt files for their developer documentation, at platform.claude.com, developers.openai.com and ai.google.dev/gemini-api/docs.
Lighthouse’s agentic browsing audits include an llms.txt check. It flags a server error, and a missing file counts as not applicable.
Jeremy Howard published the proposal at llmstxt.org on September 3, 2024, and updated it to version 2 on August 10, 2026.
Google’s guidance on AI features says you don’t need new machine-readable files, AI text files or markup to appear in AI Overviews and AI Mode.
The proposal defines a small Markdown structure, in this order. Only the H1 is required. The file usually lives at the site root, but it can also sit under a subpath such as /docs/llms.txt.
The name of the site or project.
A short description with the key facts an AI tool needs to understand the rest of the file.
Paragraphs or lists without headings that add context, such as regions served or how to read the links.
Each section is a Markdown list of [name](url) links, each optionally followed by a colon and a short note.
Links under an H2 named Optional can be skipped when an AI tool needs a shorter context.
Ploy’s own file follows the format: an H1, a two-sentence summary and eight H2 sections, from What Ploy does to Company information, with 173 links.
Ploy generates it on each request from the site’s page lists, blog and library, so a new post appears without anyone editing the file. It also has a section on connecting AI assistants through the Ploy MCP.
The homepage points to the file with an HTTP Link header, </llms.txt>; rel="service-doc", one of the discovery signals the agent readiness audit checks.
List the pages an AI tool needs to explain your product: pricing, product and feature pages, docs, comparisons and key guides. Leave out tag pages, legal pages and thin archives, or move them under Optional.
Use your site or company name as the H1, then a one- or two-sentence blockquote that says what you do and who it is for.
Use plain section names such as Product, Docs or Comparisons. Write each entry as a Markdown link followed by a colon and a one-line note.
Publish the file at your site root so it returns a 200 status with a plain text or Markdown content type. Lighthouse flags a server error.
Generate the file from your CMS or page list, or review it whenever you add a key page. An llms.txt generator can draft one from your sitemap, but trim the result to the pages that matter.
All three sit at the site root, and none replaces another. robots.txt controls what crawlers may fetch, sitemap.xml lists what exists, and llms.txt picks what is worth reading.
| Question | llms.txt | robots.txt | sitemap.xml |
|---|---|---|---|
| Purpose | Summarize the site and point AI tools to key pages | Tell crawlers which URLs they may fetch | List the URLs search engines should crawl |
| Format | Markdown | Plain-text rules such as User-agent and Disallow | XML |
| Controls access | No | Yes, for crawlers that follow it | No |
| Status | Community proposal | IETF Proposed Standard, RFC 9309 (2022) | Sitemaps protocol supported by major search engines |
For AI agents that take actions on a page rather than read it, see What is WebMCP?

Ploy checks whether AI assistants can find, read and act on your site, then fixes the gaps it can and reports the rest. Each run uses AI credits.