llms.txt example template
The short answer
A standard llms.txt begins with an H1 of your brand name, a brief blockquote descriptor, and organized markdown sections listing your primary tools, documentation guides, and API endpoints with bulleted titles and concise one-line descriptions optimized for rapid LLM context windows.
Standard llms.txt Markdown Structure
An llms.txt file provides large language models and developer agents with an unambiguous, structured index of your product documentation, guides, and tools.
| Markdown Element | Syntax Example | Purpose |
|---|---|---|
| H1 Title | # Brand Name | Declares the entity identity |
| Blockquote | > Short summary of core purpose | Provides high-density entity descriptor |
| H2 Section | ## Documentation | Groups related endpoints and guides |
| List Item | - [Title](url): Description | Provides direct link and semantic summary |
Frequently Asked Questions
Where should llms.txt be placed?
At the root of your domain (e.g. https://hubseo.tech/llms.txt).
What is llms-full.txt?
An optional full concatenation of your product documentation for deep context injection.
How do I validate my llms.txt?
Use HubSEO's free llms.txt validator tool at /tools/llms-txt-validator.
Can llms.txt be generated dynamically?
Yes, using a standard Next.js route handler returning text/plain.