How to add llms.txt to your Shopify store

Most guides for this are now wrong. In May 2026 Shopify took over the /llms.txt route platform-wide, so the old tricks — file uploads with redirects, app proxies — stopped working. Here is what actually happens now, the supported way to customize the file, and an honest look at whether it matters.

Last updated August 17, 2026 · Applies to all Shopify plans

What llms.txt is (in one minute)

llms.txt is a proposed standard from Jeremy Howard of Answer.AI, introduced in September 2024. The idea: put a plain-markdown file at your domain root that gives AI language models a curated index of your most important pages — your best collections, policies, and answer pages — so a model doesn't have to wade through navigation, scripts, and pop-ups to understand your store.

It's worth being upfront about its status: llms.txt is a proposal, not a ratified standard. No major AI provider has formally committed to reading it, and Google's John Mueller said in 2025 that no AI system used it at the time. We'll come back to what that means for you at the end — but first, the mechanics, because on Shopify they changed completely this year.

The big 2026 change: Shopify now serves /llms.txt for you

For most of the file's life, Shopify had no native way to serve it — you couldn't upload arbitrary files to your domain root, so merchants leaned on workarounds. That era is over. Per Shopify's developer changelog (May 28, 2026), every store now includes a default agents.md file at /agents.md, and the /llms.txt and /llms-full.txt paths point to that same content by default.

agents.md is Shopify's agent-facing store description: it tells AI agents and shopping assistants what your store sells and how to interact with it, including discovery info for Shopify's commerce endpoints (MCP and the Universal Commerce Protocol). Shopify staff confirmed on the developer forums that the redirect from /llms.txt to /agents.md is intentional — agents.md is now the primary storefront discovery file.

The side effect: merchants who had set up a custom llms.txt through a redirect or an app found it silently overridden. Here's the current state of every method you'll see recommended online:

How to customize llms.txt on Shopify (step by step)

The supported route is a theme template — the same pattern Shopify uses for robots.txt.liquid. Total time: about 10 minutes.

1. Generate your content first

   Write the markdown you want the file to contain, or use our free llms.txt generator — paste your store URL and it drafts a spec-correct file from your public pages. No signup.

2. Open the theme code editor

   In Shopify admin: Online Store → Themes, find your live theme, click … → Edit code.

3. Create the template

   In the templates directory, create a new file named llms.txt.liquid. (Create agents.md.liquid instead if you want one file to control all three paths — see the fallback table below.)

4. Paste your content and save

   Paste the markdown into the template and save. One important quirk: this template runs in a restricted Liquid context — the usual objects like shop and collections aren't available, so write it as plain static markdown rather than Liquid loops.

5. Verify it's live

   Visit yourstore.com/llms.txt in a private browser window. You should see your content instead of Shopify's generated default. Then run our free AI-visibility check to confirm crawlers can see it, along with the rest of your store's AI-readable signals.

Which template controls which URL

Per Shopify's template docs, each path resolves in this order:

Two caveats worth knowing: the template lives in your theme, so if you switch or replace themes you'll need to re-add it — and headless storefronts (Hydrogen or other custom frontends) don't use theme templates, so this method doesn't apply there.

What to put in the file

The llms.txt spec is deliberately simple: an H1 with your store name, a short blockquote summary, then H2 sections listing your key links with one-line descriptions. For a store, that means best-selling collections, shipping and returns policies, and any FAQ or guide pages. A minimal example:

Keep it curated — your 10–30 most useful links, not a full sitemap dump. The generator produces this structure automatically.

Honest question: is this worth doing?

Here's our candid read. The case for: it takes minutes, it can't hurt, and Shopify itself has clearly decided agent-facing discovery files matter — that's why every store now ships one. The case against: there's still no public evidence that the major AI assistants fetch llms.txt when answering shoppers. Google says its systems don't use it, and OpenAI, Anthropic, and Perplexity haven't committed to it either. Anyone telling you llms.txt will transform your AI traffic is selling something.

So: do it, but treat it as the cheapest item on the list — not the list. What demonstrably determines whether ChatGPT, Perplexity, or Google's AI Overviews can find, read, and recommend your store is the boring fundamentals: AI crawlers not being blocked, complete Product and Offer schema, real product descriptions, and answer-shaped content. That's exactly what our free check scores, and what the Hatchloop app for Shopify — launching on the Shopify App Store — is built to fix and keep fixed.