llms.txt examples

The llms.txt format is simple enough to learn from three patterns. Every example below follows the Answer.AI convention: H1, blockquote summary, H2 sections of described links, Related section. You can adapt any of them, or generate your own from a sitemap with the generator.

Example 1: a documentation site

# Acme SDK Documentation

> Acme SDK is a JavaScript library for building payment flows. It provides a client library, server APIs, and a checkout UI.

## Core documentation

- [Getting started](https://acme.dev/docs/getting-started): install and run your first payment
- [API reference](https://acme.dev/docs/api): every endpoint, parameter and error code
- [Webhooks](https://acme.dev/docs/webhooks): subscribe to payment events

## Guides

- [Refunds](https://acme.dev/guides/refunds): how to refund a charge
- [Subscriptions](https://acme.dev/guides/subscriptions): recurring billing in 4 steps

## Related

- [Sitemap](https://acme.dev/sitemap.xml): machine-readable URL index
- [llms-full.txt](https://acme.dev/llms-full.txt): self-contained full content

Note how each description answers "what will I find here?" — AI agents use these one-liners to decide which page to fetch. This pattern fits any project with real documentation.

Example 2: a SaaS marketing site

# Acme Analytics

> Acme Analytics is a privacy-first web analytics tool for small teams. It offers event tracking, funnels and dashboard sharing without cookie banners.

## Product

- [Features](https://acme.com/features): events, funnels, retention
- [Pricing](https://acme.com/pricing): free plan and Pro at $19/month
- [Security](https://acme.com/security): data residency and encryption

## Resources

- [Blog](https://acme.com/blog): product updates and analytics guides
- [Help center](https://acme.com/help): setup and troubleshooting

## Related

- [Sitemap](https://acme.com/sitemap.xml): machine-readable URL index
- [llms-full.txt](https://acme.com/llms-full.txt): self-contained full content

Example 3: a content blog

# The Acme Journal

> The Acme Journal publishes weekly essays on software engineering and AI tooling, written by practicing engineers.

## Latest essays

- [Why we wrote our own queue](https://acme.blog/why-own-queue): a deep dive into delivery guarantees
- [A field guide to llms.txt](https://acme.blog/field-guide-llms-txt): adopt the AI navigator file

## About

- [About the journal](https://acme.blog/about): contributors and editorial policy

## Related

- [Sitemap](https://acme.blog/sitemap.xml): machine-readable URL index
- [llms-full.txt](https://acme.blog/llms-full.txt): self-contained full content

Example 4: this site's own llms.txt

Dogfooding: LLMsTxt Generator publishes its own AI-facing files — /llms.txt and /llms-full.txt — both generated with the tool and scoring 5/5 on the GEO checks. That is the validation loop we recommend: generate, score, fix, publish, repeat after content changes.

What makes a great llms.txt example?

Three properties recur in the examples above: every link carries a description, sections mirror the site's real structure, and the Related section points to the sitemap and llms-full.txt. For AI citability, add the five GEO practices — entity-rich openings, 50–150-word chunks, question headings, entity density and definitional phrasing — explained in llms.txt SEO.