# llms.txt

> What llms.txt proposes, how it differs from robots.txt and a sitemap, and the honest state of whether anything actually consumes it.

Source: https://netweft.com/glossary/llms-txt
Updated: 2026-09-12

**A proposed convention: a markdown file at a site's root that indexes the site's content for large language models, with a companion llms-full.txt containing the whole site as one document. It is a convention, not a standard, and no model is obliged to read it.**

`llms.txt` proposes that a site publish, at its root, a markdown index of its
own content written for a model rather than for a crawler: a title, a short
description of the site, and a list of links with a sentence about each.
`llms-full.txt` is the maximal version — the whole site as one document, so a
model can take it in a single fetch.

**It is not robots.txt and it is not a sitemap.** `robots.txt` grants or
withholds permission. A sitemap lists URLs for discovery. `llms.txt` is neither
of those: it is an editorial summary, and its value is in the sentences, not in
the list.

**The honest position on adoption.** It is a proposed convention, not a
standard, and there is no public confirmation from a major model provider that
it is consumed. Publishing one is cheap and carries no risk; claiming it does
something measurable would be a claim nobody can currently support.

What is measurable is the thing underneath it. A site that can produce a good
`llms.txt` is a site whose pages are also available as plain text — and a model
that can read a page as markdown instead of parsing HTML around it makes fewer
mistakes about what the page said. That is why
[this site serves every page twice](/blog/reading-a-workspace-from-an-agent):
once as HTML, and once as the same document at the same path plus `.md`.