llms.txt Examples: Real Files for Every Site Type
The fastest way to learn a format is to read a good example — so here are four complete, spec-valid llms.txt example files for the site types that publish them most: SaaS documentation, e-commerce, personal blogs, and corporate websites.
Why Examples Are the Fastest Way to Learn llms.txt
The llms.txt specification is deliberately minimal — one required # H1, an optional
blockquote summary, free-form notes, and ## H2 sections that each contain a list of
links. Reading the spec tells you the rules; reading real llms.txt examples tells
you what the rules look like in practice. The format leaves real decisions to you: which pages
deserve a link, how to group them into sections, how many links is too many, and where the
optional stuff goes.
Every example below follows the llmstxt.org v2 specification exactly: exactly one H1 at the top,
a blockquote summary, short notes without headings, H2 file lists with absolute URLs and a
: description on every link, and a trailing ## Optional section where it
helps. The site names are fictional — swap in your own domain, pages, and descriptions. If you want
the rules themselves, the
complete llms.txt format guide
walks through every element.
The second thing examples teach you is that the format scales without changing shape: the same skeleton that fits a ten-link blog file also carries a multilingual corporate index. Once you can read one of these files end to end, you can write one for any site — which is exactly what the generator behind this page automates.
llms.txt Example 1: SaaS Documentation Site
Documentation is the canonical use case for llms.txt — AI coding agents answer questions from docs
more than from any other page type. This example shows three organizational habits worth copying:
linking straight to .md versions of pages, referencing an
llms-full.txt for agents that want everything, and moving secondary links into
## Optional.
# Pulseboard Analytics
> Pulseboard is a product analytics platform for SaaS teams — event tracking, funnels, retention, and dashboards from a single SDK.
Pulseboard has SDKs for JavaScript, Python, and mobile. All documentation is published as Markdown, so every link below points directly at a .md file.
## Important links
- [Quick start](https://pulseboard.dev/docs/quickstart.md): Install the SDK and send your first event in 10 minutes
- [Event tracking API](https://pulseboard.dev/docs/api/events.md): Track, batch, and alias events, with code examples
- [Dashboards & reports](https://pulseboard.dev/docs/dashboards.md): Build funnels, retention cohorts, and custom reports
- [llms-full.txt](https://pulseboard.dev/llms-full.txt): The complete documentation in a single file
## Guides
- [Tracking plan design](https://pulseboard.dev/docs/guides/tracking-plan.md): Structure your events before you ship
- [Data privacy & consent](https://pulseboard.dev/docs/guides/privacy.md): GDPR, CCPA, and cookieless tracking
- [Migrating from Amplitude](https://pulseboard.dev/docs/guides/migrate.md): Step-by-step migration guide
## Optional
- [Changelog](https://pulseboard.dev/changelog.md): Release notes for all past versions
- [Pricing](https://pulseboard.dev/pricing.md): Plans, limits, and billing FAQ
Notice what makes this file useful to an agent: the blockquote explains what the product is in one
breath, the llms-full.txt link offers a deep-read option without bloating this file,
and ## Optional keeps pricing and changelog out of the default context. The .md
URLs matter too — Markdown renders cleanly inside an LLM's context window, with none of the nav,
cookie banners, or layout noise of the HTML versions.
llms.txt Example 2: E-commerce & Product Site
For stores, the goal is different: agents should be able to answer product questions — what you
sell, what it costs, how shipping works — and recommend pages to shoppers. This
llms.txt example organizes by product line, adds an HTML comment in the notes area
(the only safe place for comments), and keeps time-sensitive pages like sales in
## Optional.
# Terra Outfitters
> Terra Outfitters is an online outdoor gear store — tents, backpacks, sleeping bags, and hiking apparel with free shipping over $75.
<!-- Generated from our product feed on 2026-08-19; product pages are also served as Markdown at .md URLs. -->
## Product lines
- [Tents](https://terra-outfitters.com/products/tents.md): 2–6 person tents, shelters, and footprints
- [Backpacks](https://terra-outfitters.com/products/backpacks.md): Daypacks and multi-day packs from 20L to 75L
- [Sleeping bags](https://terra-outfitters.com/products/sleeping-bags.md): Down and synthetic bags rated to -20°F
- [Hiking apparel](https://terra-outfitters.com/products/apparel.md): Jackets, base layers, and trail pants
## Help & policies
- [Shipping & returns](https://terra-outfitters.com/shipping.md): Delivery times, costs, and 60-day returns
- [Sizing guide](https://terra-outfitters.com/sizing.md): Fit guidance for packs, apparel, and footwear
- [Product care](https://terra-outfitters.com/care.md): Cleaning and repair instructions
## Optional
- [Sale & clearance](https://terra-outfitters.com/sale.md): Current discounts and limited offers
The shape is the same as the SaaS example, but the content priorities flipped: category pages and
policies carry the weight instead of API references. The HTML comment survives parsing because it
sits in the notes area, where the spec allows it. If your store runs seasonal promotions, keep them
out of the main sections — a sale page that goes stale in ## Optional costs far less
trust than a dead link at the top of the file.
llms.txt Example 3: Personal Blog
Blogs have the opposite problem from docs sites: too much content, most of it not worth an agent's
context. A good blog llms.txt example is a curated list — recent or best posts
only — with the archive tucked into ## Optional. Keep the whole file under a couple of
hundred words and agents will actually read it.
# Field Notes by Maya Chen
> Field Notes is a personal blog about distributed systems, Rust, and marathon running, written by Maya Chen, a backend engineer at a fintech startup.
Posts are written in Markdown and archived by category. The list below covers the most useful posts; the full archive is under Optional.
## Recent posts
- [Why we moved from Postgres to TiDB](https://mayachen.dev/posts/tidb-migration.md): A production postmortem with real query numbers
- [Rust async in 15 minutes](https://mayachen.dev/posts/rust-async.md): A practical walkthrough for beginners
- [My 2025 reading list](https://mayachen.dev/posts/reading-2025.md): Books on systems, history, and endurance training
- [Training for a sub-3 marathon](https://mayachen.dev/posts/marathon-training.md): The exact plan I used, week by week
## Optional
- [About](https://mayachen.dev/about.md): Bio, speaking, and contact details
- [All posts](https://mayachen.dev/archive.md): Complete chronological archive
- [Talks](https://mayachen.dev/talks.md): Slides and recordings from conference talks
Ten links, two sections, one blockquote — that's the whole file. If you publish a lot, rotate the
featured posts as new ones land, or point ## Optional at category pages instead of
individual posts. "Most useful" beats "most recent": an evergreen tutorial outranks yesterday's
link roundup, because agents are usually answering a question, not catching up on news.
llms.txt Example 4: Corporate Website
Corporate sites serve a different audience again: investors, journalists, and job seekers asking factual questions. This llms.txt example demonstrates a multilingual layout — a section per language, each with its own absolute URLs — plus company-critical pages up front and legal pages at the end.
# Nordhelm Group
> Nordhelm Group is a Munich-based industrial automation company — robotics, control software, and factory integration services for manufacturers across Europe.
The site is published in English and German. Links are grouped by language, and every page is available as Markdown.
## English
- [About Nordhelm](https://nordhelm-group.com/en/about.md): Company history, leadership, and locations
- [Products & solutions](https://nordhelm-group.com/en/products.md): Robot arms, vision systems, and control software
- [Industries](https://nordhelm-group.com/en/industries.md): Automotive, electronics, and logistics use cases
- [Newsroom](https://nordhelm-group.com/en/news.md): Press releases and company news
## Deutsch
- [Über Nordhelm](https://nordhelm-group.com/de/ueber-uns.md): Unternehmensgeschichte, Führung und Standorte
- [Produkte & Lösungen](https://nordhelm-group.com/de/produkte.md): Roboterarme, Bildverarbeitung und Steuerungssoftware
- [Karriere](https://nordhelm-group.com/de/karriere.md): Offene Stellen und Bewerbungsprozess
## Optional
- [Investor relations](https://nordhelm-group.com/en/investors.md): Annual reports and financial results
- [Imprint & privacy](https://nordhelm-group.com/en/imprint.md): Legal notices (Impressum) and privacy policy
The language-split sections are the takeaway: agents can fetch the German pages when the answer
should be in German and ignore them otherwise. Note the German descriptions still follow the
[text](url): note convention — keep descriptions in the page's own language so the
link list stays meaningful to every reader. The legal section at the end matters for European
sites, where an Impressum is a legal requirement and a common question for agents to answer.
What to Highlight in Your llms.txt, by Site Type
Each site type earns agent traffic for different reasons. Use this comparison to decide what belongs in your file:
| Site type | What agents look for | What to prioritize |
|---|---|---|
| SaaS documentation | Setup steps, API reference, guides | Quick start + API links + an llms-full.txt reference |
| E-commerce / product | What you sell, prices, shipping and returns | Product categories, help & policy pages, FAQ |
| Personal blog | Recent and evergreen posts, author context | A curated list of recent/best posts — keep it short |
| Corporate website | Company facts, products, news, contact info | About, products, newsroom — one section per language if multilingual |
Hybrid sites — a blog with a docs section, a store with a corporate About page — can mix and match: pick the section structure that matches your dominant content type, then add one section for the secondary type. The file stays valid either way, because validity never depends on the topic, only on the order and shape of the elements.
The Universal llms.txt Template: A Copy-Paste Checklist
Strip away the site-specific choices and all four examples share the same skeleton. Work through this checklist in order and you'll have a valid file every time:
| Step | Element | What to include |
|---|---|---|
| 1 | # Site Name (H1) | The only required element — exactly one, at the very top. |
| 2 | Blockquote | One or two lines of key context about the site. |
| 3 | Free-form notes | 0–3 short paragraphs; no headings allowed here. |
| 4 | ## Section (H2) | Two to five file lists, grouped by topic. |
| 5 | Link items | [text](absolute URL): description — never relative, always described. |
| 6 | ## Optional | Secondary links agents can skip when context is short. |
| 7 | llms-full.txt | One link to the expanded file, if you publish one. |
| 8 | Validation | Run the finished file through the free llms.txt checker. |
When you're done, your file should look like a short README: roughly 40 to 150 lines, one H1, one blockquote, a few notes, and every link absolute and described. If a section is thinner than three links, fold it into another section — the checklist is a guide, not a contract.
llms.txt Examples FAQ
Can I copy these llms.txt examples as-is?
The structure is copy-safe — that's the point of a template. Replace the site name, links, and descriptions with your own, keep the section order, and run the result through a validator. The fictional domains in these examples will fail link checks if you leave them in.
How many links should my llms.txt file have?
There is no hard limit, but most sites do best with 10–40 links across two to five sections. The file is meant to fit comfortably in a context window — if it reads like a sitemap, cut it down and move the long tail into ## Optional or llms-full.txt.
Should my llms.txt list every page on my site?
No. An llms.txt file is a curated index, not a sitemap — agents trust it because every link is worth reading. List the pages that deserve attention, group them sensibly, and publish the full expansion separately as llms-full.txt.
Ready to write your own llms.txt?
Generate a spec-perfect file from your URLs in under a minute — free, no sign-up. Then read the full format guide for the details.