llms.txt for Shopify: what it is, what it isn't, and how to publish one

llms.txt is a plain-text file at your domain root that tells AI assistants what your store is, what it sells, and which URLs are authoritative for which purpose. It is a convention rather than a ratified standard, it does not rank you, and its real value is removing ambiguity for an assistant that would otherwise infer your catalogue by crawling.

Two claims circulate about llms.txt and both are wrong. The first is that publishing one makes AI assistants recommend you. The second is that it is a fad worth ignoring. The truth is duller and more useful: it is a cheap, low-risk way to state plainly what an assistant would otherwise have to work out, and stating things plainly is most of what AI visibility rewards.

This article covers what the file actually is, what evidence exists for it working, a Shopify-specific template you can adapt, how to publish it on Shopify specifically, and the honest limits.

What the file actually is

llms.txt is a plain-text, Markdown-formatted file served at the root of your domain. Its structure is conventional rather than enforced: an H1 with the site name, a blockquote summarising what the site is, optional prose context, and then H2 sections containing linked lists of the pages that matter, each link followed by a short note explaining what it contains.

The design intent is to give a model a curated entry point instead of a crawl. Rather than fetching two hundred URLs to infer that you sell fragrance-free hair care to people with sensitive scalps, an assistant can read one file that says so and points at the six pages worth reading.

The honest state of support

This is where most articles overstate, so it is worth being precise. llms.txt originated as a community proposal and has been adopted by a growing number of documentation sites and platforms. It is not a ratified standard. No major assistant publishes a commitment to read it, weight it, or treat it as authoritative.

What can be said with confidence: the file is fetched — server logs on sites that publish one show requests for it from AI crawlers. What cannot be said with confidence: exactly how any given assistant uses the contents, or how much it influences whether you are cited.

Which produces a straightforward cost-benefit. Publishing costs perhaps thirty minutes, carries no downside, and makes your positioning unambiguous to anything that reads it. That is a reasonable bet. Paying for a tool whose entire value proposition is generating this file, or expecting it to move a citation rate on its own, is not.

What to put in it, for a store specifically

Most llms.txt guidance is written for documentation sites, where the natural sections are guides and API references. A store has different content and different ambiguities to resolve.

The sections that earn their place in a commerce llms.txt:

• A one-paragraph summary stating what you sell, to whom, and where you ship. This is the single most valuable line in the file — it is the sentence an assistant needs to decide whether you are a candidate at all.
• Categories, each with a canonical collection URL and a sentence describing what is in it and who it suits.
• Policy pages — shipping, returns, warranty — each linked with the actual policy summarised in one line, so an assistant answering "do they ship to the UAE" does not have to parse a page.
• Sizing, materials, care or compatibility guides, if your category has them. These are heavily queried and usually buried.
• Brand facts a shopper asks about: where products are made, certifications you genuinely hold, how long you have been trading.
• An explicit note about what you do not sell, if your name or category is ambiguous. This prevents wrong recommendations, which is as valuable as earning right ones.

What to leave out: every product URL (that is what your sitemap is for), marketing language with no informational content, and anything you would not want quoted verbatim in an answer to a customer.

A template you can adapt

The shape below follows the convention while covering the commerce-specific ground above. Replace the specifics; keep the structure.

# Northwind Hair Co. — fragrance-free hair care for sensitive scalps. Family-run since 2019, shipping across the GCC and to the UK. All products are sulphate-free and dermatologist-tested; we do not sell styling tools or colour products.The header and summary — the highest-value lines in the file

Then the linked sections, each entry being a Markdown link followed by an em dash and one clarifying sentence:

• ## Categories — link each collection with who it is for: "Shampoo — sulphate-free daily and clarifying shampoos for sensitive and eczema-prone scalps."
• ## Buying guides — sizing, ingredient and compatibility pages, with what question each answers.
• ## Policies — "Shipping — free above 150 AED in the UAE, 3–5 days GCC, 7–10 days UK. Returns accepted unopened within 30 days." Put the answer in the sentence, not only behind the link.
• ## About — where products are made, certifications held, how long you have traded.
• ## Not stocked — the ambiguity note: what people assume you sell that you do not.

Publishing it on Shopify

Shopify does not give you filesystem access, which is why the usual "upload a file to your root" instructions do not apply. The route is a theme template.

1. 1

   Check what already exists

   Visit yourstore.com/llms.txt. Some stores serve a platform-generated default. A generic file is better than a 404, but it describes a Shopify store in general terms rather than describing yours — treat it as a placeholder to replace.

2. 2

   Draft the content first, outside the theme

   Write the file in a plain text editor and get the summary line right before touching code. The summary is the part that does the work; the links are supporting material.

3. 3

   Add the template to your theme

   In Online Store → Themes → Edit code, create the template your theme's documentation specifies for serving plain-text at a custom path, and set its content type so it is served as text/plain rather than HTML. Duplicate your theme before editing so you can revert cleanly.

4. 4

   Verify what is actually served

   Load the URL in a private window and confirm two things: the content is your text, and the response is plain text rather than your theme's HTML shell wrapped around it. A file served inside a page layout is not usable.

5. 5

   Keep it current

   An llms.txt describing categories you discontinued is worse than none, because it asserts something false about your catalogue. Tie updating it to whatever process you already use when categories or policies change.

If your theme makes this awkward, the alternative is a reverse proxy rule at your CDN or DNS provider serving the path from elsewhere. That is more infrastructure than the file warrants for most stores — the theme route is fine.

agents.md and where this is heading

A related convention, agents.md, is aimed at agents that act rather than merely read — including the shopping agents that are starting to compare, configure and in some cases transact on a shopper's behalf. Where llms.txt describes content, agents.md leans toward describing capabilities and constraints: what an agent can do here, what it should not attempt, where the authoritative endpoints are.

For a store today, the practical advice is the same: publish both if it is cheap, keep them consistent with each other, and do not build strategy on either. The direction of travel — assistants preferring sites that state their own facts explicitly — is durable even though the specific file conventions may not be.

Frequently asked questions

The verdict

Publish one. It takes half an hour, cannot hurt you, and forces a useful exercise: writing down in one paragraph what you sell and to whom, which many stores have never done in a form a stranger could read.

Then stop thinking about it. The file will not move your citation rate on its own. The things that will — crawler access, product descriptions that answer buyer constraints, and complete structured data — are the same things they were before this convention existed, and they are where the remaining hours should go.