llms.txt Examples: 7 Real Files, Annotated, and Templates You Can Copy
A good llms.txt example is short: an H1 with your site name, a one-line summary in a blockquote, and a few H2 sections listing your most useful pages with a note on each. Below are seven real files we opened on October 17, 2026, from a 637-byte minimum to a 90 KB documentation index, what each does well or badly, and ready-to-edit templates for five common site types.

The format in 30 seconds
The llms.txt proposal (Jeremy Howard, September 2024) defines a Markdown file at /llms.txt with sections in a fixed order:
- H1 with the site or project name. This is the only required part.
- Blockquote with a short summary.
- Optional free text (paragraphs or lists, but no headings) with extra context.
- H2 sections with link lists, each item written as
- [Name](url): optional note. - An H2 called Optional for secondary links an agent can skip when it is short on context.
The proposal also suggests serving clean Markdown copies of important pages (for example page.html.md). If you want the long version with the robots.txt comparison, read our llms.txt guide; this page is about examples.
Who actually reads it (keep expectations honest)
Google is explicit: its page on AI features and your website says you don't need new machine-readable files, AI text files or markup to appear in AI Overviews and AI Mode. So llms.txt is not a ranking signal and not a way into Google's AI answers.
Where it does help is when an agent or a person deliberately points a tool at your site: a coding assistant reading your docs, a research agent asked to summarize your product, or someone pasting yoursite.com/llms.txt into a chat. That is why the best examples below come from developer documentation. For a small site it is a 20-minute courtesy, not a growth channel.
The 7 examples at a glance
Sizes and link counts are our own measurements of each live file on October 17, 2026. They change as sites update.
| # | File | Size | Links | Best lesson |
|---|---|---|---|---|
| 1 | llmstxt.org | ~0.6 KB | 3 | The minimum that is still useful |
| 2 | FastHTML | ~4.8 KB | 21 | Textbook structure, "things to remember" notes, a real Optional section |
| 3 | Svelte | ~1.7 KB | 7 | A hub that points to full, medium and small versions |
| 4 | Stripe Docs | ~93 KB | 454 | Direct instructions to agents; also what "too big" looks like |
| 5 | Vercel | ~5.2 KB | 27 | "When to use us" and "how agents should behave" sections |
| 6 | Shopify | ~12.5 KB | 71 | A marketing site organized by user goal, not by sitemap |
| 7 | Yoast | ~7.7 KB | 62 | A company and content site, with a few format slips to avoid |
1. llmstxt.org: the minimum viable file
The proposal's own file is an H1, a two-sentence blockquote and one Docs section with three links, each pointing to a .md version of a page and carrying a short note. Nothing else.
Copy this: if your site has five pages that matter, this is all you need. A short file that lists the right pages beats a long one that lists everything.
2. FastHTML: the textbook structure
FastHTML is the example the proposal itself was built around, and it shows every part of the format:
- A blockquote that says what the library is and what it is built on.
- A free-text list of things to remember, such as which frameworks it is not compatible with. This is the most useful idea in any file here: it heads off the mistakes a model is most likely to make about you.
- H2 sections Docs, API, Examples and an Optional section holding most of the tutorials.
Copy this: write three to five "things to remember" about your business. For a local bakery that might be "We do not deliver" or "Orders need 48 hours' notice." Those lines fix wrong AI answers more directly than any list of links.
3. Svelte: llms.txt as a hub for bigger files
Svelte's file is tiny because it is a router. One section links to three full-text bundles (complete, abridged and compressed documentation), another links to separate llms.txt files per package, and a Notes section explains what each version leaves out.
Copy this: only if you have a lot of documentation. A blog does not need size variants. But the habit of telling the reader what a link contains and what it omits is worth stealing for any file.
4. Stripe: instructions to agents, and a size warning
Stripe's file opens with plain instructions before any links: check package registries for the latest version instead of relying on remembered version numbers, and which sandbox type to use. Further down, a whole H2 is titled as instructions for LLM agents and says which APIs to prefer and which legacy ones never to recommend.
It also shows the cost of completeness: by our count it holds 454 links across 26 sections in about 93 KB. That is a lot of context for an agent to spend on a table of contents.
Copy this: the instruction style ("When someone asks about X, point them to Y; do not recommend Z"). Avoid: listing every page. A small site should stay well under 100 links; most need 15 to 40.
5. Vercel: tell agents when you are the right answer
Vercel's file has two sections most sites skip: When to use Vercel (a bullet list of jobs the product does) and How agents should use Vercel, which includes asking the user for approval before changing account resources. Its Optional section links to machine-readable extras such as a product taxonomy.
Copy this: a "When to use us" list in customer language. It is the closest thing in llms.txt to a positioning statement, and it is exactly what a research agent needs to recommend you for the right job and not for the wrong one.
6. Shopify: a marketing site organized by goal
Shopify is not a docs site, and its file shows how a business site can work. Sections follow what a visitor wants to do: start a business, build with AI, sell online, payments, sell in person, plans, help. Each link has a one-line note written for a buyer.
Two cautions. The notes read like ad copy in places, and superlatives do nothing for an agent trying to answer a factual question. There is also no Optional section, so an agent cannot tell which of the 71 links matter least.
Copy this: goal-based sections for a services or e-commerce site. Skip: sales claims; write what the page contains.
7. Yoast: a content company, with slips to avoid
Yoast's file covers products, its academy, integrations, events, help articles and legal pages. It is a good model for a site that is both a product and a publisher. It also shows small format slips:
- H3 subheadings (free and paid courses) inside H2 sections. The proposal only describes H2 file-list sections, so simple parsers may flatten or skip them.
- Many links with no note at all. Notes are optional, but a bare link tells an agent nothing about why to open it.
- No Optional section, even though legal pages and event archives are obvious candidates.
Copy this: the split between products and educational content. Fix: keep to H2 sections and give every link a note.
Copy-paste templates by site type
Replace everything in angle brackets. Keep the order: H1, blockquote, notes, H2 lists, Optional last.
Blog or niche publisher
# <Blog name>
> <Blog name> is an independent blog about <topic> for <audience>, written by <author> since <year>.
- Articles are based on <first-hand testing / experience as a ...>.
- We do not <sell X / give medical advice / accept paid reviews>.
## Start here
- [<Pillar guide>](https://example.com/guide/): <what it answers>
- [<Second pillar>](https://example.com/second/): <what it answers>
## Popular articles
- [<Title>](https://example.com/post-1/): <one-line summary>
## About
- [About the author](https://example.com/about/): <credentials, location>
- [Editorial policy](https://example.com/editorial/): <how posts are researched and updated>
## Optional
- [Archive](https://example.com/archive/): Full list of posts by date
Local business
# <Business name>
> <Business name> is a <type of business> in <city, region> serving <area> since <year>.
- Address: <street, city>. Hours: <days and hours>. Phone: <number>.
- We <do / do not> offer <delivery, emergency calls, online booking>.
## Services
- [<Service>](https://example.com/service/): <what is included, price range page if public>
## Book or contact
- [Contact](https://example.com/contact/): Phone, map and booking form
## Optional
- [Blog](https://example.com/blog/): Seasonal tips and news
SaaS or app
# <Product>
> <Product> helps <who> <do what> without <pain>.
## When to use <Product>
- <Job 1 in customer words>
- <Job 2>
## Things to remember
- <Product> does not <common wrong assumption>.
- Pricing: see the pricing page; there is a free plan for <limit>.
## Docs
- [Quickstart](https://example.com/docs/start.md): <first 10 minutes>
- [API reference](https://example.com/docs/api.md): <scope>
## Company
- [Pricing](https://example.com/pricing/): Plans and limits
- [Security](https://example.com/security/): Data handling
## Optional
- [Changelog](https://example.com/changelog/): Release notes
Online store
# <Store>
> <Store> sells <products> online to <countries>.
- Shipping: <regions, typical time>. Returns: <window>, see the returns page.
## Shop by category
- [<Category>](https://example.com/c/category/): <what is in it>
## Help
- [Shipping](https://example.com/shipping/): Costs and delivery times
- [Returns](https://example.com/returns/): How to return an item
## Optional
- [Size guide](https://example.com/sizes/): Measurements by brand
Prefer not to hand-write it? Our free llms.txt generator builds a first draft from your sitemap that you can then trim with the lessons above. On WordPress, see how to add llms.txt to WordPress.
Decision table: how big should your file be?
| Your site | Sections | Links | Extras worth adding |
|---|---|---|---|
| Local business, portfolio | 2–4 | 5–15 | Facts block: address, hours, what you don't do |
| Blog, under 100 posts | 3–5 | 15–40 | Author and editorial policy links |
| Store | 3–5 | 15–50 | Shipping and returns facts; categories, not products |
| SaaS | 4–7 | 20–60 | "When to use" and "Things to remember" |
| Large docs | Many | Hub + per-section files | Svelte-style hub, Markdown page copies |
These ranges are our editorial recommendation, not a rule from the proposal.
Checklist before you publish
- File is at
https://yoursite.com/llms.txt, returns HTTP 200 and is plain text or Markdown, not an HTML page. - Exactly one H1, then the blockquote.
- Every link is absolute, returns 200 and is not blocked by robots.txt or set to noindex.
- Every link has a note that says what the page contains.
- No marketing superlatives, no keyword lists, no prices that will go stale.
- Secondary links are in an Optional section at the end.
- AI crawlers you care about are not blocked from the pages you list. Our AI crawler checker shows that in one pass.
- You have a reminder to review the file when you publish or retire key pages.
What to do next
Start with the template for your site type, keep it under 40 links, and add three "things to remember" lines. Then remember that an agent reading your llms.txt will still judge the site behind it. If you want to know how your site looks from the outside before agents and partners do, run it through Satelo's free check: you get a Quality Score from 0 to 100 with the evidence behind each number, mostly from open data, in about 30 seconds.
FAQ
What is an example of an llms.txt file?
The smallest useful example is the one at llmstxt.org/llms.txt: an H1 with the name, a one-paragraph blockquote summary, and one Docs section with three links and short notes. FastHTML's file shows the full structure, including an Optional section.
What should be in an llms.txt file?
An H1 with your site name (the only required part), a short blockquote summary, optional notes, and H2 sections that list your most useful pages as Markdown links with a one-line note each. Put secondary links in a section called Optional.
Does Google use llms.txt?
Google says you don't need to create new machine-readable files, AI text files or markup to appear in AI Overviews or AI Mode. Treat llms.txt as a help for agents and tools that choose to read it, not as a Google ranking signal.
Where do I put the llms.txt file?
In the root of your site so it opens at yoursite.com/llms.txt. The proposal also allows files in subpaths such as /docs/llms.txt for a documentation section.
How long should llms.txt be?
There is no limit in the proposal. For a small site, 15 to 40 links is usually enough. Very large files, like Stripe's 90 KB documentation index, use a lot of an agent's context just for the table of contents.
What is the difference between llms.txt and llms-full.txt?
llms.txt is an index of links. llms-full.txt is a convention some sites use, such as Svelte, for a single file with the full text of their documentation. It is not part of the original proposal, and small sites rarely need it.
Read next




Check your site's Quality Score
Free, no sign-up: a 0–100 score from mostly open data. Then add your site to Satelo and get partner articles from sites of your level.
Enter a domain like example.com
Add my site