llms.txt generator

Fill in your site name, a one-line summary and the pages that matter. We write a spec-conformant llms.txt you can drop at your site root.

Site or project name *

Summary

Becomes the > blockquote under the title.

Details (optional)

Section 1

Section heading (H2)

Sections with no links are left out. Links in a section named “Optional” can be skipped by tools that need a shorter context.

llms.txt

# Your site name

The H1 name is the only required part of the file. Add one.

Upload the file to your site root so it loads at https://yourdomain.com/llms.txt.

What llms.txt is

llms.txt is a proposed standard, published by Jeremy Howard of Answer.AI at llmstxt.org in September 2024. The idea is simple: put a short Markdown file at /llms.txt that tells a language model what your site is and which pages matter, with links. Web pages are full of navigation, scripts and ads; a curated list is easier for a model to use inside a limited context window.

The format

The spec defines a fixed order. This generator follows it:

An H1 with the site or project name. This is the only required part.
A blockquote summary: one or two sentences with the key facts.
Optional paragraphs or lists with more detail, with no headings.
H2 sections, each a list of links in the form - [title](url): notes.
A section named Optional holds links a tool can skip when it needs a shorter context.

# Acme Invoicing

> Invoicing software for freelancers.

## Docs

- [Getting started](https://acme.example/docs/start.md): Set up and send a first invoice

## Optional

- [Blog](https://acme.example/blog)

What it does and doesn’t do

Adoption is partial. Some AI coding assistants and agents read llms.txt when they’re pointed at a site, and several documentation platforms generate one automatically. The major AI search products haven’t said their crawlers use it to choose which sources to cite. There’s no evidence it affects Google rankings, and Google has said Search doesn’t use it.

So why bother? It takes ten minutes, it has no downside, and it forces a useful exercise: deciding which pages actually explain your product. We publish one generated from our page registry, so it never goes stale: launchranked.com/llms.txt.

What to put in it

The pages that answer the basics: what it is, who it’s for, what it costs, how to start.
Docs, pricing, comparisons and policies. Skip tag archives and thin pages.
Factual notes after each link. Describe the page; don’t sell it.
Absolute URLs. The spec also suggests offering clean Markdown copies of pages at the same URL plus .md.
Update it when your key pages change, or generate it from your sitemap or CMS.

Questions

Is llms.txt an official standard?

No. It's a proposal published at llmstxt.org in September 2024, not a W3C or IETF standard. Anyone can adopt it, and no AI company is obliged to read it.

Does llms.txt help SEO?

There's no evidence it affects Google rankings, and Google has said Search doesn't use it. Treat it as documentation for AI tools and agents, not a ranking tactic.

What's the difference between llms.txt and robots.txt?

robots.txt tells crawlers what they may fetch. llms.txt suggests what's worth reading and in what order. llms.txt doesn't block or allow anything; access is still controlled by robots.txt.

Where do I put the file?

At the root of your site, so it loads at https://yourdomain.com/llms.txt as plain text. In Next.js, put it in public/ or generate it from a route handler. In WordPress, upload it to the web root or use a plugin that serves it.

Free launch

Launching something? Get a page that ranks.

Launch free on LaunchRanked: a permanent, SEO-ready product page, a weekly leaderboard slot and a followed link after human review. No badge required.

Launch free See Autopilot