llms.txt on Shopify: What It Is and How to Change It

Published: August 24, 2026

Last updated: August 24, 2026

11 min read

In May 2026, Shopify quietly gave every storefront three new files.

No banner in the admin. No email. Merchants found /llms.txt, /llms-full.txt and /agents.md live on their domains, generated on their behalf, and had to ask in the developer forum what they were.

Most store owners still don't know they're there.

Which means most store owners are currently introducing themselves to AI search through a file they've never read.

And having read a few: the default introduces Shopify's ecosystem beautifully. Your store, less so.

The wider industry is still arguing about whether llms.txt matters at all.

I'll give you my honest position on that argument below, because I've run this experiment on a real store and the answer isn't the one either camp wants.

In this guide, I'll take you through what llms.txt actually is, what Shopify's auto-generated version contains, how to override it properly (there's a gotcha), what to put in yours, and where it fits in the AI search work from my complete Shopify SEO guide.

Platform facts in this guide were verified in August 2026. This corner of search changes monthly, so if you're reading it much later, check the current state before you act on anything dated.

Short on time? Here are the key takeaways

Shopify generates these files for you: llms.txt, llms-full.txt and agents.md are live on your storefront already.
Edit agents.md.liquid, not llms.txt.liquid: Shopify mirrors one into the other, and its own docs advise against a separate file.
Your template replaces the default entirely: copy Shopify's agent links across or you silently delete them.
Google ignores the file: the value is the canonical sentence that writing it forces you to decide.

What llms.txt actually is

Let's define the thing before arguing about it.

'llms.txt' is a plain-text file, written in Markdown, that sits at the root of your domain and gives AI systems a curated map of your site: what this business is, in a sentence, followed by your most important pages with one-line descriptions.

The spec was proposed in late 2024 by Jeremy Howard of Answer.AI, and the format lives at llmstxt.org.

Think of it as the menu you hand an AI at the door, as opposed to the sitemap, which is the full stock room inventory.

The file matters less than what writing it forces you to decide.

The honest bit: does anything read it?

Here's where I'm supposed to tell you this is essential and every day without one costs you customers.

I won't, because the evidence doesn't support it.

Google has now put it in writing. Its guide to optimising for generative AI features states that you don't need to create AI text files to appear in Google Search, "as Google Search itself doesn't use them", and that maintaining one "won't harm (nor help) your visibility or rankings in Google Search".

That's about as flat a no as documentation gets.

The llms.txt project itself reached a version 2 this August and now claims adoption among the major model providers. Treat that the way you'd treat any spec author describing their own uptake: plausible, unaudited, and not the same as a vendor committing to read your file.

Shopify theme specialist Ilana Davis, whose judgement on this platform I rate highly, advises store owners to leave the file alone for now.

That's not a silly position.

So why am I telling you to spend an afternoon on it anyway?

Three reasons.

The cost asymmetry is absurd: one afternoon, once, against a possible seat at the table as AI shopping matures. There is no version of this where you lose meaningfully by doing it.
The default file is working against you today: Shopify's auto-generated version exists whether you engage or not, and it wasn't written to sell your store. That alone changes the question from "should I have one" to "should mine say this".
Writing it forces the canonical-language decision: to fill in the first two lines you must decide, in one sentence, what your store is. That sentence, used consistently everywhere, is the single highest-value asset in AI search. I know because I've watched ChatGPT quote one back word for word.

The file might be ignored. The exercise never is.

What Shopify ships by default (and who it serves)

Pull up yourstore.com/llms.txt and read what the machines are being told.

The auto-generated file points AI agents at your search endpoint, your catalogue, your sitemap, and Shopify's agentic commerce plumbing: the UCP discovery endpoint (Universal Commerce Protocol, the standard that lets AI agents transact) and an MCP endpoint for structured store queries.

Plus store details and platform attribution.

What it doesn't contain: your buying guides. Your bestselling collections. Your delivery promise, your authenticity process, your reason anyone should buy from you rather than the next tab.

It describes Shopify's world with your logo on it.

To be fair to Shopify, the default is built for the agentic future they're racing toward, where a shopping agent discovers your store, queries stock and completes checkout on a buyer's behalf.

The companion /agents.md file is the operating manual for exactly that: discovery, product search, cart flows, human approval steps.

That infrastructure is genuinely useful and you shouldn't remove it.

However, infrastructure isn't persuasion. The persuasion layer is yours to write.

How to override it (and the bit almost every guide gets wrong)

Shopify serves these files natively now, which killed the old workarounds.

The Cloudflare Worker tricks and redirect-app setups you'll find in guides from early 2026 no longer apply.

The current mechanism is a theme template, and here's where most advice goes wrong.

Nearly every guide tells you to create llms.txt.liquid. Shopify's own documentation tells you not to.

The reason is that agents.md is the primary file. Shopify generates /llms.txt by mirroring /agents.md, so the three files are effectively one document served at three addresses. Edit agents.md.liquid and your llms.txt updates with it. Create a separate llms.txt.liquid and you've given yourself two files to keep in sync forever.

So:

Create the right file: in your theme's code editor, add a new file in the Templates folder named agents.md.liquid. The .liquid extension is essential. A plain agents.md file does nothing.
Write your content: plain text or Markdown, and Liquid works if you want dynamic values.
Mind the replacement rule: your template replaces the default entirely. Shopify does not merge them. Copy the default file's agent and developer links into your version before you overwrite, or you'll silently remove the agentic commerce endpoints along with the platform boilerplate.
Check both live: load yourstore.com/agents.md and yourstore.com/llms.txt. Both should now read as your words.

One more thing worth knowing: llms-full.txt is not a longer document. On the stores I've checked it mirrors the same content, so don't spend an afternoon writing an expanded version nobody serves.

Shopify documents all three templates properly, along with a developer changelog from 28 May 2026 when the customisation templates shipped. The developer forum thread is where merchants first pieced the behaviour together, and it's still the best place to watch it evolve.

Two caveats. These are Online Store theme routes, so headless and Hydrogen storefronts don't serve them. And what these files actually do for shopping agents is covered in my guide to ChatGPT product recommendations.

What to put in yours

Curation is the entire point.

Shopify serves the same content at all three addresses, so what you write is the whole introduction.

If everything's important, nothing is.

Mine follow this shape:

The canonical sentence first: one line that says what you are, in the exact words you want repeated. Specific beats clever. "UK golf apparel brand that designs and sells its own hoodies, tees and headwear" gives a machine something to quote. "Elevated essentials for the modern golfer" gives it nothing.
Shop, but curated: your five to ten money collections with one-line descriptions, not all ninety.
Guides that answer buying questions: the content you'd want quoted in an AI answer.
The trust pages: about, delivery, returns, authenticity or guarantees. Agents check these before recommending. So do humans.
Shopify's agent links: preserved from the default, as above.
Consistency with your schema: the canonical sentence here should match your Organization markup, per my Shopify schema markup guide.

The stack that actually got a store cited

Now the part I can back with receipts, and the part that keeps this article honest.

At REHAUS, the pre-owned designer furniture retailer I rebuilt this year, llms.txt went live alongside three other things: a canonical AI information page, Product schema stripped back to a single clean source, and 28 articles written to one rigid, declarative template.

The result: ask ChatGPT for the best second hand designer furniture and REHAUS comes back number one, "Best Overall", above Vinterior, Pamono, 1stDibs and eBay UK.

The answer quotes the site's canonical language almost word for word: a specialist reseller that collects, authenticates, prepares and stores.

Can I isolate llms.txt's contribution to that? No, and I won't pretend otherwise.

What I can tell you is that every piece of the stack repeats the same declarative language, the file is the cheapest piece of it, and the sentence ChatGPT quotes is the one I wrote when building exactly these assets.

The full build sequence is in the REHAUS case study.

If you want the rest of the stack, my guides to AI Overview optimisation and how to rank in ChatGPT cover the citation side, and my AEO readiness score will tell you in two minutes which pieces your store is missing.

Keep it in proportion

A disqualifier, because this article will attract owners looking for a shortcut.

If your collection pages have default metadata and your schema comes from three conflicting apps, llms.txt is not your priority.

It polishes a signal. It can't create one.

Work through the foundations in my 40-point Shopify SEO checklist first, then come back.

The file will still take one afternoon.

And measure this layer the way it deserves: not in GA referral traffic (citations mostly don't click), but with a monthly ritual.

Ask ChatGPT, Perplexity and Google's AI Mode the one question your store should win.

Note who's in the answer. Track whether you are.

Final Thoughts

llms.txt sits in a strange category: unproven, nearly free, and quietly becoming infrastructure while everyone argues about it.

My position is the boring one. Spend the afternoon.

Write the canonical sentence like it'll be quoted back to you, because at REHAUS it was.

Edit agents.md.liquid rather than llms.txt.liquid, preserve Shopify's agent links, curate ten pages that sell your store, and get back to the work that moves rankings this quarter.

Early costs little here. Late costs the answer.

And if you'd rather know exactly where your store stands across the whole AI search layer, that's what my AI visibility audit covers: crawler access, schema, canonical language, and where the assistants currently place you.

Get in touch, or email me directly.

Author Bio

Graeme Whiles is an independent SEO and AEO consultant at GWContent. He has worked with enterprise and SaaS brands, including Originality.ai, Connecteam, 6sense, Practice Better, and Peppr, growing organic traffic and AI search visibility across some of the most competitive categories in B2B. He also built Three Putt Golf Clothing from a blank domain as a live proof of concept for his methodology.

llms.txt on Shopify FAQs

Does Google use llms.txt?

No, and Google now documents it. Its generative AI optimisation guide says you don't need AI text files to appear in Search because Search doesn't use them, and that having one neither harms nor helps your rankings. Treat llms.txt as a low-cost bet on the assistant side of search, never as a Google ranking input.

What's the difference between llms.txt, llms-full.txt and agents.md?

On Shopify, less than the names suggest. agents.md is the primary file, covering how shopping agents should search, add to cart and check out, and Shopify mirrors its content into llms.txt and llms-full.txt. Edit agents.md.liquid and all three update, which is why Shopify advises against creating a separate llms.txt.liquid.

Will llms.txt get my products recommended by ChatGPT?

Not on its own. Recommendations come from the whole stack: clean Product schema, consistent canonical language, declarative content and third-party corroboration. REHAUS earned its number one ChatGPT spot with all of those together. The file is the cheapest component, not the cause.

Do I need an app to add llms.txt to Shopify?

Not anymore. Since May 2026, Shopify serves these files natively, and you override them with an agents.md.liquid template in your theme's Templates folder. Apps and redirect workarounds from before that date are obsolete, and some will now conflict with the native file.