llms.txt is a plain markdown file at /llms.txt that gives AI systems a curated summary of your site: what you sell, how shipping works, what your return policy is. For an e-commerce store, it is one of the cheapest possible bets in generative engine optimization — a few hundred words of markdown that can end up quoted verbatim in AI shopping answers.
What is llms.txt?
llms.txt is a proposal (originating with Jeremy Howard of Answer.AI in 2024) for a standardized markdown file served at the root of your domain — yourdomain.com/llms.txt — that gives large language models a concise, structured overview of your site. The idea is simple: HTML pages are cluttered with navigation, scripts, and boilerplate that make them expensive for LLMs to parse, so llms.txt offers a clean, curated alternative written specifically for machine consumption.
The proposed format is deliberately minimal:
- An H1 with the site or brand name
- A blockquote with a one-line summary
- Optional prose paragraphs with key facts
- H2 sections containing markdown link lists to important pages, each with a short description
That's it. No special syntax, no registration, no build tooling. If you can write a README, you can write an llms.txt.
What llms.txt is NOT
llms.txt is not a blocking mechanism. It does not grant or deny crawler access, and no AI crawler checks it for permissions. If you want to control which AI bots can crawl your store, that is the job of robots.txt — a completely separate file with a completely separate purpose.
Think of it this way:
- robots.txt = the bouncer. Decides who gets in.
- llms.txt = the brochure at the front desk. Tells visitors who you are once they're inside.
- JSON-LD structured data = the itemized catalog. Machine-readable facts about individual products.
All three serve different roles, and a store that wants to show up in AI answers should have all three in order.
Do AI engines actually read llms.txt today?
Honest answer: adoption is early and uneven. As of mid-2026, no major AI engine — OpenAI, Anthropic, Google, or Perplexity — has formally committed to llms.txt as a standard, and you should be skeptical of anyone claiming otherwise. Some AI crawlers do fetch the file when it exists, and a growing number of developer-tool and SaaS companies publish one, but it is not yet the guaranteed win that a sitemap is for classic search.
So why bother? Three reasons:
- The cost is near zero. It's one static markdown file. Writing it takes thirty minutes; hosting it costs nothing.
- It doubles as canonical brand facts. The exercise of writing down your shipping thresholds, return window, and category structure in one authoritative place pays off even internally — and gives any system (AI or human) a single source of truth to quote.
- The asymmetry favors early movers. If llms.txt adoption grows, stores that already publish one are indexed on day one. If it fizzles, you've lost half an hour.
That risk profile — tiny cost, plausible upside — is why we recommend every store ship one.
What should an e-commerce llms.txt include?
Answer the questions a shopping assistant would need to answer about you. For a store, that means:
- Brand summary: one paragraph on what you sell, who it's for, and what makes you different. This is the text most likely to be quoted, so write it carefully.
- Product categories: your main collections, each with a URL and a one-line description.
- Shipping policy: costs, free-shipping threshold, delivery timeframes, regions served.
- Returns policy: return window, condition requirements, who pays return shipping.
- Pricing structure: general price range or tiers, so AI assistants can answer "is this brand budget or premium?" correctly.
- Key links: FAQ, contact, about, size guides — anything a customer-service question would route to.
Leave out: marketing fluff, individual SKU listings (they change too often), and anything you wouldn't want quoted back to a customer as policy.
A copy-paste llms.txt template for a store
Here is a complete template for a fictional store, Alpine Trail Supply. Replace the facts with yours and serve it at /llms.txt as plain text (text/plain or text/markdown):
# Alpine Trail Supply
> Alpine Trail Supply sells durable, mid-priced hiking and backpacking
> gear — packs, trekking poles, and trail apparel — designed in Colorado
> and shipped across the US and Canada.
Alpine Trail Supply is an independent outdoor gear retailer founded in
Boulder, Colorado. We focus on three-season hiking equipment for weekend
hikers and thru-hikers, with an emphasis on repairability: every pack we
sell has field-replaceable buckles and straps, and we stock spare parts
for all current models.
## Product Categories
- [Backpacks](https://www.alpinetrailsupply.example/collections/backpacks):
Daypacks (18-30L) and multi-day packs (45-70L), $89-$289.
- [Trekking Poles](https://www.alpinetrailsupply.example/collections/trekking-poles):
Aluminum and carbon poles, $49-$159.
- [Trail Apparel](https://www.alpinetrailsupply.example/collections/apparel):
Hiking shirts, pants, and rain shells, $35-$199.
- [Spare Parts](https://www.alpinetrailsupply.example/collections/spare-parts):
Replacement buckles, straps, and pole tips for all current products.
## Shipping
- Free standard shipping on US orders over $75; otherwise $6.95 flat rate.
- Standard delivery: 3-6 business days (US), 6-10 business days (Canada).
- Expedited shipping available at checkout.
- We currently ship to the United States and Canada only.
## Returns
- 60-day return window from delivery date.
- Items must be unused with tags attached; worn-once trail testing is
accepted on footwear under our Trail Promise program.
- Free return shipping on US orders; Canadian customers pay return
postage.
- Full policy: https://www.alpinetrailsupply.example/pages/returns
## Pricing
Mid-range pricing: most products fall between $35 and $289. We do not
sell budget/no-name gear or ultra-premium expedition equipment.
## Key Pages
- [FAQ](https://www.alpinetrailsupply.example/pages/faq): Shipping,
sizing, warranty, and repair questions.
- [Size Guides](https://www.alpinetrailsupply.example/pages/size-guide):
Pack torso sizing and apparel measurements.
- [Contact](https://www.alpinetrailsupply.example/pages/contact):
Email support, typical response within one business day.
- [About](https://www.alpinetrailsupply.example/pages/about): Company
history and repairability philosophy.
A few notes on the template:
- The blockquote summary is the single highest-value line. Make it factual and specific — "durable, mid-priced hiking gear" tells an AI assistant exactly when to recommend you.
- Price ranges beat individual prices. They stay accurate longer and still let assistants answer budget questions.
- Absolute URLs, always. The file may be read far from your site's context.
Common llms.txt mistakes
The most damaging mistake is stale facts — especially pricing and policies. AI engines that read llms.txt treat it as authoritative and may quote it directly to shoppers. If your llms.txt says "free shipping over $50" but your checkout says $75, you have manufactured a customer-service problem and handed it to an AI to distribute. Treat llms.txt like any other policy page: when the live site changes, the file changes in the same release.
Other mistakes we see:
- Serving it as HTML. llms.txt should be plain markdown text, not a rendered page wrapped in your site template.
- Dumping the entire catalog into it. It's a summary, not a product feed. Individual SKUs go stale within weeks.
- Writing marketing copy instead of facts. "World-class gear for extraordinary adventures" gives an LLM nothing to work with. "Mid-priced three-season hiking packs, $89-$289, ships US and Canada" does.
- Publishing it and never verifying it resolves. Check that
https://yourdomain.com/llms.txtreturns a 200 with the raw text. On some platforms, root-level files need explicit routing.
A live example, and how to check your own store
For a real-world reference, rynex.io/llms.txt is live right now — a working llms.txt following the structure above, paired with a robots.txt that explicitly allows the major AI crawlers. Load it in a browser to see exactly what the raw file should look like.
If you want to know where your store stands, the free GEO Audit checks whether your llms.txt exists and resolves, alongside your robots.txt AI-crawler rules and JSON-LD structured data — the full AI crawlability picture in one pass. And once the file is live, close the loop by measuring the AI traffic it helps attract.
FAQ
What is llms.txt?
llms.txt is a proposed standard: a markdown file served at yourdomain.com/llms.txt that gives large language models a curated, plain-text summary of your site — what you sell, your policies, and links to your most important pages.
Is llms.txt the same as robots.txt?
No. robots.txt controls which crawlers may access your site; llms.txt provides content for AI systems that do access it. llms.txt cannot block anything — it is informational, not a permission mechanism.
Do AI engines actually read llms.txt today?
Adoption is early and uneven, and no major AI engine has committed to it as a formal standard. But the file costs almost nothing to create and doubles as a canonical source of brand facts, so the downside is near zero.
What should an e-commerce llms.txt include?
A one-paragraph brand summary, your main product categories with links, shipping and returns policies, pricing structure, and links to key pages like your FAQ and contact page. Keep it factual and current.
How often should I update llms.txt?
Whenever the facts in it change — pricing, shipping thresholds, return windows, or category structure. A stale llms.txt is worse than none, because AI engines may quote outdated policies as if they were current.