Probably not, and the cases where the answer flips to yes have almost nothing to do with citations. That's the short version of "do you need llms.txt," and it deserves to sit in the first paragraph rather than after twelve hundred words of suspense. The file will not get you cited by ChatGPT, Perplexity, or anyone else, which every serious test keeps confirming. It might, for a specific kind of site, help agents navigate your documentation. This guide is the decision framework: who publishes the file, what the evidence actually shows, which site types have a real case, and how to add one correctly if you land on yes.
What llms.txt Is, In One Paragraph
The llms.txt proposal is a markdown file at your site's root that lists your important pages with short descriptions, so an AI system with a limited context window can find what matters without crawling everything. It came out of the developer-tools world as a courtesy index for agents, an index card handed to visiting machines at the door. It was never a submission form or a ranking input, and no major engine has documented reading it as part of answer selection. Everything confused about the file starts with people assigning it a job its own spec never claimed.
Who Actually Publishes One
Adoption is where this question gets interesting, because the file has spread fast in exactly one neighborhood. A census of 109 domains shared on r/DigitalMarketing checked which sites serve a real llms.txt, testing the response body rather than trusting status codes, since plenty of sites return a styled 404 with a 200 attached:
Checked 109 sites for llms.txt. 83% of SaaS have one, 4% of news sites do, and not a single site had ai.txt
Follow up to the robots.txt pull I did earlier this week. Same 109 domains, this time checking whether they actually publish an llms.txt, and while I was in there, ai.txt as well. On method, because it changes the number: I checked content...
The headline number, 43 of 109, sounds like real traction. Wait, I need to qualify that, because the breakdown tells a different story. SaaS came in at 83%, ecommerce and finance around 40%, marketing publishers at 26%, and news sites at 4%. One news site out of twenty two. As the author put it, that isn't an adoption curve, it's two unrelated populations.
The census found two more things worth carrying into your decision. First, several ecommerce files weren't decisions at all: multiple well-known brands on Shopify serve an identical generated agent-instructions file that the platform produces, which nobody on those teams wrote and few probably know exists. Platform defaults inflate every adoption stat in circulation. Second, publishers don't agree on what the file is even for. Some companies use theirs as a machine-readable content index; at least one major magazine uses the same filename to tell AI systems to keep out. A file whose adopters can't agree on its purpose is a convention, and a young one.
So the honest reading of adoption: it measures how fast a tactic travels through SaaS circles, and says nothing about whether anything reads the file. Which brings us to the part that should actually drive your answer.
Know exactly what AI says about your competitors.
RankControl's Recon Agent monitors competitor citations across ChatGPT, Perplexity, Claude, Gemini, Grok, and Google AI Mode. See where they show up and you don't.
What the Evidence Says About Citations
Three kinds of evidence exist, and they agree with each other.
Server logs. Sites that track AI crawlers in their access logs keep reporting the same pattern, including a commenter in that census thread who checked: AI crawlers request robots.txt constantly and llms.txt almost never. In our own 12-site logs, the big training crawlers barely touched the file, with OpenAI's search crawler the one inconsistent exception.
Controlled testing. We added llms.txt to 12 sites and tracked citations for 90 days across ChatGPT, Perplexity, Claude, and Gemini. The change landed at +1.5% total, inside normal weekly noise, while the sites that did gain citations gained them from unblocked crawlers and restructured pages. An AEO auditor in one community thread reported the same shape from the outside: of the sites they'd audited that week, the ones with a valid llms.txt had citation profiles with nothing in common. Inert is the word they used.
The engines themselves. Google's own AI search guidance includes a mythbusting section on what you don't need to do, and llms.txt sits squarely in it: the file does nothing for Search or AI Overviews. No other major engine documents it as an input either. There's also a structural reason to expect this, which a sharp Reddit commenter nailed: if engines took a self-authored file at face value, everyone would abuse it, so any careful engine has to verify by crawling your actual pages anyway. The verification step makes the map redundant.
Anyone selling llms.txt as a citation play is selling against all three piles at once.
The Decision Framework, By Site Type
Here's the thing the yes-or-no debate keeps missing: the answer segments cleanly by what kind of site you run.
| Your site | Do you need it? | Why |
|---|---|---|
| Docs-heavy dev tool | Yes, worth an afternoon | Agents genuinely navigate docs; the file is a real index |
| SaaS marketing site | Optional, ten minutes | Harmless courtesy; expect nothing from it |
| Shopify store | Check first | The platform may already generate one for you |
| Content site or publisher | Skip, or use it as policy | Almost no adoption peers; some use it to say keep out |
The dev-tools row deserves the explanation, because it's the one lane with a genuine mechanism. Companies whose product lives in documentation publish serious files: one developer's spot check found Stripe serving a 65KB markdown index of its docs and PostHog serving one north of 300KB. Those files exist because the docs were already markdown with clean URLs, so the index cost an afternoon, and because agents answering questions about those products benefit from a map of several hundred doc pages. If a meaningful share of your buyers ask AI assistants how your product works, you're in this row, and the file earns its slot as documentation plumbing.
Everyone else is choosing between ten harmless minutes and skipping it entirely, and both choices are correct. What would be incorrect is budgeting real hours, or real money, against the citation claim the evidence just dismantled.
26 content formats. Published on your domain. Matched to your brand.
Guides, comparisons, listicles, case studies, and more. RankControl generates content that gets cited by ChatGPT, Perplexity, Claude, Gemini, Grok, and Google AI Mode.
If You Add One, Add It Right
Landing on yes, or on "ten minutes, why not," here's the whole job done properly.
- Serve it at the root.
yourdomain.com/llms.txt, plain text, markdown format. - List what matters, described honestly. Your key pages with a one-line description each. An index of ten real pages beats a dump of four hundred URLs.
- Never contradict your robots.txt. In our test we found sites whose llms.txt recommended pages their robots.txt blocked, a map pointing at locked doors. Align the two files, and the llms.txt and robots.txt checklist covers the full alignment pass.
- Update it when key pages change. A stale index misdirects the few agents that do read it, which is worse than no index.
- Pay nobody. Any invoice with "llms.txt optimization" on it is measuring your anxiety, and a vendor leading with the file has told you how they pick deliverables.
The Question Behind the Question
Between us, most people asking whether they need llms.txt are really asking something else: is there a cheap file-shaped thing standing between me and AI citations? And the honest answer is that no file does that job, because citations are earned in a different room. Engines cite pages they can crawl and extract cleanly, from brands they've learned to trust, which means the work lives in crawler access, answer-first structure, entity consistency, and third-party mentions, the strategies with measured effects behind them.
We wrote a whole verdict on whether llms.txt is worth it after the GPT-5.6 retrieval changes, and the one-line version holds here: as a courtesy, harmless; as a strategy, no. The need question resolves the same way. Nobody needs the file for visibility. Some teams need it as documentation infrastructure, and that's a fine reason with the hype stripped off.
How You'd Know If This Answer Expires
Verdicts in AI search deserve expiry conditions, so here's this one's. The answer flips toward yes if a major engine documents the file as a retrieval input, or if crawler logs at scale start showing the big bots fetching it and citation changes tracking its contents. Both would be visible fast: requests to /llms.txt in access logs, and citation shifts in tracking data. Neither has happened through two model generations.
The practical move is having both instruments running, which you likely want anyway. Grep your logs monthly for who requests the file, and keep per-engine citation tracking on a weekly rhythm so any change, from this file or anything else, lands on a labeled baseline. That second instrument is what our visibility tracking does every week across six engines, and the Monday brief shows the shifts the week they happen, so you'd know the file started mattering before the checklists do.
Do you need llms.txt? If your docs are the product, spend the afternoon. If yours is any other site, spend the ten minutes or don't, and put the hours where citations actually come from. Either way, stop letting a text file carry the weight of your AI search strategy. It was never built for it.
Your competitors are getting cited by AI. You're not.
Every day without citation tracking is a day your competitors pull ahead in ChatGPT, Perplexity, and Claude.
