Does Your Small Business Need an llms.txt File?
Table of contents
The email lands on a Tuesday and it is very confident. A vendor, or a plugin newsletter, or a guy on LinkedIn with a "10 things to fix for AI search" carousel, and the message is the same: you are missing an llms txt file, every serious site has one now, and without it the AI platforms cannot read you, so you are quietly going invisible while your competitors get named. There is a screenshot of the file. It looks technical and important. The owner who forwards it asks the only sensible question: do we actually need this, or is someone selling me a thing? Here is the straight answer, from someone who has added these files to real sites and watched what happened next. The llms.txt file is real, it is cheap, it is harmless, and it is nowhere near the thing that decides whether an assistant names your business. It is a signpost. The pitch is selling you the signpost as if it were the destination.
So let us separate what the file is from what the marketing around it wants you to feel.
What an llms.txt file actually is
Strip the urgency off it and the thing is simple. An llms.txt file is a small plain-text file you place at the root of your website, the same way a robots.txt sits there. Its job is to be a curated map: it points an AI reader at your most important content, in clean text, so that instead of crawling through your whole site and the menus and the cookie banners and the footer, a reader can see a tidy list of "here are the pages that matter and here is what they are about." That is genuinely useful as a courtesy. It is a hand-drawn directory in the lobby that says which floors are worth visiting.
It is also new. The convention is young, it is still settling, and the businesses pushing it hardest are often the ones who can bill you to write one. None of that makes it bad. A clean map of your best content is a reasonable thing to offer a machine that is trying to read you efficiently. The honest part is just how far that goes, and it does not go as far as the email implies.
Does a small business need an llms.txt file?
No. It is a cheap, harmless, optional convention that maps your key content for AI readers in clean text, but it does not force any AI platform to read, trust, or cite you, and most major platforms make no promise to use it. Presence and consistency across sources matter far more.
That is the verdict in one paragraph. Add the file if you like; it takes a few minutes and it cannot hurt. Just do not believe it is the lever. The rest of this explains why the file is weaker than the pitch and what the real lever actually is, because the gap between those two is exactly where owners waste a week feeling productive and move nothing.
What the file does not do
This is the part the vendor email leaves out, so it is worth saying plainly.
An llms.txt file does not make any AI platform read you. It is an offer, not an instruction. The reader on the other side, an assistant from ChatGPT, Claude, Gemini, Perplexity, or one of several others, gets to decide whether it looks at the file at all, and support across these platforms is partial and unpromised. Some may consult a file like this; many make no commitment to use it. Anyone who tells you a specific named platform "reads your llms.txt and ranks you higher" is asserting a vendor internal they cannot actually see. The truthful frame is narrower and more boring: it is an emerging convention with uneven, unguaranteed support, and adding it is a polite gesture, not a guaranteed channel.
It does not make you trusted. A map that points at your pages says "here is my content." It does not say "and other sources agree this content is true." Trust is built when your facts show up the same way in more than one place a reader checks. A file you wrote about yourself, sitting on your own site, is still just you talking about you. It carries exactly the weight of self-description, which is real but small.
And it does not put facts on your site that were not there. If your prices live inside an image, your service is implied by photos rather than stated in a sentence, and your hours read one way on your site and another way on your map listing, an llms.txt file pointing at those pages changes none of that. The pointer is clean; the thing it points at is still unreadable or inconsistent. Your facts have to be readable and consistent regardless of any single file, which is its own piece of work covered in getting your core business facts into a form a machine can read. The file is a directory in the lobby. It cannot fix a building where the rooms are unmarked and the floor plan contradicts itself.
"Add this file or you go invisible" is the part of the pitch to ignore. An llms.txt file points AI readers at your content; it does not force them to read it, make them trust it, or change what your pages actually say. A tidy signpost on a building nobody can find inside does not fix the building.
What actually decides whether an AI platform names you
Here is the thing the file is standing in front of. When an assistant decides which business to put in an answer, it is not looking for a file that volunteers to be read. It is checking whether your core facts are present in the places it already reads, whether they are stated consistently across those places, and whether they are corroborated rather than just asserted once on your own site. That is the lever. The signals that move it are the same ones that have always separated a business an assistant can vouch for from one it skips, and they are laid out in how AI platforms decide which business to recommend.
Think of it as three attributes the assistant is quietly grading, none of which a file supplies.
Your facts are present where it reads. Not just on your homepage, but on your map listing, your directory profiles, and the pages around the web that mention you. An assistant assembles a picture of you from many sources; if your facts only exist in one place, there is not much picture to assemble.
Your facts are consistent across those places. Same name, same hours, same service, same address, everywhere. A contradiction does not average out to "close enough"; it lowers the assistant's confidence in everything near it. The business that reads three different ways in three places has handed the assistant three reasons to trust a competitor instead.
Your facts are corroborated, not just claimed. One website saying you are the best sports physio in town is self-description. Several independent sources describing you the same way is evidence. Assistants weight evidence over assertion, which is why presence across many sources beats a single root-level file every time the two are compared.
A few minutes to write. Points AI readers at your best pages in clean text. Polite, harmless, optional. Sits on your own site, describes you in your own words, and asks to be read. Support across major platforms is partial and unpromised, so the most it can do is make your own content slightly easier to map. It is one source: you, talking about you.
The unglamorous work that actually moves whether you get named. Your core facts stated in plain text, the same way on your site, your map listing, your directory profiles, and the pages that mention you, and corroborated by sources that are not you. This is many sources agreeing, which is the thing an assistant can actually trust. Harder to sell, harder to do, and the only one of the two that decides the answer.
Notice the asymmetry the vendor email depends on. A file is easy to sell because it is easy to add: one artifact, a few minutes, a clean before-and-after screenshot. Presence and consistency across sources is hard to sell because it is hard to do: it is steady, unglamorous, spread across places you do not fully control. So the easy thing gets oversold and the hard thing gets skipped, and the owner ends up with a tidy file and the same invisibility they started with.
A five-minute file, and the visibility jump that never came
Picture the owner from the start. They read the email, they add the llms.txt file, it genuinely takes about five minutes, and they wait for the AI platforms to start naming them. Nothing happens. Not because the file is broken; the file is fine. Nothing happens because their actual problem was never the lack of a signpost. Their prices were in an image. Their service area was a map pin with no town named in words. Their business name showed up three different ways across their site, their listing, and an old directory entry. The assistant trying to read them could not confirm what they did, where, or for whom, and a file pointing at those same unreadable pages gave it nothing new to confirm.
Then they did the real work. They wrote their service in a plain sentence. They put a price range in text. They made the name and hours identical across the site, the map listing, and the directory. They earned a few mentions on pages that were not their own. And they started getting named, not because of the file, but because they had finally become a business an assistant could read and corroborate. The file was a footnote to that. The work was the thing.
That is the whole shape of it. If you want the full version of that work, the strategy for being present and consistent everywhere an AI platform looks, the work that actually earns citations across the sources assistants read is the deep guide, and it is where your real attention belongs. And if the honest read is that pulling your facts into consistent, corroborated shape across the web is more than you want to do by hand, the work of making a small business legible to AI assistants is a service like any other; naming the lever just lets you decide whether you need help with it.
So, add it or not
Add it if you like. It is cheap, it is harmless, and there is a small, real upside in handing a reader a clean map of your best content. Adding the file is fine. Believing the file is the project is the mistake.
The one thing to do after the five minutes is the thing the email did not want you to look at: get your core facts present, stated the same way everywhere, and confirmed by sources that are not you. Drop the signpost if it pleases you, then go work on the building. The deep AEO guide is where that work is mapped, and it is the next thing worth your attention.
