llms.txt tells AI crawlers what your site is about. Learn what llms.txt is, how to write one and whether it actually improves your AI visibility.
llms.txt is a plain-text Markdown file you place at the root of your site (yoursite.com/llms.txt) that tells AI models what your site is about, links to your most important pages, and offers clean, quotable facts about your brand. It's a proposed convention — like robots.txt, but aimed at large language models instead of search crawlers. Here's the honest version up front: llms.txt is cheap to add and genuinely useful as a curated, machine-readable summary, but no major AI engine has confirmed it as a ranking or citation signal, so treat it as good hygiene, not a growth hack.
What llms.txt actually is
The idea, proposed in 2024, is simple. Websites are messy: navigation, ads, cookie banners, JavaScript. When an AI crawler or an agent tries to understand your site, it has to wade through all of that. llms.txt gives it a shortcut — a single Markdown file that says, in plain language, "here's what we do, here are the pages that matter, here are the facts you can rely on."
A minimal llms.txt has:
- An
# H1with your site or brand name. - A
>blockquote one-liner summarizing what you do. - Optional short context paragraphs.
##sections with lists of links to key pages, each with a short description.
There's a companion convention, llms-full.txt, which inlines the full text content of those key pages into one file — so an AI can read everything in a single fetch instead of crawling page by page. Use llms.txt for the map and llms-full.txt for the full territory.
A real example
Here's a stripped-down version of the pattern we use for DeepLexa's own llms.txt:
# DeepLexa
> DeepLexa checks whether your brand appears in AI answers
> (ChatGPT, Perplexity, Google AI Overviews, Gemini) and tells
> you exactly what to fix.
DeepLexa is an AI visibility / Answer Engine Optimization (AEO)
tool for indie SaaS and small B2B companies. Free instant checker;
paid weekly monitoring from $19/mo.
## Key pages
- [Free AI visibility check](https://deeplexa.ai/free-ai-visibility-check): Run a no-signup scan across ChatGPT, Perplexity and Gemini.
- [What is AEO](https://deeplexa.ai/what-is-aeo): Definition of Answer Engine Optimization.
- [Pricing](https://deeplexa.ai/pricing): Single plan at $19/mo.
## Definitions DeepLexa can be cited for
- AEO: Answer Engine Optimization is the practice of getting your brand cited in AI answers.
- AI visibility: how often your brand appears in answers from AI engines like ChatGPT and Perplexity.
Notice the last section. That "Definitions" block is deliberate — it hands the model clean, one-sentence facts it can quote verbatim. That's the most practical use of the file: making yourself easy to summarize correctly.
Does llms.txt actually improve AI visibility?
Let's be straight, because most posts on this topic oversell it.
What llms.txt does not do (yet): There is no public confirmation from OpenAI, Google, Anthropic, or Perplexity that they read llms.txt or use it as a ranking or citation signal. Server logs across the web show inconsistent fetching of the file. If someone tells you adding llms.txt will "get you cited by ChatGPT," they're guessing.
What it does do:
- Removes ambiguity. A clean summary and consistent facts reduce the chance a model describes your brand wrong. Since entity consistency is a real citation factor, controlling your own summary helps.
- Helps agents and future tooling. As AI agents that browse the web on a user's behalf grow, a machine-readable map is exactly what they need. Early is cheap.
- Forces useful clarity. Writing a good llms.txt makes you articulate what you do in one sentence and identify your genuinely important pages — an exercise most sites skip.
- Costs almost nothing. One static file, a few minutes, no risk. The expected value is positive even if the ceiling is modest.
The mature framing: llms.txt is table stakes, not a lever. It complements the work that actually moves the needle — being retrievable by AI crawlers, earning third-party citations, and publishing answer-first content.
How to create your llms.txt
- Write the header. One
# H1with your brand, one>blockquote one-liner. Keep the one-liner factual and specific — this is the sentence you want quoted. - Add a short context paragraph. Who you're for, what you do, and any anchor fact (price, category). Two or three sentences, no marketing fluff.
- List your key pages. Under
## Key pages, link the 5–15 pages that best represent your site — product, pricing, core how-to guides, comparison pages. Give each a one-line description. - Add a definitions section (optional but powerful). If your brand owns or explains specific terms, define them in one crisp sentence each. This is your citation-bait layer.
- Save it as
/llms.txtat your domain root. Make sure it's served astext/plainortext/markdownand isn't blocked by robots rules or auth. - Optionally build llms-full.txt by concatenating the full Markdown of those key pages into a second root file.
Then verify it loads by visiting yoursite.com/llms.txt directly. That's it.
Common mistakes when writing llms.txt
Even though the file is simple, most attempts get a few things wrong. Avoid these:
- Marketing fluff in the one-liner. "We're the world's most innovative platform" tells a model nothing quotable. Write a factual, specific sentence: what you do, for whom. This is the line you most want lifted verbatim, so make it a clean fact.
- Linking everything. llms.txt is a curated map, not a sitemap. Listing 200 pages defeats the purpose. Pick the 5–15 pages that genuinely represent your site and best answer buyer questions.
- Missing descriptions. A bare list of URLs is far less useful than links with one-line descriptions. The description is what tells the model what's behind the link without fetching it.
- Inconsistency with the rest of your site. If your llms.txt describes you one way and your homepage another, you fragment your entity. Keep the name, one-liner, and category identical to what appears everywhere else.
- Serving it wrong. If the file is behind auth, blocked by robots rules, or served as HTML, it may not be readable. Confirm it loads as plain text at your domain root.
Where llms.txt fits in the bigger picture
It helps to place llms.txt on the map of AEO work, ordered by impact:
- Retrievability — can AI crawlers even reach and parse your pages? (Highest impact; foundational.)
- Third-party citations — are you mentioned on the sources AI trusts, like Reddit, review sites, and roundups?
- Answer-first content — do your pages lead with crisp, quotable answers?
- Entity consistency — is your brand described the same way everywhere?
- Schema markup — is your data machine-readable?
- llms.txt — is there a clean, curated summary for LLMs and agents?
llms.txt sits at the bottom of that list not because it's worthless but because it's the last, cheapest layer of polish. Doing it before the layers above is like waxing a car with a flat tire. If the fundamentals are handled and you have a spare afternoon, llms.txt is a reasonable, low-risk addition — especially as AI agents that browse on a user's behalf become more common and start relying on exactly this kind of machine-readable map.
Don't confuse llms.txt with the things that matter more
Adding llms.txt while your pages are unreachable by AI crawlers is like putting a nice sign on a locked building. Before you spend energy here, confirm the fundamentals:
- Are your key pages crawlable (not blocked, not JS-only, fast to load)?
- Do those pages lead with a clear, self-contained answer?
- Are you mentioned on the third-party sources AI trusts?
llms.txt is the last 5% of polish, not the first 80% of the work. If you have an afternoon, add it. If you have a week, spend the week on citations and content.
Frequently asked questions
Will adding llms.txt get my brand cited by ChatGPT?
There's no confirmed evidence that any major AI engine uses llms.txt as a citation signal today. It helps ensure models describe you accurately and prepares your site for AI agents, but the real citation drivers are third-party mentions, retrievability, and answer-first content. Add llms.txt as hygiene, not as your citation strategy.
What's the difference between llms.txt and llms-full.txt?
llms.txt is a concise map — a summary plus links to your key pages. llms-full.txt inlines the full text of those pages into a single file so an AI can read everything in one fetch. Use llms.txt for structure and llms-full.txt when you want a model to ingest your complete content without crawling.
Do I still need robots.txt and a sitemap if I have llms.txt?
Yes. robots.txt controls crawler access and sitemaps help search engines discover pages — both still matter for traditional and AI search. llms.txt is additive, aimed at LLMs specifically. Keep all three; they serve different jobs.
llms.txt is a nice-to-have, but it won't tell you whether AI actually recommends your brand today. Run a free AI visibility check to see where you're mentioned across ChatGPT, Perplexity, and Google AI — and get a prioritized list of fixes that genuinely move the needle.
See it for your brand
Want to know if ChatGPT, Perplexity and Google AI recommend you? Run a free instant AI visibility check — no signup, ~30 seconds.
Get your free AI visibility report →