An llms.txt file for a store is a short map, not a catalog. Put in your brand name, one paragraph that says what you sell and where you ship, and links to the collections, guides, and policies a shopper asks about most. Leave out individual product pages, sale pages that will expire, and anything behind a login. If a model can read the file in about a minute and then find the right collection page, the file is doing its job.
The file is a community proposal, maintained at llmstxt.org. It is not a web standard, no standards body has ratified it, and the proposal does not claim that any particular engine reads it. What the proposal does define is the shape: an H1 with the site name, which is the only required part, a blockquote with a short summary, optional detail with no headings, and H2 sections of links, each written as a link title, a URL, and a one line description. A section called Optional holds links an agent can skip when it is short on room.
Start with the summary, not the catalog
The blockquote at the top is the most important paragraph in the file. Write facts a model needs to describe your brand without guessing: what you sell, who you sell it to, where you ship, and what makes the range distinct. Write it in plain sentences. Slogans describe nothing, so leave them out.
For a pet supply store, that paragraph might read: Paws and Trails sells dog and cat food, toys, and walking gear from its Austin shop, shipping across the US. It stocks food for dogs with sensitive stomachs and runs a free fitting service for harnesses.
That one paragraph already answers the questions a model gets asked first: what kind of store is this, and who is it for.
The sections a store needs
Build the file around the pages that answer pre-purchase questions. Most stores need four sections, plus Optional.
Shop. Link your collections, not your products. Each collection gets one line that says what is in it and who it is for. A dog food collection is more useful than forty dog food product pages, because the collection page stays live when individual products change, and the model can follow it to the right product from there.
Guides. Link the pages that help a shopper choose: size guides, fit guides, buying guides, care instructions. These are the pages a model quotes when a shopper asks which product fits a need, so give each one a description that says what question it answers.
Policies. Link shipping, returns, and warranty pages. Assistants get asked about these constantly, and the policy page is usually buried several clicks deep. Put it in the file so the answer is one step away. Include the facts in the link description where they are short, for example the return window, so the model does not have to open the page to state it.
About and contact. Link your about page and, if you have a physical shop, your location and hours. A model describing your brand needs to know where you are based and whether shoppers can visit.
Optional. Put secondary links here: your blog, press page, changelog, and gift card page. These are pages an agent can skip when it is short on room, and the proposal gives them a clear home so they do not clutter the main list.
A complete sample for a store
Say you run a pet supply store. Your file might look like this, replacing yourdomain.com with your actual domain:
# Paws and Trails
> Paws and Trails sells dog and cat food, toys, and walking gear from its Austin shop, shipping across the US. It stocks food for dogs with sensitive stomachs and runs a free fitting service for harnesses.
## Shop
- [Dog food](https://[yourdomain.com]/collections/dog-food): Dry and wet food, including recipes for sensitive stomachs.
- [Cat food](https://[yourdomain.com]/collections/cat-food): Dry and wet food for kittens, adults, and senior cats.
- [Walking gear](https://[yourdomain.com]/collections/walking-gear): Harnesses, leashes, and collars, listed with size ranges.
- [Toys](https://[yourdomain.com]/collections/toys): Chew toys and puzzle toys, described by dog size and toughness.
## Guides
- [Harness fitting guide](https://[yourdomain.com]/pages/harness-fitting): How to measure a dog for a harness and pick the right size.
- [Sensitive stomach food guide](https://[yourdomain.com]/pages/sensitive-stomach-food): How to choose food for a dog with a sensitive stomach.
## Policies
- [Shipping and returns](https://[yourdomain.com]/pages/shipping-returns): Free shipping over 50 dollars. 30-day returns on unused items.
## Optional
- [Journal](https://[yourdomain.com]/blogs/journal): Feeding notes and walking tips.
Notice what is not in it: no individual product pages, no sale banners, no login or checkout pages, and no variant pages for the same product in different sizes.
What stays out, and why
Individual product pages. Link the collection instead. A product page can sell out, get renamed, or get removed. The collection page stays, and the model can follow it to what is in stock now. The one exception is a small number of flagship products that define your store, and even then keep the count low, so the file stays a shortlist.
Sale and seasonal pages. A page that expires teaches the model about a sale that no longer exists. Leave it out, and update the file when a seasonal collection ends.
Anything behind a login, plus cart and checkout pages. A model cannot open them, so linking them adds nothing and wastes room.
Duplicate pages. If two pages say the same thing, link the stronger one. The file is supposed to point at the best source for each fact, not at every page that mentions it.
Marketing copy. Best in class and game changing describe nothing. The model needs facts: what you sell, where you ship, what the return window is.
How long the file should be
The proposal says the file itself stays small enough to fit in context, with the detail living behind the links, fetched only when needed. Treat that as your test. If it takes more than about a minute to read, trim it back to collections and key pages. A long file is not a thorough file. It is a file a model may never finish reading.
Revisit the file when your catalog changes. Collections get renamed, categories get removed, guides get rewritten. A file that points at last season's catalog teaches the model last season's catalog. Check it after every catalog change, and again when a policy changes, because a wrong return window in this file is worse than no return window at all.
The fundamentals
This guide covers what goes in the file for a store. The shared mechanics live in our pillar guides, see our llms.txt guide, which covers the full format, a complete sample, and per-platform publish steps. For how to get the file live on your platform, see our llms.txt platform guides for Shopify, WooCommerce, BigCommerce, Salesforce Commerce Cloud, Adobe Commerce, Wix, Squarespace, a self-hosted site, and a custom website. For crawler rules, which do not belong in this file, see our robots.txt guide for AI search.
A pet store that listed everything
Picture a pet supply store that puts every product page in its llms.txt file, more than three hundred links, plus sale pages from last season and a link to its checkout. A model reading the file has to wade through expired sales and dead product pages before it reaches the collections, and the file is so long that the model may stop before it reaches the policies at the end.
The fix is to cut, not to add. Keep the summary, keep the four collections, keep the two guides and the one policy page, and move the blog to Optional. The file drops to about a dozen links, every one of them live, and the model can read it in under a minute and then follow the right collection link.
What this guide does not cover
Writing the file is one page of a larger job. Your catalog drifts, crawler behavior changes, and being readable is not the same as being recommended or bought from. That is what monitoring and the full audit exist for.
Check your own brand now
Run the free scan. One click, no signup, and it shows exactly how readable your site is to AI tools today: aizii.ai/aeo-scan
Run the free scanSources
- llms.txt proposal (specific): https://llmstxt.org
Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
