llms.txt is a plain-text Markdown file hosted at your website's root (yourdomain.com/llms.txt) that gives AI models structured context about your brand, products, and key pages. Think of it as a cover letter for AI — while robots.txt tells crawlers what they're allowed to access, llms.txt tells them what your brand actually is and where to find the important information.
The file was proposed by Jeremy Howard of Answer.ai in late 2024 and is documented at llmstxt.org. It's not an official web standard. It's a convention — one that a growing number of companies have adopted, including Anthropic, Cloudflare, Vercel, and Mintlify.
How llms.txt Differs from robots.txt and sitemap.xml
These three files serve different purposes, and brands need all of them for complete AI and search engine accessibility.
| File | Purpose | Who reads it | Format | Controls |
|---|---|---|---|---|
| robots.txt | Controls crawler access | Search engines + AI crawlers | Plain text directives | Which pages bots can visit |
| sitemap.xml | Maps your site structure | Search engines | XML | Which pages exist and when they changed |
| llms.txt | Explains your brand to AI | AI models (when accessed) | Markdown | How AI understands your brand context |
robots.txt is a bouncer — it decides who gets in. sitemap.xml is a floor plan — it shows what's where. llms.txt is a briefing document — it explains what matters and why.
The Format
llms.txt uses Markdown with a simple structure. The spec is deliberately minimal — a few sections that give AI models the context they need to accurately represent your brand.
Required sections:
- Title / Brand description — One or two sentences explaining what your company does
- Key pages — Links to your most important pages with brief descriptions
Optional but recommended sections:
- Products or services overview
- Target audience or market context
- Documentation or resource links
- Contact or official channels
Here's a simplified structure:
# Your Brand Name
> One-line description of what your brand does.
## About
2-3 sentences of brand context. What you do, who you serve,
what makes you different.
## Key Pages
- [Product Page](/products): Description of your product offering
- [Pricing](/pricing): Current pricing and plans
- [Blog](/blog): Industry insights and guides
- [Documentation](/docs): Technical documentation
## Products
- **Product A**: Brief description
- **Product B**: Brief description
You can see a real-world example at getcited.in/llms.txt — Cited's own llms.txt file, which includes brand positioning, product descriptions, and key page links.
Step-by-Step Implementation
Step 1: Create the file. Create llms.txt in Markdown format. Keep it under 2,000 words — AI models process shorter, focused content more reliably than lengthy documents.
Step 2: Write your brand description. Lead with what your company does, not your history. "B2B SaaS platform that tracks brand visibility across AI search engines" is useful. "We're passionate about empowering businesses" is not.
Step 3: List your key pages. Include 10-20 important pages — products, pricing, core blog posts, documentation. Each link needs a one-line description of what the AI model will find there.
Step 4: Deploy to your domain root. The file must be accessible at yourdomain.com/llms.txt. For Next.js, place it in public/. For WordPress, upload to your root directory via FTP or use a plugin.
Step 5: Test accessibility. Visit yourdomain.com/llms.txt in a browser to confirm it loads. Check that your robots.txt doesn't block access to .txt files.
The llms-full.txt Variant
The spec also defines llms-full.txt — an extended version with detailed product descriptions, full feature lists, and expanded brand context. The idea is that AI models with larger context windows consume the full version while models with limited context use the shorter llms.txt. In practice, most brands start with llms.txt and add the full variant only if they have extensive technical documentation.
What to Include — and What Not To
Include: core brand positioning, products with clear descriptions, key differentiators, target market context, links to your most authoritative pages, and schema-relevant facts like founding year and headquarters.
Do not include: pricing that changes frequently (link to the pricing page instead), internal URLs, sensitive business data, promotional language, or content behind authentication walls.
Does llms.txt Actually Work? An Honest Assessment
Here's where most guides stop and tell you to implement llms.txt immediately. The reality is more nuanced.
Adoption is still early. The ALLMO study found roughly 10% of websites have implemented llms.txt. That number is growing, but it's far from universal.
No major AI platform has confirmed reading it. Google's Gary Illyes has publicly stated that Google does not support llms.txt. No other major platform — OpenAI, Anthropic, Perplexity — has officially confirmed their models consume it during inference or training. The companies that have adopted it (Anthropic, Cloudflare, Vercel, Mintlify) have done so on their own sites, which signals implicit support but not confirmed consumption.
Direct citation impact is statistically insignificant. A study by Trakkr analysing 337,000 AI citations found a p-value of 0.85 for the direct relationship between having llms.txt and receiving AI citations. In plain language — having llms.txt did not statistically predict whether a brand would be cited by AI. The correlation was essentially random.
But the indirect value is real. The brands that implement llms.txt tend to have clean technical infrastructure, structured content, and clear positioning. Creating llms.txt forces you to articulate your brand in a way AI can parse — and that exercise improves overall AI readiness even if no model ever reads the file directly.
Developer documentation sees the most value. Companies with extensive API docs and technical resources report the clearest benefits. Their use case is specific: helping AI coding assistants understand documentation structure to generate accurate code examples.
The Practical Recommendation
Implement llms.txt. It takes 30 minutes, costs nothing, has zero SEO risk, and forces a useful exercise in structured brand documentation. But don't treat it as a citation lever — it won't move your AI Visibility Score on its own.
Think of it as one signal in a broader GEO strategy. Your robots.txt configuration determines whether AI crawlers can reach your content. Your content structure determines whether they cite it. Your cross-platform authority determines whether they trust it. llms.txt is the file that says "here's who we are and where to find our best content." That has value — it's just not the whole strategy.
For a deeper look at how Indian brands are approaching llms.txt in practice, see our llms.txt guide for Indian brands.
Key Takeaways
- llms.txt is a Markdown file at your domain root that gives AI models structured context about your brand — proposed by Jeremy Howard / Answer.ai
- It complements robots.txt (access control) and sitemap.xml (site structure) — each serves a different purpose
- No major AI platform has confirmed reading llms.txt, and the Trakkr 337K-citation study found no statistically significant direct citation impact (p-value 0.85)
- The indirect value is real — creating llms.txt forces structured brand documentation that improves overall AI readiness
- Implementation takes 30 minutes: create the file, write a brand summary and key page links, deploy to your domain root
- Include stable brand information and key URLs — exclude frequently changing prices, internal pages, and sensitive data