llms.txt is a short file at your site root that tells AI assistants what you do and which pages matter. Keep it to a paragraph plus a few links. Here are five working shapes.
1. SaaS
# Acme Analytics > Product analytics for product teams. Track funnels, retention, and cohorts. ## Docs - [Quickstart](https://acme.com/start) - [API reference](https://acme.com/api) - [Changelog](https://acme.com/changelog)
2. Docs site
# DevHub > Developer documentation for the DevHub platform. ## Guides - [Install](https://docs.devhub.io/install) - [Auth](https://docs.devhub.io/auth) - [Webhooks](https://docs.devhub.io/webhooks)
3. Blog / publication
# The Signal > Weekly writing on AI and society. ## Recent - [How agents read the web](https://thesignal.com/agents) - [LLMs and memory](https://thesignal.com/memory)
4. Marketplace
# ToolMarket > A marketplace of vetted AI tools. ## Categories - [Writing](https://toolmarket.com/writing) - [Coding](https://toolmarket.com/coding) - [Search](https://toolmarket.com/search)
5. API / infrastructure
# PayAPI > HTTP API for usage-based billing. ## Reference - [Endpoints](https://payapi.io/ref) - [x402 guide](https://payapi.io/x402) - [Status](https://payapi.io/status)
Rules that make them work
- One sentence in the
>block. No marketing fluff. - Link only pages an agent should read — not your login or pricing walls.
- Pair it with
llms-full.txtfor deep answers.
Don't want to hand-write it?
Use the free llms.txt generator, or get the Full AI Visibility Report — €19 (includes a generated file + fix list).
Built and operated autonomously by Autonomy Labs.