llms.txt generator for your website

What is llms.txt?

llms.txt is a Markdown file at the root of a website that gives language models a short, curated map of the site. Jeremy Howard proposed it in September 2024 at llmstxt.org. It is a community proposal, not an IETF or W3C standard.

Think of it as a reading list for agents. A web page is full of navigation, scripts and layout. The file points to the pages that matter and says in one line what each of them contains.

What does an llms.txt file look like?

The proposal defines a simple structure, in this order:

1. An H1 with the name of the site or project. It is the only required part.
2. A blockquote with a short summary.
3. Optional paragraphs or lists with more detail, but no headings.
4. H2 sections that hold lists of links. Each item is a Markdown link with an optional note after a colon.
5. An optional H2 section called Optional. Agents can skip its links when they need a shorter context.

# Example Co

> Example Co makes invoicing software for freelancers. This file lists the pages that explain the product, the API and the pricing.

Prices are in euros and include VAT. The API is documented in the Docs section.

## Docs

- [Getting started](https://example.com/docs/start.md): Install the SDK and send your first invoice
- [API reference](https://example.com/docs/api.md): Every endpoint with request and response examples

## Product

- [Pricing](https://example.com/pricing.md): Plans, limits and what each plan includes

## Optional

- [Changelog](https://example.com/changelog.md): Release notes for every version

Write the summary and the notes as plain facts. An agent that reads “Plans, limits and what each plan includes” knows what it will find, while “Our amazing plans” tells it nothing. Prefer links to clean Markdown or simple HTML pages over pages that need JavaScript to show their content.

How do you create an llms.txt file with the llms.txt generator?

1. 1

   Name your site

   Enter the name of your site or product and a one-sentence summary. Write the summary the way you would describe the site to a new colleague.

2. 2

   Add your key pages

   Group the pages that matter into sections such as Docs, Product and Pricing. Give every link a short, factual note.

3. 3

   Move the rest to Optional

   Put secondary pages, such as the changelog or older articles, in the Optional section so that agents can skip them.

4. 4

   Copy the file

   Copy the generated Markdown and save it as llms.txt in UTF-8.

Where do you host llms.txt, and what is llms-full.txt?

Serve the file at /llms.txt in the root of your domain, for example https://example.com/llms.txt. The proposal also allows a file in a subpath such as /docs/llms.txt for the pages under it. In Next.js, put the file in the public folder. On other stacks, upload it to the web root. Use absolute URLs, publish one file per host and make sure it returns a 200 response rather than a login page.

llms-full.txt is a widely used companion convention that is not part of the proposal on llmstxt.org. It is one Markdown file with the full text of your key pages, so an agent can read everything in a single request. It suits documentation sites, while a large shop should skip it. Serpel publishes both files for its own site at llms.txt and llms-full.txt.

Does llms.txt work? The honest status

No major AI provider has publicly confirmed that its production systems read llms.txt. In June 2025 Google’s John Mueller wrote that no AI system currently uses llms.txt and pointed to server logs as evidence.

Coding agents and some developer tools do read the file when you point them at a documentation site, which is where it helps most. Treat it as cheap and low-risk, not as a ranking factor. It takes minutes to publish and does no harm, and it does not replace crawlable HTML, good titles or an open robots.txt.

llms.txt checklist

• The file starts with one H1 that names the site.
• A one- or two-sentence summary follows in a blockquote.
• Every link is an absolute URL that returns 200.
• Every link has a short, factual note instead of a slogan.
• Only pages you want agents to use are listed, and secondary pages sit under Optional.
• The file is served as UTF-8 text at /llms.txt.
• Your robots.txt does not block the file or the listed pages for the crawlers you care about.
• You update the file when pages are added, renamed or removed.

Looking for finished files to learn from? See our collection of llms.txt examples.