llms.txt generator and validator

How to use the llms.txt generator

To use the llms.txt generator, enter your site's name and a one-paragraph summary, group the pages that matter under section headings, and give each link a title, a full URL and a one-line note. Then copy or download the file and upload it to the root of your site. The file rebuilds as you type.

1. Name the site. The name becomes the H1, the one part of the file the format requires.
2. Write the summary. One paragraph of plain facts: what you sell, who it is for, where, and how buying or pricing works. It becomes the blockquote.
3. Add detail text only if it helps. Notes on how to read the links, or rules a reader should know. Paragraphs and lists are fine. Headings are not.
4. Group your best pages into sections. Use headings a person would understand, such as Products, Pricing, Policies and Guides. Pick the pages that answer real questions, not every page.
5. Give each link a note. Say in one line what the page answers. Put links a reader could skip in the Optional section.
6. Copy or download the file. "Check this file" sends it to the checker, so you can see it pass before you publish.
7. Publish it at /llms.txt. Then open the address to confirm that it loads as plain text.

New to the file itself? The guide to llms.txt explains what it is, shows a real one and helps you decide whether your site needs it.

By Kurt Philip, Founder

Worked examples: three files and what the checker says

The three examples below are built and checked by the same code as the tools above. Example Bike Shop is made up, and the examples show the format, not a recommended set of pages for a store.

1. The file the form starts with

The default values in the generator give a file of 22 lines and 971 characters: the H1, a one-line summary, a short detail paragraph with a list, 2 named sections and the Optional section, with 5 links in all. Sent to the checker, it returns no errors and no warnings. 10 checks passed.

2. The smallest valid file

A name alone is a complete llms.txt file, because the H1 is the only required part:

# Example Bike Shop

The checker returns no errors for it, with 2 warnings that are both practical advice: there is no summary, and there are no sections, so a reader has nowhere to go next. Valid is not the same as useful.

3. A file with mistakes, checked and fixed

The checker above starts with a file of 18 lines that has several common mistakes. It reports 3 errors and 6 warnings, listed in full in the tool. The check each one fails, and its fix:

The corrected file:

# Example Bike Shop

> Example Bike Shop is a made-up online store that sells commuter and touring bikes.

## Products

- [Commuter bikes](https://www.example.com/commuter-bikes/): The commuter range, with frame sizes and prices
- [Touring bikes](https://www.example.com/touring-bikes/): The touring range, with frame sizes and prices

## Policies

- [Shipping](https://www.example.com/shipping/): Shipping costs and delivery times

## Guides

- [Bike size guide](https://www.example.com/size-guide/): How to choose a frame size from your height

It returns no errors and no warnings. 8 checks passed. For a real file, see the excerpt from this site's own llms.txt in the guide, or paste convertica.org/llms.txt into the checker.

Where does the llms.txt file go?

The llms.txt file goes at the root of your site, so that it loads at https://yourdomain.com/llms.txt, next to robots.txt and the sitemap. The proposal also allows a file at a subpath, such as /docs/llms.txt, which covers the pages under that path. Our advice is to serve it as plain text or Markdown, not wrapped in a web page.

The file the generator downloads is plain text in UTF-8, named llms.txt, with no byte-order mark. The format allows one at the start of the file, but it is not needed.

• Static site or site generator: put llms.txt in the folder that is published as the site root, or generate it during the build.
• WordPress: llmstxt.org lists Yoast SEO and AIOSEO as plugins that generate the file. Use one source, a plugin or your own file, not both.
• Hosted site builders: check whether the platform already publishes one. llmstxt.org lists Wix as generating a file for every site.
• Any other host: upload the file to the web root with SFTP or the host's file manager.

How to check that the published file works

1. Open yourdomain.com/llms.txt in a browser. You should see the Markdown as plain text, not your site's design.
2. Copy what the address returns and paste it into the checker. If the server is sending a web page, the checker says so on the first line.
3. Make sure robots.txt and your firewall do not block the file or the pages it lists for the crawlers you want to reach.
4. Click a few of the links from the published file. A link to a missing page wastes the reader's effort.

How does llms.txt relate to robots.txt and the sitemap?

llms.txt, robots.txt and sitemap.xml sit side by side at the root of a site and do different jobs. robots.txt tells crawlers what they may access, the sitemap lists every page you want indexed, and llms.txt is a short, curated reading list. llms.txt grants nothing and blocks nothing: access is still set in robots.txt.

Keep the three consistent. Do not list a page in llms.txt that robots.txt blocks for the crawlers you want to reach, and do not block /llms.txt itself. The guide has a side-by-side comparison of the three files, and the AI visibility checker looks at a live site, including its robots.txt rules for AI crawlers.

What to do after you publish llms.txt

After you publish llms.txt, test it, keep it in step with the site, and then go back to the pages it points to. The file is a signpost. An AI tool that follows one of its links still has to find the price, the policy and the product on the page itself, in the HTML, in plain words.

1. Test it with an AI tool. The proposal's own advice: give an agent only your llms.txt and ask it questions about your business. Fix whatever it gets wrong.
2. Keep one source of truth. If the summary states a price or a return window, it has to match the page and the structured data. A buyer who hears one thing from an assistant and reads another on your page has a reason to doubt both, and doubt is what stops a sale.
3. Regenerate it when pages change. A hand-made file drifts. This site builds its own llms.txt from the same data as its pages, so a deleted page drops out of the file.
4. Check the pages behind the links. Convertica's free CRO audit runs eight checks on a page, and one of them is agent readiness: whether an AI agent can read what the page sells, the price and the policies.

llms.txt generator FAQ