Who this is for
A SaaS documentation team that wants AI assistants to cite the right docs and avoid stale support answers.
Worked example
SaaS Documentation LLMs.txt Map Example
A documentation-site example for publishing an llms.txt map that helps assistants find official docs without guessing.
Signals to check
- The docs contain canonical setup pages, API references, and changelogs.
- Search assistants may surface outdated blog posts.
- Support teams need a lightweight map of official pages.
Best tool path
Step-by-step workflow
- Group official docs by setup, API reference, troubleshooting, changelog, and security pages.
- Create an llms.txt file with stable URLs and short descriptions.
- Keep robots.txt rules separate from the llms.txt map.
- Review the map whenever docs routes change.
A useful crawler policy includes URL groups, intended bot categories, rule text, test examples, and a change note. The useful result is not just a score or file; it is a small record that explains what was checked, what changed, and what should be reviewed next.
Before you start
After the output
Known limitation
Robots.txt is a public crawl instruction. It is not authentication, paywall enforcement, or a substitute for server-side access control. Keep an editable copy and re-run the workflow when the destination requirement or policy changes.