Industry Playbooks · · 7 min read · By Mobilize Cloud
An online store's llms.txt should work like a good shop assistant's first answer: here's what we sell, here's how it's organized, here's how shipping and returns work, and here are the products people ask about most. It should not try to list every product. A store with 4,000 SKUs needs a short map, not a catalog.
This guide covers what to include in an llms.txt for ecommerce, what to leave out, a template you can adapt, and the specific things to know on WooCommerce and Shopify. As always with llms.txt: it's a proposal, AI companies haven't said how much they rely on it, and no file guarantees an AI tool will recommend your products. What it does is put your own, accurate description of your store in one easy-to-read place.
Why you shouldn't list every product
The llms.txt proposal describes a short, curated file: a title, a one-line summary, and sections of links to the pages that matter most. A file with thousands of product links works against that idea for a few reasons.
- It buries the important pages. Your returns policy and your best-selling category get lost between product number 812 and 813.
- Products change constantly. Items sell out, get renamed or are retired. Every one of those is a potential broken link in your file.
- There are better channels for product data. Prices, stock and variants belong in structured data on each product page and, for Google, in a Merchant Center feed. Google's guide to sharing product data recommends using both.
Our validator also warns when a file goes over 1 MB, which a full catalog can easily do. If you want a long, detailed version, that's what a separate llms-full.txt is for, and our post on whether you need llms-full.txt explains the trade-offs.
What to include in an ecommerce llms.txt
Think about the questions a shopper might ask an AI assistant about your store: Do they sell this? Do they ship to me? Can I return it? What size should I get? Then list the pages that answer them.
1. A clear title and summary
Your store name as the # title, then a one-line summary in a > blockquote. Say what you sell, who for, and where you ship. "Outdoor clothing and camping gear, shipping across the US and Canada" is far more useful than "Quality products at great prices."
2. Category or collection pages
This is the backbone of the file. List your main categories (WooCommerce product categories, Shopify collections) with a short note on what each contains. Five to fifteen is plenty for most stores. Skip filter combinations, tag pages and sale pages that change every week.
3. Policies
Shipping, returns and exchanges, warranty and payment options are some of the most-asked questions about any store, and the answers change rarely. Link the actual policy pages and add a short note with the key fact, such as "Free US shipping over $75" or "30-day returns, free exchanges". Keep those notes in sync with the pages themselves; a stale note in your llms.txt is worse than no note.
4. Help pages: sizing, care, FAQ and contact
Size guides, fit notes, care instructions, compatibility charts and your FAQ are exactly the kind of reference content AI tools can quote. Add your contact page and, if you have one, a page about your business (who you are, where you're based).
5. A handful of top products
If a few products account for most of your sales or questions, list them: your best sellers, your signature item, or products people search for by name. Keep it short, around 5 to 15, and choose products you expect to stock for a long time. Review this section whenever your range changes.
6. An Optional section
The proposal's ## Optional section is for links an AI tool can skip when it's short on space. Buying guides, your blog, lookbooks and brand stories fit well here.
A template you can adapt
Here's an example for a made-up outdoor store. Replace the names, addresses and notes with your own, and use full https:// addresses.
# Juniper Trail Outfitters > Outdoor clothing, camping gear and trail running shoes. Online store based in Ohio, shipping to the US and Canada. ## Shop by category - [Hiking boots](https://www.example.com/collections/hiking-boots): Men's and women's boots, waterproof and lightweight - [Rain jackets](https://www.example.com/collections/rain-jackets): Waterproof shells and insulated jackets - [Tents](https://www.example.com/collections/tents): 1 to 6 person tents for backpacking and car camping - [Sleeping bags](https://www.example.com/collections/sleeping-bags): Down and synthetic, rated by temperature - [Trail running](https://www.example.com/collections/trail-running): Shoes, vests and accessories ## Best sellers - [Ridgeline Waterproof Boot](https://www.example.com/products/ridgeline-boot): Our most popular hiking boot, wide sizes available - [Cloudbreak Rain Jacket](https://www.example.com/products/cloudbreak-jacket): Packable waterproof shell ## Shipping and returns - [Shipping](https://www.example.com/policies/shipping-policy): Free US shipping over $75, delivery times and Canadian rates - [Returns and exchanges](https://www.example.com/policies/refund-policy): 30-day returns, free exchanges on footwear - [Warranty](https://www.example.com/pages/warranty): How to claim under our two-year gear warranty ## Help - [Boot size guide](https://www.example.com/pages/boot-size-guide): How to measure your feet and choose a size - [Sleeping bag temperature ratings](https://www.example.com/pages/temperature-ratings): What the ratings mean - [FAQ](https://www.example.com/pages/faq): Orders, payment, gift cards and tracking - [Contact](https://www.example.com/pages/contact): Email, phone and support hours ## Optional - [Buying guides](https://www.example.com/blogs/guides): How to choose a tent, a pack or a jacket - [About us](https://www.example.com/pages/about): Our story and where we're based
Our free llms.txt generator can give you a first draft by scanning your site. For a store, treat the draft as a starting point: check it picked your categories and policies rather than a random set of product pages.
WooCommerce: what to check
On WooCommerce, the easiest route is usually your SEO plugin. Yoast SEO, Rank Math and All in One SEO can all generate an llms.txt, and our guide to adding llms.txt to WordPress walks through each. A few store-specific checks:
- See what the plugin picked. Automatic selection may favor recent posts or a sample of products over your category and policy pages. Yoast offers a manual page selection mode, and other plugins let you choose which content types are included. Use those settings so categories and policies make the cut.
- Use your real category addresses. WooCommerce category pages usually live under a base like
/product-category/unless you've changed it in your permalink settings. Copy the address from your browser rather than guessing. - Don't leave the cart and checkout in. Cart, checkout and my-account pages are useless to an AI tool. If they appear in a generated file, remove them.
- One source only. If you upload your own file, turn off the plugin's llms.txt feature so the two don't fight.
Shopify: what to check
Shopify handles llms.txt differently from most platforms. According to Shopify's developer changelog (May 2026), every store has an automatic /agents.md file, and /llms.txt and /llms-full.txt point to that same content by default. It's written for AI shopping agents rather than as a curated guide to your store.
To publish your own version, add a templates/llms.txt.liquid file to your theme (Online Store, Themes, Edit code, then add a new file in the Templates folder). Two details from Shopify's template documentation matter for stores:
- The template has very limited access to store data. Objects like collections aren't available, so in practice you write your links and notes out by hand, as in the template above.
- Shopify's standard addresses make this easy: collections live under
/collections/, products under/products/, pages under/pages/, and the built-in policy pages under/policies/(for example/policies/refund-policy).
Older advice suggested uploading the file and redirecting /llms.txt to it. Shopify's own file takes priority over that, so use the template instead. Some apps also generate llms.txt for Shopify; check what they actually publish at /llms.txt after installing.
Beyond the file: what helps product questions most
llms.txt is the small part. For questions about specific products, the work that matters more is on the product pages themselves:
- Product structured data with price, availability, and shipping and returns details.
- Real product descriptions in the page HTML: materials, dimensions, compatibility and who it's for, not just a manufacturer's one-liner.
- Crawler access. If your robots.txt or firewall blocks AI search crawlers, those tools can't read your pages. OpenAI, for example, says sites that want to appear in ChatGPT search should make sure they aren't blocking OAI-SearchBot. Our free AI readiness check tests this along with structured data and your sitemap.
Keep it working through seasonal changes
Stores change more than most sites. Collections get renamed for a season, policies change before the holidays, a best seller is discontinued. Each one can leave a dead link or an out-of-date note in your file. Put a reminder in your calendar to review llms.txt whenever you change policies or restructure categories, and run it through the validator after each change.
If you'd rather not rely on memory, list your store on LLMs Ledger. Paid plans check the file on a schedule, email you if it breaks, and open every link it contains so you hear about a dead collection page before a customer does.
Bottom line: an ecommerce llms.txt is a map, not a catalog. List your categories, your policies, your help pages and a few long-term best sellers, keep the notes accurate, and put product-level detail in structured data where it belongs.
Is your llms.txt working?
Check any site for free and get plain-English fixes in seconds.
Keep reading
Industry Playbooks
Writing an llms.txt for a local business: a templatellms.txt Guides
Why your llms.txt might be serving a web page instead of a file