Learn / Fixes
How to write an llms.txt for an online store
An llms.txt file is a short, machine readable map of what a site contains and where the authoritative version of each thing lives. For a store it is most useful pointing at your policies, your feed and your reference pages, not at your catalogue, which belongs in a feed. It grants no permission and replaces nothing: robots rules still decide access, and structured data still decides whether a product is legible.
An llms.txt is a short, machine readable map of what your site contains and where the authoritative version of each thing lives. It is useful, it is cheap, and it is routinely asked to do two jobs it cannot do: granting permission, and carrying your catalogue.
What it is genuinely good for
The value is in disambiguation. Stores accumulate several pages that all partly answer the same question: a returns policy in the footer, a returns section in an FAQ, a returns paragraph on a product page, and a help article. An llms.txt says which one is authoritative.
- Your policy pages: shipping, returns, warranty. One canonical URL each.
- Your product feed, so a reader looking for your catalogue is sent to the thing built for it.
- Your reference and guide pages, if you publish them.
- A one line description of what the store sells, in plain terms rather than marketing register.
What it cannot do
It grants nothing. If your robots rules disallow an agent, or your CDN blocks the category, the agent never fetches your llms.txt either. Permission is decided in robots.txt and at your edge, and nowhere else.
It also does not make a product legible. A file that points at a product page whose price only exists after JavaScript runs has pointed accurately at something unusable. See how to add product schema for AI agents.
Keep it small, and keep it current
The failure mode of this file is not being wrong, it is being stale. A map that points at URLs you retired is worse than no map, because it is confidently incorrect and nothing surfaces the error.
Generate it from whatever already knows your site structure rather than maintaining it by hand, and regenerate it when content changes rather than on a calendar. If it is hand written, it will be accurate on the day it is written and slowly stop being so.
Where it belongs in the order of work
After your bot rules, after your structured data, after your feed. Those three decide whether you are reachable, legible and enumerable. An llms.txt improves how well you are understood once all three are true, and does nothing if any of them is false.
For the definition of the format itself, see llms.txt.
Questions
Does llms.txt control whether AI can use my content?
No. It is a map, not a permission system. Access is decided by your robots rules and by whatever your CDN does, and treating llms.txt as a control is how a store ends up believing it has made a decision it has not made.
Should I list all my products in it?
No. A catalogue belongs in a product feed, which is built for it and can be refreshed independently. An llms.txt stuffed with product URLs is large, goes stale, and buries the things it is genuinely good at pointing to.
Is it worth doing if support is inconsistent?
For a store, it is cheap and low risk rather than transformative. It is a small file that states where your authoritative pages are. Do it after your feed, your structured data and your bot rules, not before.