Configure your llms.txt
Output: llms.txt
https://yourdomain.com/llms.txt
Real-World Examples
See how different types of projects structure their llms.txt files.
Click Load into Generator to use any example as a starting point.
Open-Source Library
Clean, minimal structure for a developer tool with documentation and guides.
# My Awesome Project
> A fast, open-source tool for doing X, built for developers.
My Awesome Project helps developers accomplish X quickly
and efficiently. It supports Y and Z out of the box.
## Documentation
- [Getting Started](https://example.com/docs/start): Installation and first steps
- [API Reference](https://example.com/docs/api): Full API documentation
- [Configuration](https://example.com/docs/config): All configuration options explained
## Guides
- [Deploy to Production](https://example.com/guides/deploy): Step-by-step deployment
- [Troubleshooting](https://example.com/guides/trouble): Common issues and solutions
## Optional
- [llms-full.txt](https://example.com/llms-full.txt): Entire documentation in one fileSaaS Product
Structured for a SaaS with product info, help centre, and developer docs.
# SaaS Product
> The all-in-one platform for team collaboration and project management.
## Product
- [Features Overview](https://example.com/features): Complete list of platform features
- [Pricing](https://example.com/pricing): Plans and pricing information
- [Changelog](https://example.com/changelog): Recent updates and new features
## Help Center
- [Getting Started](https://help.example.com/start): Set up your account and workspace
- [Integrations](https://help.example.com/integrations): Connect third-party tools
- [Billing](https://help.example.com/billing): Manage subscription and invoices
## Developers
- [API Documentation](https://developers.example.com/): REST API and authentication
- [Webhooks](https://developers.example.com/webhooks): Event-driven integrationsBlog / Personal Site
Minimal structure for a personal blog — curated best articles, no fluff.
# Jane Doe's Blog
> Writing about web development, design, and the open web.
I'm a freelance web developer based in Berlin. I write about
modern CSS, web performance, and developer tooling.
## Best Articles
- [CSS Grid Deep Dive](https://janedoe.com/css-grid): Mastering CSS Grid layouts
- [Web Performance 101](https://janedoe.com/perf): Core Web Vitals explained
- [Svelte vs React 2025](https://janedoe.com/svelte-react): Comparing frameworks
## About
- [About Me](https://janedoe.com/about): Background, skills, and contact
- [Portfolio](https://janedoe.com/portfolio): Selected client work and case studiesDocumentation Site
Comprehensive structure for a large framework docs site with multiple sections.
# Framework Docs
> Official documentation for Framework 3.x — fast, batteries-included.
## Getting Started
- [Introduction](https://docs.example.com/intro): What Framework is and why use it
- [Installation](https://docs.example.com/install): Prerequisites and setup steps
- [Quick Start](https://docs.example.com/quickstart): Build your first app in 5 min
## Core Concepts
- [Routing](https://docs.example.com/routing): File-based and dynamic routing
- [Data Fetching](https://docs.example.com/data): SSR, SSG, and ISR strategies
- [Components](https://docs.example.com/components): Building reusable UI components
## Optional
- [llms-full.txt](https://docs.example.com/llms-full.txt): Entire docs in one fileTips & Best Practices
Guidelines for writing llms.txt files that maximise how well AI assistants understand your content.
Do This
- Write a precise tagline. The blockquote is often the first thing an LLM reads. One clear sentence that explains exactly what your project does.
- Curate, don't dump. Link only your 5–20 most important pages. Quality beats quantity — LLMs benefit from focused, relevant content.
-
Add link descriptions.
The colon-delimited text after each link
(
- [Title](URL): Description) gives LLMs vital context about what a page contains before fetching it. -
Group pages logically.
Use sections (
## Section) to group related pages: Docs, API, Guides, About, etc. -
Keep it updated.
Outdated links or descriptions undermine trust.
Review your
llms.txtwhenever you restructure your site. -
Provide
llms-full.txt. Combine all key pages into one large file — some LLM clients can fetch and process it in one shot.
Avoid This
-
Don't copy your sitemap.
A sitemap lists every URL;
llms.txtis a curated index. Skip login pages, search results, user profiles, and admin areas. - Don't leave descriptions empty. Bare URLs with no context force LLMs to guess. Add at least a short phrase per link.
- Don't use vague titles. "Page 1", "Click here", or "Docs" without context are unhelpful. Be specific: "API Authentication Guide" beats "API".
- Don't include private content. Avoid linking to pages behind authentication, internal tools, or anything not meant for public consumption.
- Don't over-section. Two or three sections are usually enough. Avoid creating one section per page — group them.
-
Don't keyword-stuff.
llms.txtis about context for AI, not SEO rankings. Stuffing the tagline with keywords is counterproductive.
How LLMs Use llms.txt
Discovery
AI assistants and crawlers check for /llms.txt at your domain root
when a user asks about your product. It's an entry point — like a table of contents.
Context Window
LLMs have limited context windows. A concise llms.txt
helps them decide which pages to actually fetch, rather than
attempting to download your entire site.
Trust Signal
A well-maintained llms.txt signals that you care about how AI
represents your project — and lets you highlight canonical, accurate information.
File Placement
- https://example.com/llms.txt Required
- https://example.com/llms-full.txt Optional
- Sub-sites also work:
https://docs.example.com/llms.txt - Must be publicly accessible without authentication
- Plain UTF-8 text, no BOM, Unix line endings
Size Guidelines
- llms.txt — keep under 50 KB; ideally under 10 KB
- llms-full.txt — can be much larger (100 KB – 5 MB)
- Aim for 5–20 curated links total
- Tagline + intro: one or two short paragraphs max
- Sections: 2–5 is ideal; 10+ is usually too many
Format Reference
The complete llms.txt format specification.
The file is Markdown-based and placed at https://yourdomain.com/llms.txt.
Complete Format
# Project or Site Name > One-sentence summary (the "tagline" — this is the most important field). Optional paragraph with more detail about the project, its purpose, and who it is for. Keep it brief — 1 to 3 sentences. ## Section Name - [Page Title](https://example.com/page): Brief description of what this page covers ## Another Section - [Another Page](https://example.com/other): Short description here - [Third Page](https://example.com/third): What this page is about ## Optional - [llms-full.txt](https://example.com/llms-full.txt): Full site content merged into one file
Field Reference
| Element | Syntax | Required | Description |
|---|---|---|---|
| Title | # Project Name |
Required | H1 heading — name of your project or website |
| Tagline | > Short summary |
Required | Blockquote immediately after the title. One concise sentence. The most important field. |
| Intro | Plain paragraph text | Optional | Additional context about the project. Keep it brief — 1–3 sentences max. |
| Section | ## Section Name |
Optional | H2 headings to group related links. Use 2–5 sections total. |
| Link | - [Title](URL) |
Optional | A list item with a Markdown hyperlink. Always inside a section. |
| Link description | - [Title](URL): Desc |
Optional | Colon-delimited description after the link. Strongly recommended for every link. |
| llms-full.txt | - [llms-full.txt](URL) |
Optional | Link to the combined full-content version. By convention placed in an "Optional" section. |
llms-full.txt — The Combined Content File
llms-full.txt contains the combined text content of all pages
linked in llms.txt, concatenated into one large file. It is useful for LLM clients that:
- Can process large context windows in a single request
- Want to avoid making many individual HTTP requests per page
- Need a cached or offline snapshot of your full documentation
Tip: For large documentation sites, auto-generate llms-full.txt
with a build script that fetches and concatenates each linked page during your CI/CD pipeline.
Further Reading
- llmstxt.org — Official specification and proposal by Jeremy Howard (fast.ai)
- AnswerDotAI/llms-txt — Reference implementation and tooling on GitHub
- llmstxt.site — Directory of websites that already have llms.txt
- directory.llmstxt.cloud — Directory of websites that already have llms.txt
- claude.com/llms.txt — Anthropic's own llms.txt as a real-world example