What we fill in and what you write
Some tools promise to build your whole llms.txt without you typing a thing. Be suspicious: a file worth having describes real facts about your store —what makes it different, your shipping times, who you sell to— and none of that can be read anywhere. Inventing it would be worse than leaving it empty, because an assistant repeats it.
So we do the half that can be done well, and we tell you exactly which half that is.
We read it from your site
- The site name, from the
<title>or theog:site_name. - The one-line description, from your meta description.
- Your main categories with their URLs, pulled from the sitemap and prioritising the ones your own homepage links to.
- The key pages we find: shipping, returns, contact, about us, FAQ.
- The blog and the product page count (counted, never listed: an llms.txt is a summary, not a catalog dump).
- The platform, from technical signals in the HTML. If there's no clear signal we say "not detected" instead of guessing.
You write it
- What you sell and who to, if your meta description doesn't say it.
- What sets you apart, with verifiable facts.
- Shipping times and costs, returns, support and payment. None of that sits in the HTML reliably, and getting it wrong here is the only thing that can genuinely hurt you.
- The one-line description for each category: the name alone doesn't tell an assistant much.
- The contact details.
All of that comes out in the file between [FILL IN: …] markers, highlighted in the preview. They're there so it's impossible to upload the file without noticing. If your site declares another language the markers come out in that language too —a Spanish store gets [COMPLETA: …]— because the whole file is written in the language your store speaks.
How to upload it, platform by platform
The file goes at yourdomain.com/llms.txt, at the root, next to your robots.txt. We spell it all out in the llms.txt guide for online stores, and there's more background on the llms.txt overview page; this is the summary.
PrestaShop
Upload it over FTP or from your hosting file manager to the public root, the same folder your robots.txt lives in. The mistake that keeps happening: putting it inside the theme folder. Next time you update the template, it disappears.
WooCommerce and WordPress
Same thing: to the root of the installation, over FTP or through the file manager. If you use an SEO plugin that handles virtual files, check it isn't intercepting the path and serving a 404 instead.
Shopify
On Shopify you can't upload it to the root, and it's worth knowing before you lose an afternoon: the platform doesn't give you access to that folder. The ways out are an app that serves the file for you, a proxy or your own subdomain if you control the DNS, or sticking with what is editable —the robots.txt through robots.txt.liquid— plus your product structured data, which carries more weight than the llms.txt anyway. That third option is perfectly reasonable.
Magento and custom stacks
To the public folder your web server serves, the same one as the robots.txt. Then check two things: that it responds in a private window and that it's served as text/plain.
Before you upload it
- Replace every
[FILL IN: …]— or[COMPLETA: …], if the file came out in your store's language. An llms.txt with the markers still in it is worse than having none. - Review the category names. They come from the URL, not from the page title, and a slug doesn't always read like the commercial name.
- Remove the categories that don't define the business and add the ones missing. A sitemap also lists internal collections.
- Check that AI bots can get in with the AI citability test. If your robots.txt blocks them, your llms.txt is a sign inside a locked shop.
The llms.txt is a standard proposed in 2024. Neither OpenAI, nor Anthropic, nor Google has officially adopted it, and nobody guarantees they read it. We recommend it because doing it properly takes twenty minutes and because it's unlikely to hurt — not because it's a ranking trick, and we promise no result from adding it.
The only way it can hurt you is if you lie or if you let it go stale. A file promising 24-hour shipping when you take a week is handing the wrong ammunition to something that will repeat it.
Frequently asked questions
Is it free?
Yes, and no sign-up. You paste the URL, see the file right away and take it with you.
Why don't you fill the whole thing in?
Because half of an llms.txt is facts only the person running the store knows: what sets you apart, how long you take to ship, which countries you sell to. A script that fills that in is inventing, and what it invents an assistant will repeat in front of a customer of yours. We fill in what can be read from the site and mark the rest.
Does it work for any site?
It works with any public domain. It's built for online stores: if there's no sitemap, you still get the file with whatever can be read from the homepage and more gaps to fill in. And note the file itself comes out in the language your site declares in its <html> tag, which is deliberate: the assistants reading it are answering your customers in that language.
What if my store is on Shopify?
The file is generated the same way, but on Shopify you won't be able to upload it to the root. The three real ways out are above, including giving up on it and reinforcing everything else.
Is this Content Mood's diagnosis?
No. This is a signalling file, the smallest of the four levers. The full diagnosis looks at your entire blog —stale content, links to the catalog, whether AI can cite you— and it isn't automatic: Lautaro does it by hand, capped at thirty.
Last updated: August 2026.