llms.txt example and generator
Copy a SaaS example or draft your own file. llms.txt is a proposal for a short Markdown guide to a site’s content.
A SaaS example to copy
Acme Tasks is a fictional SaaS product. Replace its name, description and example.com links with your own information and real Markdown pages before publishing.
# Acme Tasks
> Acme Tasks is a SaaS tool for planning team projects.
Public product information is linked below. Account pages require sign-in.
## Product
- [Features](https://example.com/features.md): What the product does.
- [Pricing](https://example.com/pricing.md): Plans and included features.
## Docs
- [Getting started](https://example.com/docs/start.md): Set up a first project.
- [API reference](https://example.com/docs/api.md): Authentication and endpoints.
## Optional
- [Changelog](https://example.com/changelog.md): Product updates.
What each line is for
Format source: llmstxt.org. Read 14 Oct 2026.
| Line | What it does |
|---|---|
| # Acme Tasks | What it doesThe H1 names the site. This is the proposal’s only required section. |
| > Acme Tasks… | What it doesA blockquote gives a short summary. |
| Public product information… | What it doesA paragraph adds context for interpreting the links. |
| ## Product | What it doesAn H2 groups links to product information. |
| - [Features](…): … | What it doesA named link to the features page, followed by a short note. |
| - [Pricing](…): … | What it doesA named link to the pricing page and what it covers. |
| ## Docs | What it doesAn H2 starts another group of links. |
| - [Getting started](…): … | What it doesA link to the setup guide with a short description. |
| - [API reference](…): … | What it doesA link to the API documentation with a short description. |
| ## Optional | What it doesThe convention marks these links as secondary when a shorter context is needed. |
| - [Changelog](…): … | What it doesA secondary link to product updates. |
| Blank lines | What it doesSeparate the Markdown blocks so the file is easier to read. |
What AEOprobe checks
Our audit fetches /llms.txt at your site’s root. It counts the file as present when the response succeeds, is not served as text/html, and has a non-empty body within our 512 KiB limit.
Our basic format rule requires at least three non-empty lines and at least two lines starting with #. This is AEOprobe’s rule: the proposal itself requires only an H1 title.
The example passes this format rule. Passing does not tell us whether an assistant uses the file or whether its links work.
Draft your own file
Enter your site details below. The draft updates in your browser; you can copy it or download it as llms.txt.
Input
Preview
# Your Site Name > A short description of your site.
Questions
Do I need an llms.txt file?
It is a proposal, not proof that an assistant reads your site. AEOprobe checks the file’s availability and basic structure, not assistant adoption.
Where do I put the file?
The proposal allows the site root or a subpath. AEOprobe checks the root: for example, https://example.com/llms.txt.
Does the generator send my input anywhere?
No. The draft is built in your browser from what you type. Review it and edit the links before you publish.
Check your published file
The free audit checks that /llms.txt is there, can be read and passes AEOprobe’s basic format rule.
Run free audit