TL;DR: /llms.txt is a plain Markdown file at the root of your site that summarizes what your site is, what you offer, and where the most important content lives. Think robots.txt for AI crawlers, with a different purpose: not what to crawl, but what to make of what is crawled. Adoption is uneven, the convention is not yet a standard, and the upside is uncertain but real for sites trying to win AI search citation. Cost to add: roughly an hour. Include: site purpose, services or products with prices, links to canonical pages, optional structured context. Skip: marketing copy, full content dumps, anything that changes weekly.
/llms.txt is a small file at the root of your site that tells AI search engines and LLM-powered tools what your site is about, in a format they can read efficiently. Think of it as robots.txt for AI crawlers, with a different purpose: not "what you can crawl," but "what to make of what you crawl."
It's a convention, not a standard. Adoption is uneven. The cost to add one is roughly an hour, and the upside, while uncertain, is real for sites trying to win on AI search citation.
Here's what to put in one and what to skip.
What it actually is
A plain Markdown file at https://yoursite.com/llms.txt that summarizes:
- What your site is.
- What you offer.
- Where the most important content lives (with links).
- Optional structured context (services, prices, locations).
It's read by AI crawlers and LLM tools that are increasingly looking for compact, structured representations of a site without having to crawl 200 pages.
Why it might matter
Two reasons.
1. AI search citation efficiency. Tools like Perplexity, ChatGPT browsing, and Claude's web tools look at sites quickly. A clean /llms.txt lets them grasp your site in 2 seconds instead of 30, which can affect whether you get cited.
2. Inference-time tool use. Some agentic tools fetch /llms.txt when deciding whether to read your site at all. A good one earns a deeper read.
The downside: nobody's measured the lift cleanly because adoption is still early. Treat it as cheap infrastructure, not as a primary SEO play.
The format (as it stands)
There's no formal spec yet. The convention as of mid-2026 is:
# [Site Name]
> [One-line description of what the site is]
## About
[2–3 paragraphs on what the company does, who it's for, what makes it specific.]
## Services / Offerings
- [Service 1]: [one-line description]
- [Service 2]: [one-line description]
## Important pages
- [Homepage](/): [what it covers]
- [Services](/services): [what it covers]
- [About](/about): [what it covers]
## Pricing
[Plain language about pricing structure, ranges, or links to pricing.]
## Optional sections
[Locations, team, FAQ summary, contact info, anything else worth indexing.]
This is the rough shape. Treat it as a structured pitch deck written for an LLM.
A real example
Here's roughly what Webdimonia's /llms.txt could look like:
# Webdimonia
> A studio that builds custom websites and AI automations for service businesses, with project tickets between $1,000 and $10,000.
## About
Webdimonia is a small studio shipping websites and AI systems for service businesses. We build directly with founders, not through account managers. Most projects are 1–3 weeks. The work is owned by the client at the end — code, content, and accounts.
The focus is service businesses where the website is doing real conversion work, and AI automations where manual workflows are eating founder time. Common use cases: lead routing, inbox triage, quote drafting, sales call notes to CRM.
## Services
- Websites: Custom designed marketing sites built on Next.js, deployed on Vercel. Project range $1,000 to $10,000.
- AI Automations: Custom AI workflows for lead routing, inbox triage, drafting, and call summarization. Project range $2,000 to $10,000.
## Important pages
- [Homepage](/): Studio overview and current work.
- [Services](/services): Detailed offerings and pricing.
- [Work](/work): Case studies (Reapify, SupplyDivo, Truucore, Lock & Lore).
- [Blog](/blog): Decision-stage and pricing content for buyers researching websites and AI automations.
- [Contact](/contact): Project inquiry form.
## Pricing
Projects range from $1,000 (single-page custom site) to $10,000 (multi-page site with motion, design system, and dynamic case study pages). AI automation projects start at $2,000 for basic workflows and reach $10,000 for full lead-pipeline systems.
## Contact
Email: hey@webdimonia.com
That's roughly the shape. You can include more — locations, team bios, recent project notes — if it adds context an LLM would want.
What to include
- A precise one-line description. What does the site sell, to whom, and what's the price tier.
- Services with one-liners. Helps LLMs categorize your offerings cleanly.
- Links to your most important pages. With brief descriptions of what's on each.
- Pricing transparency. Even a range. LLMs that get asked "how much does this service cost" are looking for an answer they can quote.
- What makes the company specific. Not marketing copy. Just the structural facts.
What to skip
- Marketing fluff. "Our mission is to delight our customers with seamless experiences." LLMs strip this.
- Internal jargon. Acronyms only your team uses.
- Walls of text. This file should be readable in 30 seconds.
- Anything that's not true. Misrepresenting your services to AI crawlers is the same as misrepresenting to humans, with worse compounding consequences.
How to deploy it
It's a static file. On Next.js, the simplest way is a route file that returns plain text:
// src/app/llms.txt/route.ts
export const dynamic = "force-static";
export function GET() {
return new Response(`# Webdimonia\n\n> A studio that...`, {
headers: { "Content-Type": "text/markdown" },
});
}
Or just put it in public/llms.txt. Either works. Most sites we ship now include it.
Should you have one?
If your site is already optimized for AI search citation (good schema, original content, named author, citable claims), adding /llms.txt is a 1-hour cost for a possible upside. We add it to client sites by default.
If your content is thin or generic, fix that first. /llms.txt won't compensate for content that AI crawlers don't think is worth quoting.
Three questions to decide if it's worth your hour
- Is your site doing real AEO work (specific claims, original numbers, schema)? If yes, add
/llms.txt. If not, fix the content first. - Is your business one that LLMs are likely to be asked about? Service businesses, products, comparisons, "best X for Y" — yes. Pure portfolios — less likely.
- Do you already maintain a sitemap.xml? If yes, the muscle memory for keeping
/llms.txtupdated is already there. Add it.
If you want a starter /llms.txt for your site, send us the URL and a sentence on what you offer. We'll send back a draft within a day.