An llms.txt example, line by line

Here is a complete llms.txt example for a small software company, followed by what each line does. If you would rather start from your own site than from a template, the seogeoaeo.ai llms.txt Generator drafts the same structure from your homepage, using only pages it could load.

The example

# Northwind Invoices

> Northwind Invoices is web-based invoicing software for freelancers and small agencies. It sends invoices, tracks payments and exports reports for accountants.

Northwind is a fictional company used for this example. Prices are listed in euros and include VAT.

## Product

- [Features](https://northwind.example/features): What the app does, by task
- [Pricing](https://northwind.example/pricing): Plans and what each includes

## Help

- [Getting started](https://northwind.example/help/start.md): Set up an account and send a first invoice
- [Payment methods](https://northwind.example/help/payments.md): Cards, bank transfer and payment links
- [Refund policy](https://northwind.example/legal/refunds): When and how refunds are issued

## Optional

- [Company blog](https://northwind.example/blog): Product news and guides

Line by line

The H1. The first line, the name after a single hash, is the only part the llms.txt proposal requires. Use the name people search for, not a slogan. If your company and product have different names, pick the one customers type and mention the other in the summary.

The blockquote. The line starting with > is the summary. An agent may read only this far, so it should say what you are, who it is for and the main things it does. Two sentences are plenty.

The context paragraph. Plain text after the summary, with no headings, holds facts an agent needs to read the rest correctly. Currency, regions served and naming quirks belong here.

The H2 sections. Each ## heading starts a list of links. The names are up to you. Group by what a person would ask about: product, help, policies, docs.

The link lines. Each line is a Markdown link, then a colon and a short note. The note tells an agent which page answers which question, so it can pick one link instead of fetching all of them.

The .md links. Two help links end in .md. The proposal suggests offering a clean Markdown copy of a page at the same address with .md added, because agents read it more easily than HTML. This is optional; normal page links are fine.

The Optional section. ## Optional is a convention for links an agent can skip when it is short on space. Put nice-to-have material here, such as the blog, changelog or press page, so the main sections stay short.

What this example leaves out

The last row is the one people get wrong. A link to a page that was moved or never existed sends the agent nowhere. Before you publish, open every link in the file once, and do it again whenever you rename or remove pages.

Turn the example into your own file

You can copy the pattern by hand. For a faster start, run your homepage through the seogeoaeo.ai llms.txt Generator. It costs 15 credits per run, takes your site URL and an optional site name for the H1, and returns a Markdown draft whose every link is a public URL the run fetched. Pages built only with JavaScript may not appear, so add those yourself.

Then publish the file at /llms.txt as plain text and run it through the AI Agent Readiness Checker, also on seogeoaeo.ai, which checks llms.txt syntax and links.

On WordPress, Yoast SEO's free llms.txt feature builds and refreshes a file for you, which can be simpler than maintaining one by hand.

Keep expectations modest. llms.txt is an optional file. It is not a Google search requirement, and it helps only the agents that choose to read it.