Published August 10, 2026
Does llms.txt actually do anything for AI search visibility?
Short answer: almost certainly not for AI search, and Google has said so directly. The one place it shows real signs of life is with AI coding agents. If a tool generates the file for you for free, keeping it is harmless — but building a strategy around it is not supported by the evidence.
What this means
An llms.txt file is a plain Markdown file at the root of your site — yoursite.com/llms.txt — that summarizes what your business does and links to your most important pages. It was proposed by Jeremy Howard of Answer.AI in September 2024, on the reasoning that language models have limited context windows and that stripping a cluttered HTML page down to clean text is slow and lossy (Howard, 2024). The idea was to hand a model a tidy index instead.
Worth being precise about one thing, because it causes real confusion: despite the name, llms.txt is nothing like robots.txt. It blocks nothing, permits nothing, and controls nothing. It is a suggestion that a machine is free to ignore, and for the most part, machines do ignore it.
Who this applies to
If you run a local service business — a clinic, a law firm, a contractor, a restaurant — and someone has told you that you need an llms.txt file to show up in ChatGPT, this article is for you. It also applies if your website platform quietly started generating one and you are wondering whether it is doing anything. The answer differs depending on who your customers are, and that distinction turns out to matter more than anything else here.
How we'd evaluate whether llms.txt is worth your time
We start with your server logs, because that is the only place the truth lives. The question is not whether your file is well-written — it is whether anything ever requested it. Most owners have never checked, and the answer is usually "nothing did." From there we ask how your buyers actually shop: someone choosing a dentist behaves nothing like a developer picking a software library, and only one of those paths currently runs through llms.txt.
Available options
- Do nothing. Perfectly defensible. Google has stated it ignores the file entirely, so skipping it costs you nothing in Google Search.
- Let your platform generate it. Wix and similar builders increasingly create these automatically. Near-zero effort, near-zero expected return, but it costs you nothing either.
- Write and maintain one deliberately. Only worth it if AI coding agents or other agentic tools are plausibly part of how customers find you — and even then, link to it so agents can discover it.
- Pay someone to build one as an "AI visibility" service. We would not recommend this, and we do not sell it. The evidence does not support the price tag.
Benefits, limitations, and tradeoffs
The honest benefit is cheapness and a bet on the future: if the web becomes genuinely agentic, a file agents already know how to read could matter later. The limitation is that today, the base rate of readership is close to zero. There is also a real downside that rarely gets mentioned — an llms.txt file is content that agents are built to trust, which makes it an attractive target. If it goes stale or someone edits it without your knowledge, it misleads every agent that reads it. Treat it like code, not like marketing copy: version it, restrict who can change it, and keep it to plain links and descriptions rather than anything instruction-shaped.
What we know about how this actually plays out
This is a rare case where the evidence is unusually direct. Google's own Search Central documentation addresses it in a section titled "Mythbusting generative AI search: what you don't need to do." Google states that you don't need to create machine-readable files, AI text files, or Markdown to appear in Google Search including its generative AI features, "as Google Search itself doesn't use them," and adds that maintaining such a file "will neither harm nor help your site's visibility or rankings in Google Search, as Google Search ignores them" (Google Search Central, 2026).
The largest independent measurement backs this up. Ahrefs analyzed server logs across 137,210 domains and found that 28% published an llms.txt file, but 97% of those files received zero requests in May 2026 — nothing fetched them at all, not bots, not humans. Of the small fraction that were fetched, named AI bots accounted for 19.5% of requests, and AI retrieval bots specifically — the ones powering AI search answers — made up just 1.1%. The study also found that AI bots never requested llms.txt files that didn't exist, meaning publishing one does not put you on any AI system's radar (Linehan & Guan, 2026).
Two caveats the researchers themselves raise, which we think are important. A fetch is not a read: a bot requesting the file proves nothing about whether it acted on the contents, so every number in that study is a ceiling rather than a floor. And the sample skews technical, so 28% adoption should be read as an upper bound.
Google is not entirely of one mind here, which is worth knowing. The Chrome team shipped an llms.txt check inside Lighthouse's experimental agentic browsing audits, with documentation noting that without the file, "agents may spend more time crawling the site to understand its high-level structure and primary content" (Chrome for Developers, 2026). That is a different team optimizing for a different future — agents acting on your site, not AI search citing it. The Ahrefs data points the same direction: the heaviest identifiable AI readers were coding and agentic tools, with Anthropic's Claude Code out-fetching every AI retrieval bot, assistant, and training crawler.
Next steps
Check your logs for requests to /llms.txt before spending another minute on it. If your platform already generates one, leave it and move on. If you are being sold an llms.txt file as the path to showing up in ChatGPT, ask the seller for their evidence — then weigh it against Google's own documentation. The things that actually move AI visibility are less exciting and better supported: content that says something only you can say, a clean crawlable site, accurate business details, and a real presence in the third-party sources these systems read.
Orlando considerations
For most Orlando businesses we talk to — medical practices, home services, hospitality, professional services — customers are not reaching you through coding agents, so llms.txt is close to irrelevant to how you get found. Your leverage is elsewhere: an accurate Google Business Profile, consistent details across directories, and genuine reviews. Those feed the local signals AI tools lean on when someone asks which business in Orlando to call.
Frequently asked questions
Will adding llms.txt help me show up in ChatGPT?
There is no evidence that it will. AI retrieval bots — the crawlers behind live AI answers — accounted for roughly 1% of requests to these files in the largest study available, and no AI system goes looking for a file you haven't published. If showing up in ChatGPT is the goal, your effort is better spent elsewhere.
Does Google use llms.txt at all?
No. Google Search Central states directly that Google Search doesn't use these files and ignores them. Google may crawl the file as it crawls any URL it discovers, but that isn't special treatment. Confusingly, Chrome's Lighthouse does audit for it — that's aimed at AI agents browsing your site, not at Google Search rankings.
Could having an llms.txt file hurt me?
Not in Google Search — Google says it neither helps nor harms. The genuine risk is security: agents are designed to trust this file, so a stale or tampered-with version misleads anything that reads it. If you keep one, control who can edit it and review anything your platform generates on your behalf.
Is it worth creating one anyway, just in case?
If it's free and automatic, sure — the cost is near zero and it may matter more later if agents end up mediating AI search. What we'd push back on is paying for one, or treating it as a meaningful part of an AI visibility strategy. Publishing alone isn't enough regardless: agents fetch these files when something points them there, not speculatively.
References
Chrome for Developers. (2026, May 5). llms.txt. Lighthouse — Agentic browsing audits. https://developer.chrome.com/docs/lighthouse/agentic-browsing/llms-txt
Google Search Central. (2026, July 10). Optimizing your website for generative AI features on Google Search. Google for Developers. https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
Howard, J. (2024, September 3). The /llms.txt file. llms-txt. https://llmstxt.org/
Linehan, L., & Guan, X. (2026, June 15). We analyzed 137K sites: 97% of llms.txt files never get read. Ahrefs. https://ahrefs.com/blog/llmstxt-study/
Last updated: August 10, 2026