llms.txt examples.
Copyable llms.txt examples for SaaS, documentation, ecommerce, local businesses, and blogs. The Markdown structure stays the same. The useful part is which pages you include and how you describe them.
Industry templates
The same format, different priorities.
These files are original examples, not copies of live sites. Prefer .md URLs when you publish Markdown twins of HTML pages, as the official proposal recommends.
Lead with product, pricing, and docs
Help a reader understand the product, who it is for, and the first documentation page.
# Relay
> Customer support software for growing teams.
Relay is a shared inbox with automations. Start with the product overview,
then the quickstart. Skip marketing landing pages unless a feature is only explained there.
## Start here
- [Product overview](https://relay.example/product.md): Shared inboxes, routing, and automations.
- [Pricing](https://relay.example/pricing.md): Plans, seats, and included features.
## Documentation
- [Quickstart](https://relay.example/docs/quickstart.md): Connect a mailbox and invite teammates.
- [API](https://relay.example/docs/api.md): Authentication and core endpoints.
## Optional
- [Changelog](https://relay.example/changelog.md): Recent product changes.Make the learning path obvious
Group by the questions new users ask: start here, concepts, guides, and reference.
# Atlas API
> API documentation for building search into web applications.
Prefer the markdown copies of these pages. The HTML docs include navigation chrome
that is not useful in a small context window.
## Start here
- [Introduction](https://docs.atlas.example/index.md): Main concepts and when to use Atlas.
- [Authentication](https://docs.atlas.example/auth.md): Create keys and authenticate requests.
## Guides
- [First search query](https://docs.atlas.example/guides/first-query.md): Index a document and run a query.
## Reference
- [Endpoints](https://docs.atlas.example/reference.md): Parameters and responses.
## Optional
- [SDKs](https://docs.atlas.example/sdks.md): Official client libraries.Explain the catalog without listing every SKU
Point to collections, shipping, returns, and support. Leave product variants out of the file.
# Field & Grain
> Outdoor apparel and gear for weekend hiking.
This file orients shopping assistants and support agents. It does not list inventory.
Use collection pages and policy pages, then let those pages carry product detail.
## Shop
- [Jackets](https://fieldandgrain.example/collections/jackets.md): Waterproof and insulated layers.
- [Footwear](https://fieldandgrain.example/collections/footwear.md): Trail shoes and boots.
## Orders
- [Shipping](https://fieldandgrain.example/shipping.md): Regions, times, and duties.
- [Returns](https://fieldandgrain.example/returns.md): Window, condition, and refunds.
## Optional
- [Size guide](https://fieldandgrain.example/size-guide.md): Measurements by garment type.Services, proof, and how to get in touch
A service business needs trust pages and a clear next step more than a product matrix.
# Fieldwork Studio
> Brand strategy and web design for independent hospitality businesses.
Fieldwork works with restaurants, inns, and small hotels. The work page shows outcomes;
contact is the next step for a new project.
## Services
- [Brand strategy](https://fieldwork.example/services/strategy.md): Positioning, story, and direction.
- [Web design](https://fieldwork.example/services/web.md): A conversion-focused website.
## About
- [Work](https://fieldwork.example/work.md): Selected hospitality projects.
- [Contact](https://fieldwork.example/contact.md): Start a conversation about a new project.Point to the best entries, not the archive
Curate cornerstone articles. Tag pages and paginated archives waste context.
# North Wind Notes
> Independent writing on local food systems and small farms.
Use the essays below as the canonical introductions. Older posts are listed on the archive
page and do not belong in this file unless they are still the best explanation of a topic.
## Start here
- [About](https://northwind.example/about.md): Who writes this site and why.
- [What we cover](https://northwind.example/topics.md): Recurring subjects and who they are for.
## Essays
- [Seasonal buying](https://northwind.example/essays/seasonal-buying.md): How to read a market stall.
- [Farm visits](https://northwind.example/essays/farm-visits.md): What to ask before you visit.
## Optional
- [Archive](https://northwind.example/archive.md): Chronological list of all essays.Blank starter
A clean place to begin.
Replace the placeholders. Keep descriptions useful to someone who has never seen the website.
# Your website or organization
> One or two sentences describing what this website does and who it helps.
Add useful context here if a reader needs it to interpret the links below.
Do not use headings in this preamble.
## Start here
- [Page title](https://example.com/page.md): Explain what someone will learn or do there.
## Product, services, or documentation
- [Page title](https://example.com/another-page.md): Add a concise, factual description.
## Optional
- [Secondary page](https://example.com/secondary.md): Skip this section when context is tight.Good vs bad
The format is easy to fake and still fail.
Useful
# Example Company
> Payroll software for firms with 20 to 200 employees.
Start with the product overview. API details live in the docs links.
## Start here
- [Product](https://example.com/product.md): What the product does and who it is for.
- [Pricing](https://example.com/pricing.md): Plans and included features.Weak
# Welcome
## Links
- Home
- https://example.com/page?ref=utm_source=llms
- [All posts](/blog?page=12)
- [Login](https://example.com/account)- No summary, so the reader does not know what the site is.
- Bare URLs and relative links without titles.
- Login and paginated archives do not belong in the curated file.
Live files
Read real examples, then write your own.
The official proposal and example live at llmstxt.org. FastHTML documents a subpath file at /docs/llms.txt. OpenAI, Anthropic, and Gemini publish files for developer docs. Use them as structure, not as copy-paste content.
Common questions
Questions about llms.txt examples.
What should an llms.txt example include?
A site name as an H1, a short summary, optional extra context without headings, then H2 sections of Markdown links with brief notes. That is the official format. The value is which pages you choose.
Can I copy a real company's llms.txt?
Use public files as structure references, not as your content. Anthropic, OpenAI, Gemini, and many docs platforms publish live files. Link to them; do not republish their text as yours.
Should ecommerce examples list every product?
No. Point to collections, policies, and support. Individual SKUs belong on product pages, not in a file meant to fit in a small context window.
Is llms-full.txt required in these templates?
No. llms-full.txt is an unofficial companion some platforms emit. These examples follow the official llms.txt format only.
Where can I see live files on the web?
The proposal site is https://llmstxt.org/. Documentation platforms such as Mintlify generate files for hosted docs. FastHTML publishes a well-known example at /docs/llms.txt.
Keep exploring
More useful llms.txt resources.
Move from the format to implementation, examples, and a live check without losing the thread.