← Back to blog/Engineering

What Is llms.txt? A Practical Guide for SaaS Docs Teams

llms.txt is a machine-readable index for documentation. Here's what it does, why it matters, and where it stops being enough.

F
Faizan Khan
2026-05-29 • 6 min read

If you run a docs site for a SaaS product, you already publish structure for humans and search engines. You have navigation for people. You probably have a sitemap.xml for Google. llms.txt is the missing layer for AI agents: a small file that tells them where your useful documentation lives and where to start.

It is not complicated. It is not a new protocol stack. It is just a practical way to make your docs easier for agents to discover.

This post is the definitional guide: what llms.txt is, why SaaS docs teams should care, and where the file stops being enough.

The public spec at llmstxt.org is short and worth reading. What follows is the practical version for teams maintaining real product docs.

What llms.txt Is

llms.txt is a plain-text or markdown file, usually served at the root of a docs site, that gives AI agents a curated index of your documentation.

Think of it as a hand-written map.

Not a crawler dump. Not every URL on your site. Just the pages an agent should actually read first.

A minimal version looks like this:

Markdown
1# Acme Docs
2

3Acme's developer documentation for authentication, API requests, webhooks,
4rate limits, and SDK setup.
5

6## Start Here
7

8- [Quickstart](https://docs.acme.com/quickstart): Set up your first API request
9- [Authentication](https://docs.acme.com/authentication): API keys, OAuth, and scopes
10- [Errors](https://docs.acme.com/errors): Error codes and retry guidance
11

12## Common Tasks
13

14- [Webhooks](https://docs.acme.com/webhooks): Receive event notifications
15- [Rate Limits](https://docs.acme.com/rate-limits): Understand limits and backoff
16- [Node SDK](https://docs.acme.com/sdks/node): Integrate with Node.js

That is the core idea. Give the model a small, opinionated set of entry points instead of making it guess.

Why SaaS Docs Teams Should Care

More people are using AI tools as the first interface to your docs.

They paste a URL into Claude Code. They ask Cursor how to authenticate with your API. They ask ChatGPT how to set up webhooks for your product. In all of those cases, the model has to figure out where the useful documentation is and which pages matter.

If your docs are well structured, a model can usually muddle through. But llms.txt gives it a shortcut:

  • what your product docs cover
  • which pages matter most
  • where to start for common tasks
  • which references are canonical

That is especially useful for SaaS docs because most products have the same failure mode: too many pages, too much duplication, and no obvious "start here" path for a machine.

Humans can recover from that by browsing. Agents are much better if you point them directly.

What Makes llms.txt Different

The useful distinction is this:

  • navigation is written for humans moving through a site
  • sitemap.xml is written for crawlers discovering URLs
  • llms.txt is written for agents trying to choose what matters first

That is why the file tends to work best when it is short and opinionated.

The moment it starts trying to mirror the whole docs surface, it stops acting like guidance and starts acting like a worse sitemap.

If you want the longer comparison, read llms.txt vs sitemap.xml: What Each File Does for AI Discovery.

What a Good First Version Looks Like

A useful first version usually has:

  • a one-sentence description of the docs set
  • a short "start here" section
  • a small number of links for common tasks
  • enough structure that an agent can tell where to go next

The point is not to be exhaustive.

The point is to remove ambiguity.

If you want concrete patterns, examples, and templates, read llms.txt Examples: Real Patterns for API Docs, Help Centers, and Developer Docs.

If you want the implementation mechanics, read How to Add llms.txt to Your Documentation Site.

If you want the SaaS-specific judgment call about what belongs in the file at all, read llms.txt for SaaS Docs: What to Include and What to Skip.

What llms.txt Does Not Solve

This is the part most teams miss.

llms.txt helps with discovery. It does not automatically make your docs cheap to consume, easy to interpret, or agent-ready in the deeper sense.

It does not fix:

  • bloated HTML pages
  • weak information architecture
  • missing decision tables
  • broken examples
  • unclear product boundaries

And it does not tell an agent how to use your product well. For that, you may also want a skill.md file, better markdown delivery, or a more structured docs experience overall.

That is why we treat llms.txt as the first layer, not the whole solution. If you want the systems view, we already wrote that up in llms.txt Isn't Enough.

The Right Way to Think About It

Do not think of llms.txt as an SEO hack.

Think of it as a documentation affordance for agents.

Humans benefit from sidebars, breadcrumbs, and curated quickstarts. Agents benefit from the same kind of editorial judgment, just expressed in a smaller and more explicit format.

If your docs team already knows which pages matter most, llms.txt is simply the place to write that down in a machine-readable way.

And if you stop there, that is still a meaningful improvement.

If you want the next layer after that, add markdown delivery, cleaner docs structure, and a skill.md that tells agents how to use your product well.

More Articles