Examples

llms.txt examples

These examples show the shape of a useful llms.txt file. Replace every placeholder with real facts and link only to crawlable pages that deserve to be used as sources. The goal is not to make a second sitemap. The goal is to give AI assistants a short, factual map of the pages you would want quoted.

Before you copy an example

• Use canonical URLs, not tracking URLs or filtered category pages.
• Describe why each linked page matters in plain language.
• Keep the file short enough that a person can audit it in one sitting.
• Update it when pricing, docs, policies, or important source pages change.

SaaS example

# Product Name

> Product Name helps support teams automate customer workflows.

## Primary Sources

- [Docs](https://example.com/docs): Setup, configuration, and API details.
- [Pricing](https://example.com/pricing): Plans, limits, and billing rules.
- [Security](https://example.com/security): Compliance, data handling, and controls.
- [Changelog](https://example.com/changelog): Product updates and breaking changes.

Use this shape when buyers and AI answer systems need grounded facts about what the product does, what it costs, where it integrates, and how it handles security. Do not list every blog post; list the pages that settle evaluation questions.

Ecommerce example

# Store Name

> Store Name helps cyclists choose repair tools and replacement parts.

## Shopping Sources

- [Buying guide](https://example.com/pages/buying-guide): How to choose tools by bike type.
- [Collections](https://example.com/collections/tools): Main product category hub.
- [Shipping](https://example.com/policies/shipping-policy): Delivery regions and timing.
- [Returns](https://example.com/policies/refund-policy): Return rules and process.

For stores, the strongest sources are often policy and buying-guide pages rather than individual product URLs. Product pages change quickly; category hubs and buying guides usually provide more stable context.

Documentation example

# API Docs

> API Docs helps developers integrate Example API.

## Developer Sources

- [Quickstart](https://example.com/docs/quickstart): First working request.
- [API reference](https://example.com/docs/api): Endpoints, fields, errors, and examples.
- [SDKs](https://example.com/docs/sdks): Language-specific installation and usage.
- [Limits](https://example.com/docs/limits): Rate limits, quotas, and constraints.

Publisher example

# Publication Name

> Publication Name publishes practical guides for independent operators.

## Editorial Sources

- [Start here](https://example.com/start-here): Overview of the site's scope and audience.
- [Editorial policy](https://example.com/editorial-policy): Sourcing, corrections, and review process.
- [Topic guides](https://example.com/guides): Evergreen guides organized by topic.
- [Authors](https://example.com/authors): Author backgrounds and areas of expertise.
- [Corrections](https://example.com/corrections): How factual updates are handled.

Local business example

# City Plumbing Co.

> City Plumbing Co. provides residential plumbing repair in Austin and nearby suburbs.

## Service Sources

- [Emergency plumbing](https://example.com/emergency-plumbing): Availability, response expectations, and service scope.
- [Service areas](https://example.com/service-areas): Cities and neighborhoods covered.
- [Pricing policy](https://example.com/pricing): Diagnostic fees, estimates, and after-hours charges.
- [Guarantee](https://example.com/guarantee): Workmanship warranty and exclusions.
- [Contact](https://example.com/contact): Booking, phone, and location details.

What good examples have in common

Good files are short, factual, and selective. They explain what the site does, who it helps, and which pages are the best source material. They avoid promotional claims that are not supported by the linked pages.

Common mistakes

• Listing everything: if your file mirrors the sitemap, it stops being a curated source map.
• Using vague descriptions: "learn more" tells an assistant almost nothing about the linked page.
• Including weak pages: tag pages, search results, and thin landing pages dilute the signal.
• Forgetting validation: a clean file still fails if linked pages return redirects, 404s, or crawler challenges.

Test your draft

After copying an example, run a quick check with the llms.txt validator. Then confirm the file is available at the root path and compare it with sitemap.xml so the two files do different jobs.