Skip to the content

Free generator, runs in your browser

llms.txt Generator

Give language models a clean map of your site. Fill in the name, a one sentence summary and the links that matter, and copy a valid llms.txt.

Write an llms.txt

Fill in the fields. The Markdown updates as you type.

One or two sentences. It becomes the blockquote under the title.

One link per line, in the form: title | url | short note. The note is optional.

llms.txt

Why use the llms.txt Generator

Follows the proposal

An H1 title, a blockquote summary, optional details and H2 sections of links, in that order.

Sections and notes

Group links into sections and add a short note to each, the way the format intends.

Optional section

Mark secondary links as Optional so tools with a small context can skip them.

Private

The file is written in your browser. Nothing is uploaded.

When to use the llms.txt Generator

Documentation

Point models at the getting started guide, the API reference and the changelog.

SaaS products

List pricing, features, security and support pages.

Publishers

Link the main topic hubs and the editorial policies.

Open source

Link the readme, the docs and the contribution guide.

Agencies

Ship an llms.txt as part of every new site.

Personal sites

Describe who you are and link your main work.

Understanding llms.txt

How to use the generator

  1. 1Name and summary. The name becomes the H1, the summary the blockquote. Keep the summary to one or two sentences.
  2. 2Details. Add anything a model should know, such as what the product is not.
  3. 3Sections. Add a section per topic and one link per line in the form Title | url | note.
  4. 4Publish. Save the file as llms.txt at the root of your site, served as text.

What to include

The pages a model needs to answer questions about your site accurately: what it is, how it works, how much it costs, the policies. Leave out navigation pages, tag archives and anything that changes daily.

Expectations

llms.txt is an emerging convention. Some AI tools and agent frameworks read it, major assistants have not committed to it. It is cheap to publish and useful documentation either way.

Privacy and availability

The generator runs entirely in your browser. Nothing you type is sent to Aback or anywhere else, and it keeps working offline once the page has loaded.

Copy or download the result and publish it on your own site. Then check the live file with the matching checker, because what crawlers see is what your server sends.

Frequently asked questions

What is llms.txt?

A Markdown file at the root of a site that gives language models a short, curated summary and the most important links.

Where do I publish it?

At /llms.txt on your domain, served as text/plain or text/markdown.

How many links should it have?

Enough to cover what matters, usually ten to fifty. It is a curated index, not a sitemap.

What is the Optional section?

A section named Optional holds links that can be skipped when a tool has little room, as the proposal describes.

Do I also need llms-full.txt?

It is optional. It inlines the content of the linked pages so a tool can read everything in one request.

Does it replace robots.txt or the sitemap?

No. robots.txt controls crawling, the sitemap lists every page, llms.txt is a curated overview for models.

How do I check it after publishing?

Run the llms.txt validator. It checks the format and requests a sample of the links.

↑ ↓ to move↵ to openesc to close