How to Add an llms.txt File to Shopify

You can add an llms.txt file to Shopify only if you run a headless storefront. On every standard Shopify plan, the platform will not let you write a file to your web root. So /llms.txt either does not exist on your domain, or it resolves through a redirect to somewhere else.

Why the WordPress instructions don't work here

Most llms.txt guides are written for WordPress. Install a plugin, or drop the file in your root over FTP, and you're done. That works because WordPress gives you filesystem access and a server that hands back whatever you put there.

Shopify gives you neither. You get theme files, a Files area for images and documents, and admin settings. None of them touch the root of your domain. No amount of clever Liquid templating gets around it.

What you can edit on a standard Shopify store

robots.txt is editable, and it is a different file

Shopify generates your robots.txt and lets you append rules for a supported set of user agents. You cannot replace the file or add arbitrary blocks.

That setting still matters for AI crawling, because robots.txt is where you allow or block tokens like ClaudeBot (Anthropic's training crawler) and PerplexityBot. One thing to keep straight: blocking a training crawler does not remove your pages from that operator's AI answers. The indexing agent and the live fetch agent run on separate tokens, and those are the ones that decide whether you show up. We walked through the consequences in Does Blocking AI Crawlers Hurt Your Visibility?.

Pages live under /pages/, not at the root

A Liquid template renders a page at /pages/your-handle. You can put llms.txt content on that page as plain text. The URL will still be /pages/your-handle, and the content type will still be text/html. Close enough to fool nobody.

Shopify Files uses a different hostname

Uploads land on cdn.shopify.com. That is not your domain, so it does not give you yourstore.com/llms.txt. It gives you a CDN path you could point a redirect at.

The routes that exist, and what each one really serves

The redirect row is the one most store owners end up using. It deserves a closer look, because it is not the same thing as hosting the file.

What a Shopify redirect actually does

In the Shopify admin, open Online Store, then Navigation, then URL redirects. Enter /llms.txt as the from path and point it at a page or a Files URL. Save, then test it:

curl -I https://yourstore.com/llms.txt

You get a 301 and a Location header. Follow it and you land on an HTML document with a text/html content type. An agent that follows the redirect reads HTML, not plain text.

Shopify also refuses some from-paths that collide with store routes, so the redirect may simply not save. Test it rather than assuming.

There is no published rule saying AI agents follow a redirect to find an llms.txt file. You are hoping. That hope costs nothing, but it is still a hope.

Hydrogen is the one clean route

Shopify's headless stack, Hydrogen on Oxygen, lets you define your own routes. A route that returns text/plain at /llms.txt is straightforward when you already run Hydrogen. If you are on Hydrogen, do it. It's an hour of work.

If you are on a standard theme, don't replatform for one text file. Going headless to publish a file that a handful of tools read is a bad trade, and your theme is not the bottleneck on AI visibility anyway.

What llms.txt is actually worth

Adoption is partial. No major operator has publicly committed to honouring llms.txt. Neither OpenAI, Anthropic nor Google documents it as a signal their crawlers follow. Several documentation platforms and developer tools do read it.

That makes publishing one a cheap bet, not a ranking lever and not a requirement. Publishing the file is not the same as a crawler fetching it, and only your site's own server sees which of those happened.

What moves the needle more is being present where AI answers pull from, and knowing which agents actually reach you. The two that can send referral traffic are ChatGPT-User (OpenAI's live fetcher) and Claude-SearchBot (Anthropic's search index crawler). Training crawlers bring none. The Small Business Guide to AEO and GEO vs SEO: What's Different and What Still Works both go deeper on that.

How to tell whether anything ever requested it

Shopify does not give you raw server logs, so you cannot watch for a request to /llms.txt directly. Your options are a third-party log service, or a crawler tracker that reports on your storefront traffic.

Kymo classifies AI crawler user agents into ai_answer, indexing and training, and shows which pages they hit. Setup is in the Kymo documentation. If you are comparing tools first, The Best AI Visibility Tools, and What Each One Can't Tell You is a fair starting point, and the Analytics basics section covers the fundamentals if this kind of data is new to you.

Pricing, if you get that far: Solo is $9 a month or $90 a year for up to 10,000 events a month. Studio is $29 a month or $290 a year for up to 100,000 events a month. Every feature is on both plans. Both start with 14 days free, no card required, and AI crawler tracking does not count against your event limit.

Do the redirect if you're on a standard theme. Add the route if you're on Hydrogen.

That is the honest answer for llms txt on Shopify. A standard store cannot host the file at its root, and no app quietly fixes that. The redirect gets the path to resolve. Hydrogen gets you the real file. Everything else is the wrong URL or the wrong hostname.

Run the check on your own store before you touch anything

The free AI visibility check reads your URL from public signals, so your site does not need Kymo installed, and the report arrives by email. It shows what AI assistants already do with your pages. If you would rather watch it continuously, start tracking it and see which engines crawl you day to day.

Start free → 14-day free trial. No card required.