Tools

llms.txt Generator

Create an llms.txt file that lists the site's chosen summary and priority pages for systems that read it. 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.

Write a concise summary you would be comfortable having an AI system use to describe your site. Write it, do not leave it to be inferred.

Key pages

Optional pages

Optional is a reserved heading in the specification: it marks links that can be skipped when a shorter context is needed. 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.

How the number is worked out

  • llms.txt is a proposal, not a standard every engine honours yet. It sits next to your sitemap and your robots file rather than replacing either.
  • Add a short note explaining what each linked page covers. A list of URLs repeats your sitemap; a line saying what each page answers is the part a model can use.
  • The title is the only part the specification actually requires. The summary states how you want systems that read the file to describe the site.

What comes out

You will see

  • A complete llms.txt file in the format the proposal defines
  • Your summary as a blockquote, which is the line most likely to be quoted
  • Key pages as a linked list, each with a note saying what it answers
  • An Optional section, which is the reserved heading for pages a reader may skip
  • A copy button and a download that saves it under the right filename
  • A note on where the file goes and what it does not replace

How to use it

Three steps, and the third one is the point

  1. Name the site and write one sentence

    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.

  2. List the pages that answer questions

    List the pages that settle something: sizing, shipping, returns, how the product is made and who it is for. Leave the rest of the sitemap out.

  3. Add a note to every link

    A list of URLs repeats your sitemap. A line saying what each page answers is the part that is worth reading.

What llms.txt is

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 worth stating plainly because adoption has not been confirmed.

What it costs to publish is ten minutes. For engines that read llms.txt, the file states your chosen summary and priority pages.

The llms.txt Generator result panel, first state
One key page, with a note saying what it settles rather than only its URL.
The llms.txt Generator result panel, second state
An optional page added. Optional is a reserved heading in the specification, so it gets its own section instead of joining the main list.

Why each link needs a description

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.

Write one note per link and one summary for the site.

The tool

What this one does

  • Follows the format the proposal defines

    H1 name, blockquote summary, section headings, and links written as markdown with a note after the colon.

  • Uses Optional as the reserved heading

    Optional has a specific meaning in the specification: links that can be skipped when a shorter context is needed. Background and archive pages belong there.

  • Asks for the sentence, rather than inferring one

    The summary is the line most likely to come back in an answer. Nothing here writes it for you.

  • Leaves out what you did not fill in

    Empty rows do not appear. There is no filler text and no placeholder company description in the file you take away.

  • Downloads under the right name

    The file saves as llms.txt, which is the only filename that works, and the tool says where on the domain it belongs.

  • States what it does not replace

    It sits alongside your sitemap and your robots file. Neither of those stops mattering because this one exists.

Reading the result

What each line is telling you

The H1 line
Your site name. This is the only part the specification requires.
The blockquote
Your one sentence. Read it back and ask whether you would be happy seeing it quoted, because that is the job it is doing.
Key pages
The main section. Each row is a link and a note, and the note is the part that answers a question.
Optional
A reserved heading, not a general second section. Only use it for pages that can be dropped without losing the point.

The calculation is only the start
of the diagnosis.

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

What you can do with it

  • Publish it and see what changes

    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.

  • Write the sentence you want repeated

    Most brand descriptions in an answer are assembled from whatever text was nearest. This is a chance to supply one on purpose.

  • List pages that answer common questions

    Sizing, returns, materials, compatibility. The pages a support inbox keeps answering are the pages a model keeps being asked about.

  • Keep it short on purpose

    Keep the list focused on the pages that answer your audience's most important questions. A complete URL inventory belongs in the sitemap.

Questions

llms.txt Generator questions

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.

Do AI search engines read it?

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.

Does it replace robots.txt or my sitemap?

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.

How many pages should I list?

Few enough that the selection means something. A dozen pages that settle real questions is more useful than two hundred that repeat the sitemap.

What goes in the Optional section?

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.

Is my data sent anywhere?

No. The file is built in your browser and never leaves it until you download it.

The rest of the set

Fifteen more, all free, all in the browser

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