Where does the llms.txt file go?
At the root of your domain, so it is reachable at yoursite.com/llms.txt. It goes next to robots.txt rather than inside a folder.
The file an answer engine reads before it reads your site. It says which pages carry the answers, in your words rather than in a crawler guess.
Name your site, write the one line you want quoted back, list the pages that answer real questions, and take the file away.
Everything here is worked out in your browser. Nothing you type is sent anywhere, and there is no account to make.
This is the sentence most likely to be quoted back. Write it, do not leave it to be inferred.
Key pages
Optional pages
Optional is a reserved heading in the specification: it marks links a reader may skip when it needs a shorter context. Background and archive pages belong here.
Result
Fill in the fields on the left. Nothing is generated until you do, and nothing is filled in on your behalf.
What comes out
How to use it
The sentence matters more than the list. It is the description a model is most likely to repeat, and if you do not write it, something else writes it for you.
Not your whole sitemap. The pages that settle something: sizing, shipping, returns, how the product is made, who it is for.
A list of URLs repeats your sitemap. A line saying what each page answers is the part that is worth reading.
llms.txt is a plain markdown file that sits at the root of a domain, next to robots.txt, and describes the site to a language model in the site owner words. It has a defined shape: a heading with the name, a blockquote summary, then sections of links where each link carries a short note.
It is a proposal rather than a standard every engine honours. That is the accurate position and it is worth stating plainly, because plenty of pages about this file imply an adoption that has not been confirmed.
What it costs to publish is ten minutes. What it changes, if an engine does read it, is which sentence describes you and which pages get reached for first.
A generator that turns your sitemap into a list of URLs has done nothing: the sitemap already exists and a crawler already has it. The part a model can use is the note next to each link, because it says what the page settles.
Compare a bare link to a sizing page with a link that says it explains how to pick a size without measuring. The second one can be matched to a question. The first one has to be opened and guessed at.
That is why the note field sits next to every row here rather than being optional, and why the summary line is asked for before anything else.
The tool
H1 name, blockquote summary, section headings, and links written as markdown with a note after the colon.
Optional has a specific meaning in the specification: links a reader can skip when it needs a shorter context. Background and archive pages belong there.
The summary is the line most likely to come back in an answer. Nothing here writes it for you.
Empty rows do not appear. There is no filler text and no placeholder company description in the file you take away.
The file saves as llms.txt, which is the only filename that works, and the tool says where on the domain it belongs.
It sits alongside your sitemap and your robots file. Neither of those stops mattering because this one exists.
Reading the result
We look at your search visibility across Google and the answer engines, and tell you what is costing you orders. No charge for the first look.
In practice
The file costs almost nothing to put up. Save it at the root of the domain and watch which pages get cited over the following months.
Most brand descriptions in an answer are assembled from whatever text was nearest. This is a chance to supply one on purpose.
Sizing, returns, materials, compatibility. The pages a support inbox keeps answering are the pages a model keeps being asked about.
The value is in the selection. A file that lists everything has selected nothing, and reads exactly like the sitemap it duplicates.
Questions
At the root of your domain, so it is reachable at yoursite.com/llms.txt. It goes next to robots.txt rather than inside a folder.
It is a proposal, and adoption is not something we can confirm on your behalf. Treat it as cheap to publish and unproved in effect, rather than as a setting that switches something on.
Neither. Robots.txt controls access, the sitemap lists pages for crawling, and this file describes what the important pages answer. Publishing one does not let you drop the other two.
Few enough that the selection means something. A dozen pages that settle real questions is more useful than two hundred that repeat the sitemap.
Pages a reader can skip when it needs a shorter context: company history, archived posts, background material. It is a reserved heading with that specific meaning, not a place for a second list.
No. The file is built in your browser and never leaves it until you download it.
The rest of the set
llms.txt is a file you publish, not a standard anyone is obliged to read. Serving it costs almost nothing, and whatever value it has sits in what it points at rather than in the file itself.
Where this comes up