How it differs from llms.txt
| llms.txt | llms-full.txt | |
|---|---|---|
| Contents | Site summary and a list of links with descriptions | The full text of the listed pages, in Markdown |
| Size | Usually a few kilobytes | Can be hundreds of kilobytes or more |
| Use | Lets a reader pick what to fetch | Lets a reader load everything at once |
Neither file is an official web standard, and AI providers have not committed to reading either. llms-full.txt spread mainly through documentation platforms, where developers paste a docs site into a coding assistant.
When it helps
- Documentation and APIs: developers and coding agents can load the full docs in one go.
- Small, stable sites: a full copy is easy to keep accurate.
- Not for large stores or news sites: a file of every product or article goes stale quickly and becomes too large to be useful.
How to build one
- Start from the page list in your llms.txt.
- Convert each page’s main content to Markdown, without navigation, footers or cookie banners.
- Join them under H2 headings with the source URL for each section.
- Generate it at build time so it stays in step with the pages, and serve it at
/llms-full.txtas plain text.
Start with llms.txt; the generator builds it in a minute. Add llms-full.txt only if people actually load your content into AI tools.
Shipwork checks whether /llms.txt exists and is served as text, alongside AI crawler access in robots.txt. Free, no account, no signup. Paste your store address.
Generate an llms.txtQuestions
Do I need llms-full.txt?
Where does llms-full.txt go?
Is llms-full.txt part of the llms.txt proposal?
Keep reading