Shopify llms.txt is no longer a file you upload. Since May 2026, Shopify Online Stores have served a default /agents.md file, and the /llms.txt and /llms-full.txt URLs mirror it unless your theme says otherwise. That default is the same set of agent instructions on millions of stores. It tells an AI system how to shop at your store and says nothing about what you sell. This guide covers how to check what your store serves, which template to edit, what the Liquid context won't let you do, and what changes for UK stores selling through Shopify Markets.

What Shopify serves at /llms.txt by default

/agents.md is the canonical file and /llms.txt mirrors it

Shopify's developer documentation describes /agents.md as the canonical, agent-facing description of a store. It points AI agents and shopping assistants to the store's Universal Commerce Protocol (UCP) and Model Context Protocol (MCP) endpoints, lists read-only URLs for product, collection and search data, and links the published policies. The /llms.txt and /llms-full.txt URLs are alternates that mirror that content by default.

Shopify's advice for most stores is to leave the managed file alone, which is why no theme ships with an llms.txt.liquid template.

What the default file actually says

The files served at kyliecosmetics.com/llms.txt and stevemadden.com/llms.txt on 27 October 2026 show the default in practice. Both read as shopping rules for agents. They send an agent to the Shop skill or the store's UCP and MCP endpoints, require the buyer's authorisation before an order is placed, ask agent traffic to identify itself, tell agents to back off when a request returns a 429, and point to the sitemap for public pages. Both link to the store's privacy, terms, refund and shipping policies, and both finish with Shopify developer resources. Neither reads as a description of the brand.

A forum measurement of 20 large storefronts on 14 September 2026 found the same pattern: route templates for fetching products, and no products. Stellar AEO Labs reaches the same conclusion in its guide to customising the default files, pointing out that the default says nothing about hero products or positioning.

Why headless storefronts can return a 404

The Online Store renderer produces these files, and a headless storefront built on Hydrogen and Oxygen doesn't run it. On those stores /llms.txt can return a 404 until a developer builds the route. In the same forum measurement, three of the 20 stores returned no file, and all three were headless. The sample was large brands only, so treat it as an illustration. A 404 on a headless store is a build task. Shopify hasn't withdrawn anything.

What changed in 2026

A misleading thread title muddied this story, so here are the dates in order.

• Early May 2026: merchants began reporting that /llms.txt returned Shopify's own content and that redirects to a hosted file had stopped working.
• 24 May 2026: a Shopify Community thread titled "Shopify just killed /llms.txt for all stores" appeared, describing a redirect to /agents.md.
• 28 May 2026: Shopify's developer changelog documented three theme templates and a fallback order.
• 14 September 2026: a poster in the same thread tested 25 well-known storefronts and reported that /llms.txt returns HTTP 200 as markdown, with no redirect. Of the 20 stores that could be measured, 17 served a file.

The September test is the one to trust. The file isn't dead. It's mirrored, and anyone with theme access can override it.

How to check what your store serves

Run these on your primary domain, not a locale or Markets path.

1. Open yourstore.com/llms.txt and confirm it loads with an HTTP 200, not a redirect.
2. Check the response headers with curl -I https://yourstore.com/llms.txt. The September test saw a markdown content type on stores serving the default.
3. If you do get a redirect, request /robots.txt on the same host. If that redirects too, the host has moved (www to apex, or the reverse), not the path. Test the canonical host instead.
4. Compare the file with yourstore.com/agents.md. On an unmodified store the same test found the two differ by a single line, the one naming which path was requested.
5. If /llms.txt returns a 404, check whether the storefront is headless.

Which template should you edit

Shopify looks for a theme template in a fixed order and uses the first one it finds.

‍

Add only agents.md.liquid and it serves all three URLs. Add llms.txt.liquid and it overrides /llms.txt alone, leaving /agents.md and /llms-full.txt on the default. Many how-to guides, and the AI Overview Google shows for this query, tell you to create llms.txt.liquid first. That works, but it changes one URL and nothing else.

Replacing agents.md.liquid replaces the managed file entirely, so anything in the default that you still want has to be written back in. If all you want is a brand summary at /llms.txt, I'd use llms.txt.liquid: it leaves Shopify's managed agent instructions untouched and gives you less to keep current.

To add a template, go to Online Store, then Themes, then Edit code. Right-click the Templates folder, choose New file and name it exactly. It can't be a JSON template, and once it exists you own the content. Shopify's own advice in the llms.txt.liquid documentation is that most stores shouldn't add one.

What llms.txt.liquid can and cannot use

Liquid objects that render blank

These templates render with a restricted Liquid context. Only the request object and the agents object are available. The shop, collections, articles, blogs, pages and linklists objects aren't injected, so they print nothing. Shopify restricts the context because the file is cached broadly and served to every agent that asks for it.

In practice, {{ shop.name }} renders as an empty string. Tante-E's guide describes the files as dynamically populated with store data, but that only holds for the agents object. Everything else you hardcode.

Using the agents object instead

The agents object is filled in automatically. It gives you the store name, the store URL, the UCP discovery URL, the MCP endpoint URL, the supported UCP versions, the primary currency code and the sitemap URL. Shopify recommends using it for the UCP and MCP endpoints rather than typing them in, so the values stay correct if the store's commerce configuration changes.

