For an online store, llms.txt works best as a short map: your main categories, your policy pages, your size and buying guides, and your sitemap. Leave out individual product pages, checkout, cart, account and login URLs. The file is for navigation and context, not for listing inventory or transactional flows.
Nobody can promise that any AI engine reads the file or that it changes what gets cited. Treat it as a cheap, low-risk summary of your site, and keep it accurate.
What llms.txt is for, and what it is not
Cloudflare describes llms.txt as a directory of documentation products grouped by category, and llms-full.txt as the full contents, intended for offline indexing, bulk vectorization, or large-context models [4]. Vercel describes the same split: llms.txt sits at a well-known path and links to documentation, while llms-full.txt returns the complete documentation in one plain-text response [5].
Both descriptions point the same way. llms.txt is a directory, not a data dump. For a store, that means grouping and linking, not enumerating every SKU. If you want to know how the two files differ in the spec, see llms-full.txt vs llms.txt. For the basics of the format, see What Is llms.txt.
What to put in a store's llms.txt
1. A one-paragraph description of the store
State what you sell, who for, and where you ship. Plain facts. This becomes the blockquote summary under the title.
2. Categories, not products
Link to category and collection pages. A store with 4,000 products usually has 10 to 40 categories that explain what the store is. Each category page already links to its products, so the map stays short and stays correct as inventory changes.
Include an individual product only when it is a stable, defining item: a flagship product, a gift card page, a custom-order page. Anything that goes out of stock or gets renamed seasonally should not be in a hand-maintained file.
Product data has a better home. Shopify says its Catalog is the authoritative product data feed for agentic channels, and that its agent discovery files do not replace Catalog capabilities [1]. On any platform, product feeds and product schema carry item-level detail. llms.txt does not need to.
3. Shipping and returns pages
These are the pages a shopper (or an assistant answering for one) most needs before buying: delivery times, costs, regions, return windows, refund conditions. Link them directly with a description that states what is on the page.
On Shopify, the shipping policy link appears on product pages and in the cart, while the return policy link appears in the checkout footer and the order review page [2]. Those policies live at their own URLs, so link the policy pages themselves, not the checkout screens that surface them.
4. Size guides and buying guides
Size charts, fit guides, material and care pages, compatibility charts, and "how to choose" pages answer pre-purchase questions in text and tables. They are good candidates because they are stable, factual and specific to your store. Link each one by name, such as "Men's size guide: chest, waist and inseam measurements in inches and cm."
5. Company and support pages
About, contact, warranty, FAQ, and any page that states who runs the store and how to reach them. Add your sitemap URL as well. For sitemap basics, see the XML sitemap guide.
What to leave out
| Leave out | Why |
|---|---|
| Checkout URLs | Checkout is where customers enter shipping information and payment details and place an order [3]. It is a transactional flow, not a page that explains anything. |
| Cart | Per-session and empty for any crawler. |
| Account, login, order history, wishlist | Private or session-bound pages. Nothing useful for a public summary. |
| Search result and filter URLs | Endless parameter combinations that duplicate category content. |
| Every product URL | Goes stale, bloats the file, and duplicates what category pages and feeds already cover. |
| Discount-code and tracking URLs | Temporary and user-specific. |
| Thin or duplicate pages | Tag archives, empty collections, test pages. |
One caution: llms.txt is not an access control. Listing a URL does not grant anything, and omitting one does not hide it. If a page must not be fetched, use real access controls. See robots.txt is not a privacy control.
An example for a small store
The first line is the H1 with the store name: # Northwind Outfitters. The rest of the file:
> Northwind Outfitters sells hiking and camping gear for adults, shipped from the US to the US and Canada. Prices in USD.
## Categories
- [Tents](https://example.com/collections/tents): Backpacking and family tents, 1 to 6 person
- [Sleeping bags](https://example.com/collections/sleeping-bags): Down and synthetic bags with temperature ratings
- [Footwear](https://example.com/collections/footwear): Boots and trail shoes, men's and women's
## Policies
- [Shipping policy](https://example.com/policies/shipping-policy): Delivery times, costs and regions
- [Return policy](https://example.com/policies/refund-policy): 30-day return window and refund conditions
## Guides
- [Footwear size guide](https://example.com/pages/size-guide): Size charts in US, EU and cm
- [How to choose a sleeping bag](https://example.com/pages/sleeping-bag-guide): Temperature ratings explained
## Company
- [About](https://example.com/pages/about): Who we are
- [Contact and support](https://example.com/pages/contact): Email and hours
- [Sitemap](https://example.com/sitemap.xml): Full URL list
The return window and regions above are placeholders. Write only what your own pages actually say. A summary that contradicts the linked page is worse than no file.
Platform notes
Shopify
Shopify says /agents.md is its canonical agent discovery URL, and /llms.txt and /llms-full.txt are compatibility URLs that can serve the same information [1]. By default, that content includes the store name, store URL, sitemap link, store policies, and discovery endpoints for other types of store information [1].
So on Shopify, check what /llms.txt already serves before writing anything. The default may cover policies and the sitemap. If you want to change it, Shopify says you can add an llms.txt.liquid theme template, and a URL-specific template overrides a shared agents.md.liquid template for that path [1]. That is where you would add your categories and size guides.
Open yourstore.com/llms.txt in a browser first. If the default already lists your policies and sitemap, your work is adding categories and guides, not starting over.
Other platforms
The notes cover only Shopify, so check your own platform's documentation for specifics. In general, the file must be served at /llms.txt on your domain root as plain text or Markdown. Where you control the web root, upload it. On hosted platforms without file access, you may need a plugin, a route or a redirect rule. Whichever you use, request the URL and confirm it returns a 200 and the content you expect.
Keeping it maintained
- Use category-level links so the file rarely needs editing.
- Review it when you change policies, add a category, or move a page.
- Test every link after a theme or platform migration. Policy URLs often change.
- Keep descriptions factual. No sales copy.
To draft a first version from your live homepage and sitemap, use the free llms.txt generator, then cut it down to the sections above. For a full walkthrough of the format, see How to Write an llms.txt File.
What to do next
- Open
/llms.txton your store and see what it serves now. - List your categories, policy pages, size guides and buying guides.
- Remove checkout, cart, account, search and filter URLs from any draft.
- Check that every description matches what the linked page says.
- Publish, request the URL, and confirm it returns a 200.