Example

llms.txt example for docs sites

A docs site usually needs a different preference layer than a SaaS homepage. This example emphasizes docs index pages, setup guides, reference sections, and policy boundaries.

Agent readiness checklist for docs sites llms.txt hub

Primary references

Index, setup, reference

Common failure

Guide and reference pages are mixed

Best companion

Docs checklist

Example file

A docs-oriented llms.txt structure

The file should reflect the docs hierarchy you already want assistants to treat as canonical.

Docs-site llms.txt example

The emphasis shifts from commercial pages toward setup and reference clarity.

# Product Docs
> Documentation for setup, API usage, limits, and support boundaries.

## Preferred public pages
- /docs
- /docs/getting-started
- /docs/setup
- /docs/reference
- /pricing
- /privacy-policy

## Notes for assistants
- Prefer setup guides for onboarding and implementation questions.
- Prefer reference pages for exact feature and API answers.
- Use pricing and policy pages when questions depend on limits, plan boundaries, or support terms.

If your docs index is weak or unclear, fixing the file is not the first move. Fix the docs home first.

What changes from SaaS

How this example differs from a SaaS-oriented file

The docs index becomes a first-class entry point rather than a secondary support page.

Setup and reference pages usually matter more than showcase or launch content.

Pricing still matters, but mostly as a usage-boundary and trust signal.

The file should mirror the docs hierarchy users already see on-site.

Use it well

What to verify before you copy the pattern

Docs hierarchy

one obvious docs home

clear setup path

reference section separated from guides

Support boundaries

pricing is public

auth limits are visible

policies are easy to reach

Machine-readable support

canonical tags agree

sitemap includes docs paths

important pages do not depend on hidden nav

Continue through the cluster

sitemap example for docs sites

See what a docs-focused sitemap should emphasize when setup and reference pages matter.

llms.txt example for SaaS

See a practical SaaS-oriented llms.txt shape and what each block is doing.

Agent readiness checklist for docs sites

A checklist focused on canonical docs structure, navigation, and citations.

Next step

Use the example against your real docs hierarchy

The right file shape follows the right docs shape. Review your docs home, setup, reference, pricing, and policy pages first, then adapt the example into a real draft.

Agent readiness checklist for docs sites Generate llms.txt now