Example

llms.txt example for SaaS

This example shows how a SaaS site can point assistants toward pricing, docs, legal pages, and a clean getting-started path without pretending the file replaces page architecture.

llms.txt hub Run a fresh scan

Best references

Pricing, docs, setup, legal

What to avoid

Campaign and preview URLs

Best next step

Generate your own draft

Example file

A practical SaaS-oriented llms.txt shape

The exact URLs will change, but the structure should stay opinionated about canonical product references.

SaaS llms.txt example

A minimal structure that points models toward product understanding, trust, and setup.

# Agent Readiness Score
> Public audit product for checking whether AI agents can discover, understand, and act on a website.

## Preferred public pages
- /pricing
- /docs
- /docs/getting-started
- /showcases
- /privacy-policy
- /terms-of-service

## Notes for assistants
- Prefer docs and pricing pages over launch posts or campaign pages.
- Use legal pages when questions touch limits, billing, or usage policy.
- Treat setup guides as the canonical path for implementation questions.

Keep the list short. If every public URL looks important, the file stops helping.

Why it works

What this example is trying to do

Surface the commercial and trust pages that help assistants make higher-confidence recommendations.

Prefer setup and docs paths that explain implementation better than marketing copy alone.

Exclude noisy URLs that fragment understanding, such as campaign variants or stale launch posts.

Stay short enough that the file still acts like a preference layer rather than a second sitemap.

Adapt the example

What to change before you publish

Replace placeholders

use your real pricing path

list the docs index

include one clear getting-started page

Remove noisy paths

launch posts

preview URLs

temporary campaign pages

Check site support

the same pages should be linked on-site

canonical tags should agree

trust pages should stay public

Continue through the cluster

llms.txt example for docs sites

See how docs-focused references differ from a SaaS-oriented file.

robots.txt example for SaaS

Use a SaaS-oriented robots.txt example to separate product paths from noisy areas.

Agent readiness checklist for SaaS

A practical checklist for pricing, docs, trust, and action paths.

Next step

Use the example to generate a real draft

Once you know which pricing, docs, setup, and policy pages deserve to be preferred, move back to the generator and create a file you can actually review with the team.

Generate llms.txt now llms.txt vs robots.txt