A brand-led llms.txt.liquid looks like this, with square brackets marking what you fill in:

# {{ agents.store_name }}

> [One sentence on what the store sells, who it is for and where it ships.]

## Priority collections

- [Collection name]: [full URL]. [One factual line about the range.]

## Policies

- Shipping: [full URL]

- Returns: [full URL]

## For agents

- Store: {{ agents.store_url }}

- UCP discovery: {{ agents.ucp_discovery_url }}

- MCP endpoint: {{ agents.mcp_endpoint_url }}

- Sitemap: {{ agents.sitemap_url }}

Keep contact email addresses and phone numbers out of it. Shopify's generated file leaves them out on purpose, because the file is broadly cached and served to every agent.

Shopify Markets and UK stores

The file is served at the bare primary domain, with no locale or Markets subfolder prefix, and it has no localised counterpart. A UK store selling into the EU and US through Shopify Markets gets one file, in one language, at one URL.

Two things follow. The agents.currency value is the store's primary currency code, so if you sell in local currencies through Markets, a line saying prices are in GBP will be wrong for some shoppers. Leave pricing out and let the product pages and structured data carry it. Shipping and returns terms that differ by market need writing out as plain text for each region you sell to, with links to the policy pages that apply. Write the summary in UK English, since it speaks for the primary domain.

What to put in a curated file

Curated beats complete. A file that lists every product and blog post buries the pages you most want an AI system to find, and because the shop and collections objects render blank, every URL you add is a hardcoded value that will go stale.

A sensible file starts with a plain description of the business, then lists the main collections and a handful of hero products with full URLs. Add any buying guides that answer real customer questions, and link to shipping and returns. Leave out prices and stock levels. They change daily and belong in your product pages, structured data and feeds. Whatever the file says should match what the product pages say. Put a review date in your calendar, because a hardcoded file nobody revisits turns into the least accurate page on the site.

Does llms.txt change AI visibility?

On the evidence so far, not much.

Ahrefs analysed 137,210 domains that received traffic in May 2026 and found that 28% publish an llms.txt file. 97% of those files received no requests that month. Among the 3% that were fetched at all, AI retrieval bots made 1.1% of the requests, and Ahrefs concluded the cons outweigh the pros for AI search visibility right now. It also points out that its customers skew technical, and that a fetch doesn't prove a bot acted on the file.

Google Search and Chrome treat the file differently. According to Search Engine Journal, Google's AI optimisation guide lists llms.txt among the things AI Overviews and AI Mode don't need, and John Mueller and Gary Illyes have been reported saying Google doesn't use it. Chrome's Lighthouse, meanwhile, added an experimental agentic browsing category that includes an llms.txt audit, which checks for a machine-readable summary at the domain root. That category has no weighted score and sits outside the SEO audits. It measures how readable a site is to browser agents, not how it ranks.

On the Shopify side, EVDEV audited 3,703 live stores in October 2026 and found 95.1% serving the default file, 4.3% with a customised one and 0.5% with none. The same audit found only 3.7% of best-seller product pages carried the full set of structured product details it checked for. EVDEV says its sample isn't random, so read those figures as a rough guide.

The file costs almost nothing to edit, and the evidence for a payoff is thin. I'd spend the first afternoon on product schema and crawlable pages instead. SearchUp's guide to structured data on ecommerce websites covers the schema, and the piece on how Shopify stores show up in ChatGPT and Google AI Overviews covers the rest. The Shopify SEO checklist for UK stores sets out the order. Customising llms.txt comes after that.

Frequently Asked Questions

Does my Shopify store already have an llms.txt file?

Yes, if it runs on the Online Store. Shopify serves a default /agents.md, and the /llms.txt and /llms-full.txt URLs mirror it unless your theme overrides them. Headless Hydrogen or Oxygen storefronts differ, because the file may return a 404 until you build the route yourself.

How do I customise llms.txt on Shopify?

Go to Online Store, Themes, Edit code, then add a file under templates. Use agents.md.liquid to change /agents.md, /llms.txt and /llms-full.txt together, or llms.txt.liquid to change /llms.txt only. Shopify falls back from the specific template to agents.md.liquid, then to its generated default.

Can I use shop or collections objects in llms.txt.liquid?

No. These templates render with a restricted Liquid context, so only the request object and the agents object are available. The shop, collections and articles objects render blank. Hardcode the brand details and URLs you want, and use the agents object for the store name, sitemap and agent endpoints.

Does llms.txt work with Shopify Markets?

The file is served at the bare primary domain, with no locale or Markets subfolder prefix, and it has no localised version. A store selling in several markets gets one file. Write it for the primary domain, and link to market-specific policy pages where the terms differ.

Will llms.txt improve my AI visibility?

Not on its own. Ahrefs found 97% of llms.txt files in its May 2026 sample received no requests, and Google says its AI search features don't need one. Treat the file as a cheap signpost. Complete product pages, structured data and third-party mentions do more of the work.

Do I need an app to create an llms.txt file on Shopify?

No. The default already exists, and a custom version is a theme template containing text. Apps that generate or inject the file also exist, so check what each one changes in your theme before installing. Whichever route you use, confirm the result by opening the URL.

If you want to know how your own store reads to AI systems, our free AI visibility tool checks crawler access, schema and AI channel configuration in one pass, and our Shopify SEO services cover whatever it finds.