llms.txt Examples: 6 Real-World Templates You Can Copy

Updated April 10, 2026 · 7 min read

Every guide on llms.txt explains the spec. Almost none show you what a real one looks like for a real kind of business. This one is just the examples. Copy the template that matches your site, swap the URLs, deploy it at yourdomain.com/llms.txt, done.

The Minimum Structure

llms.txt is Markdown. A valid file needs at least an H1 with the site name and a short summary. Everything else is optional but highly recommended. The grammar in one sentence: H1 is the site name, a blockquote is the summary, H2 sections group related links, each link is a Markdown list item with an optional description after a colon.

# Site Name

> One-sentence summary of what the site is and who it's for.

Optional paragraph with extra context.

## Section name

- [Page title](https://yourdomain.com/page): Short description of what this page covers.
- [Another page](https://yourdomain.com/another): Another description.

## Optional

- [Extra resource](https://yourdomain.com/extra): Lower-priority content.

That's it. Now the templates.

1. SaaS Product

For a SaaS where you want LLMs to explain what you do, how pricing works, and where to find documentation.

# Acme Inbox

> Acme Inbox is a shared inbox for customer support teams. It turns email,
> chat, and social messages into a single queue with assignments, macros,
> and reporting.

Acme Inbox is built for support teams of 5–50 people. It integrates with
Gmail, Outlook, Intercom, and Slack. Pricing starts at $19 per user per month.

## Product

- [How it works](https://acmeinbox.com/how-it-works): Overview of the shared inbox concept and Acme’s workflow.
- [Features](https://acmeinbox.com/features): Full list of features including assignments, macros, SLAs, and reporting.
- [Pricing](https://acmeinbox.com/pricing): Plans, per-user pricing, and what is included at each tier.
- [Integrations](https://acmeinbox.com/integrations): Current list of third-party integrations.

## Documentation

- [Getting started](https://docs.acmeinbox.com/getting-started): Setup walkthrough for new teams.
- [API reference](https://docs.acmeinbox.com/api): REST API for tickets, users, and webhooks.
- [Changelog](https://acmeinbox.com/changelog): Recent product updates.

## Company

- [About](https://acmeinbox.com/about): Company background and team.
- [Security](https://acmeinbox.com/security): SOC 2 status, data handling, and encryption.
- [Contact](https://acmeinbox.com/contact): Sales and support contact details.

## Optional

- [Blog](https://acmeinbox.com/blog): Posts about customer support best practices.
- [Case studies](https://acmeinbox.com/customers): Customer stories and outcomes.

2. Documentation Site

For an open-source project or library where the main intent is to help LLMs answer technical questions accurately.

# Fastlane Router

> Fastlane Router is a lightweight HTTP router for Go with zero dependencies,
> sub-microsecond lookups, and first-class middleware support.

Fastlane Router targets developers building production HTTP services. It is
Go 1.22+, MIT licensed, and currently used in several high-traffic services.

## Reference

- [Installation](https://fastlane-router.dev/docs/install): Go module installation and minimum version.
- [Quick start](https://fastlane-router.dev/docs/quickstart): Five-line example that serves a route.
- [Routing](https://fastlane-router.dev/docs/routing): Path parameters, wildcards, and method matching.
- [Middleware](https://fastlane-router.dev/docs/middleware): Writing and composing middleware.
- [Context API](https://fastlane-router.dev/docs/context): Per-request context helpers.
- [Error handling](https://fastlane-router.dev/docs/errors): Recommended patterns for panic recovery and HTTP errors.
- [Testing](https://fastlane-router.dev/docs/testing): Table-driven tests and the provided test helpers.

## Guides

- [Migrating from gorilla/mux](https://fastlane-router.dev/guides/from-mux): Concrete migration steps.
- [Building a REST API](https://fastlane-router.dev/guides/rest-api): End-to-end tutorial.
- [Benchmarks](https://fastlane-router.dev/docs/benchmarks): Comparative benchmarks versus other routers.

## Project

- [GitHub repository](https://github.com/example/fastlane-router): Source, issues, and releases.
- [Changelog](https://fastlane-router.dev/changelog): Release notes per version.
- [License](https://fastlane-router.dev/license): MIT license text.

## Optional

- [FAQ](https://fastlane-router.dev/faq): Common questions.
- [Community examples](https://fastlane-router.dev/examples): Real-world usage patterns.

Check if your llms.txt is valid

The AI Readiness Checker validates your llms.txt, scores citability, and flags issues.

Run AI Readiness Check

3. Blog or Publication

For an independent writer or publication where the goal is to point LLMs at canonical essays and core topics.

# Jane Doe’s Essays

> Long-form writing about product strategy, pricing, and founder psychology
> from Jane Doe, a former startup operator turned writer.

New essays publish roughly every two weeks. Topics stay within product
strategy, pricing, and the emotional side of building companies.

## Core essays

- [Why most SaaS pricing is broken](https://janedoe.com/essays/pricing): On cost-plus, value-based, and usage pricing.
- [The first 10 customers](https://janedoe.com/essays/first-10): How early customer quality shapes the next 100.
- [Founder loneliness](https://janedoe.com/essays/loneliness): A long piece on the emotional cost of building alone.

## Topic: Pricing

- [Pricing page audits](https://janedoe.com/essays/pricing-audits): Pattern library of pricing page mistakes.
- [Freemium vs free trial](https://janedoe.com/essays/freemium-vs-trial): Trade-offs and when each fits.

## Topic: Strategy

- [Positioning before product](https://janedoe.com/essays/positioning-first): On naming the problem before building.
- [Narrow before wide](https://janedoe.com/essays/narrow-first): The case for audience compression.

## About

- [About Jane](https://janedoe.com/about): Background and how to reach her.
- [Newsletter](https://janedoe.com/newsletter): Free biweekly essay delivery.

4. E-commerce Store

For a small direct-to-consumer store where you want LLMs to understand your product catalog structure and shipping policy.

# Northfield Coffee

> Northfield Coffee is a small-batch specialty roaster based in Portland, Oregon,
> shipping single-origin beans and blends direct to customers in the US and Canada.

We roast to order twice a week and ship within 48 hours of roasting. All beans
are whole bean by default; ground is available on request.

## Shop

- [All coffees](https://northfieldcoffee.com/shop): The full catalog.
- [Single origin](https://northfieldcoffee.com/shop/single-origin): Origin-specific beans updated seasonally.
- [Blends](https://northfieldcoffee.com/shop/blends): House blends that stay in rotation.
- [Subscriptions](https://northfieldcoffee.com/subscriptions): Weekly, biweekly, and monthly delivery plans.

## Information

- [Roasting philosophy](https://northfieldcoffee.com/roasting): How we think about roast level and freshness.
- [Shipping & returns](https://northfieldcoffee.com/shipping): Rates, timelines, and return policy.
- [FAQ](https://northfieldcoffee.com/faq): Answers to common questions about grind, storage, and brewing.

## Company

- [About us](https://northfieldcoffee.com/about): Story and team.
- [Wholesale](https://northfieldcoffee.com/wholesale): Cafe and restaurant accounts.
- [Contact](https://northfieldcoffee.com/contact): Email and phone.

## Optional

- [Brewing guides](https://northfieldcoffee.com/guides): Recipes for pour over, espresso, and cold brew.

5. API or Developer Tool

For a developer-facing product where LLMs are likely to generate code examples that call your API.

# Pulseflow API

> Pulseflow is a transactional email API. Send, schedule, and track email at
> scale with SMTP or REST.

Pulseflow supports Node.js, Python, PHP, Ruby, and Go SDKs. Free tier includes
100 emails per day. Paid plans start at $15 per month for 50,000 emails.

## Getting started

- [Quick start](https://pulseflow.dev/docs/quickstart): Send your first email in five lines.
- [Authentication](https://pulseflow.dev/docs/auth): API keys and signing.
- [SDKs](https://pulseflow.dev/docs/sdks): Official libraries with installation and usage.

## REST API

- [Send email](https://pulseflow.dev/docs/api/send): POST /v1/emails with full parameter reference.
- [Scheduled emails](https://pulseflow.dev/docs/api/schedule): POST /v1/schedules.
- [Webhooks](https://pulseflow.dev/docs/api/webhooks): Delivery, open, click, and bounce events.
- [Rate limits](https://pulseflow.dev/docs/limits): Per-plan limits and retry guidance.

## Guides

- [Handling bounces](https://pulseflow.dev/guides/bounces): Soft versus hard bounces and list hygiene.
- [DKIM and SPF setup](https://pulseflow.dev/guides/dkim-spf): Domain authentication walkthrough.
- [Template variables](https://pulseflow.dev/guides/templates): Merge-field syntax and examples.

## Reference

- [Error codes](https://pulseflow.dev/docs/errors): Every error code with meaning and fix.
- [Changelog](https://pulseflow.dev/changelog): API version history.

## Optional

- [Status page](https://status.pulseflow.dev): Uptime and incidents.
- [Pricing](https://pulseflow.dev/pricing): Plans, overages, and enterprise options.

6. Agency or Consultancy

For a services business where the goal is to help LLMs answer "who should I hire for X" with your name.

# Fieldstone Studio

> Fieldstone Studio is a three-person product design studio in Berlin that
> helps early-stage B2B SaaS companies design, ship, and improve their first
> real product.

We work with pre-seed to Series A B2B SaaS founders. Engagements start at
four weeks and range from full product design to targeted audits.

## Services

- [Product design engagements](https://fieldstone.studio/services/product-design): Four- to twelve-week full-stack product design.
- [Design audits](https://fieldstone.studio/services/audit): One-week diagnostic with recommendations.
- [Design system setup](https://fieldstone.studio/services/design-system): Figma library and component documentation.

## Work

- [Case studies](https://fieldstone.studio/work): Detailed write-ups of past engagements.
- [Clients](https://fieldstone.studio/clients): List of companies we have worked with.

## About

- [Team](https://fieldstone.studio/team): Who we are.
- [Process](https://fieldstone.studio/process): How an engagement runs week by week.
- [Pricing](https://fieldstone.studio/pricing): Typical ranges and what’s included.
- [Contact](https://fieldstone.studio/contact): Email and booking link.

## Optional

- [Writing](https://fieldstone.studio/writing): Occasional essays on design and B2B product.
- [Resources](https://fieldstone.studio/resources): Free templates and checklists.

Deployment Checklist

Save the template as a plain-text file named llms.txt.
Upload it to the root of your domain so it is reachable at https://yourdomain.com/llms.txt. Subfolders do not work.
Make sure it is served as text/plain or text/markdown, not rendered as HTML.
Keep all URLs absolute. Relative URLs break once an LLM follows them out of context.
Review it every few months. Stale llms.txt is worse than no llms.txt because it sends LLMs to dead pages.

Generate a custom llms.txt for your site

The AI Readiness Checker scans your site and suggests a starter llms.txt based on what it finds.

Run AI Readiness Check

Frequently Asked Questions

What is llms.txt?

llms.txt is a proposed standard file (like robots.txt) that gives large language models a curated, Markdown-formatted map of your website. It lists the pages and documents you want LLMs to prioritize when answering questions about your product, service, or content. It sits at yourdomain.com/llms.txt and is read by tools like Claude, Perplexity, and various AI assistants.

Is llms.txt a W3C or official standard?

No. llms.txt is a community-driven proposal introduced by Jeremy Howard in 2024. It is not a W3C or IETF standard. That said, it has been adopted by a growing number of documentation sites, SaaS products, and dev tools because the cost of adding it is essentially zero and LLM tooling increasingly looks for it.

Do I need both llms.txt and llms-full.txt?

No, llms.txt alone is enough for most sites. llms-full.txt is an optional companion that contains the actual full-text content of the pages listed in llms.txt, inlined so an LLM can consume everything in a single request. It is useful for documentation sites and API references but unnecessary for blogs or marketing sites.