On May 28, 2026, Shopify quietly shipped something that changes how AI shopping assistants and answer engines discover a store's content: native, customizable support for /agents.md, /llms.txt, and /llms-full.txt at the true domain root, on every store, automatically. Most merchants have never heard of this. Here is what it actually is, why it matters, and what changing it looks like in practice.
What these files actually are
Think of it as a curator's note written for a language model instead of a person. Robots.txt tells a crawler what it is allowed to visit. Sitemap.xml lists every page. An agents.md or llms.txt file does something different: a short, plain-text summary of what a site actually is and where the important content lives, written for an AI system to read in one pass rather than for URL discovery. When ChatGPT, Claude, Perplexity, or Google's AI Overviews try to understand a store quickly, this is one of the places they check.
What changed on May 28, 2026
Before this update, getting a working llms.txt onto a Shopify store meant a workaround, a URL redirect or a proxy layer, because Shopify did not let merchants place files at the true domain root. Shopify now serves all three paths natively, with a generic auto-generated default already live on every store even without any customisation. The redirect and proxy workarounds that used to be necessary no longer apply and, in most cases, no longer work.
Customisation happens through three theme templates, added under Online Store > Themes > Edit code:
-
templates/agents.md.liquid, the canonical file. If the other two do not have their own template, they fall back to this one. -
templates/llms.txt.liquid, controls/llms.txtspecifically. -
templates/llms-full.txt.liquid, controls/llms-full.txtspecifically, intended for a longer, more detailed version.
The fallback chain matters: a specific template first, then agents.md, then Shopify's generic default if neither exists. For most stores, customising just agents.md.liquid is enough to control all three paths.
What actually goes in the file
The generic Shopify default is functional but generic, essentially a machine-readable dump of what the store sells. A curated version does more: a short paragraph on what the business actually is, followed by flat, organised link lists, main collections, key guides, contact and policy pages. One technical detail matters more than it sounds: adding {% layout none %} at the very top of the template. Without it, the content renders wrapped in the theme's full HTML, header, footer, navigation and all, which defeats the purpose of a file meant to be read in one pass.
We rebuilt ours along these lines, it is live at digistoresg.com/agents.md if you want to see the actual structure rather than just a description of it.
Does this actually affect anything measurable yet
Honestly, this is still early. Adoption of llms.txt by the AI systems that are supposed to read it is uneven and still rolling out across different providers, so treat this as a foundation being laid rather than a lever with an immediate, measurable payoff. What is measurable already, and does the same underlying job, is structured data: Product, Article, and FAQPage schema markup on your actual pages is what AI answer engines lean on most heavily right now to extract clean, citable facts rather than parsing marketing copy. A curated agents.md is the map; correct schema on the pages themselves is the substance the map points to. Worth having both, but if only one gets done first, the schema is the one with more evidence behind it today.
Where this fits with everything else
This sits alongside the same theme-editing discipline covered in our broader guide on managing a Shopify store with Claude: duplicate the live theme fresh, edit the duplicate, verify, publish manually. A new theme template is no exception to that pattern, and it is exactly the kind of narrow, detail-sensitive change that is easy to get right once and then never revisit as the platform keeps evolving underneath it.
Frequently asked questions
Do I need to do anything, or does Shopify handle this automatically?
Shopify serves a generic default automatically with no setup required. Customising it with a curated summary of your actual business, rather than relying on the generic version, is optional but likely more useful to an AI system trying to understand what your store actually is.
What is the difference between agents.md and llms.txt on Shopify?
They are two paths that, by default, point to the same content. agents.md is the canonical template; if llms.txt or llms-full.txt do not have their own separate template, they fall back to whatever agents.md contains.
Do the old llms.txt redirect or proxy workarounds still work?
No. As of the May 2026 update, Shopify serves these paths natively at the platform level, which superseded the redirect and Cloudflare Worker style workarounds many merchants had set up previously.
Is llms.txt more important than structured data schema?
Not currently. Product, Article, and FAQPage schema on individual pages has more established, measurable impact on how AI answer engines cite a site right now. llms.txt is a useful complement, a high-level map, not a replacement for correct on-page schema.
Will this affect my Google Shopping or Merchant Center listings?
No, these are separate systems. Merchant Center and Shopping listings are driven by your product feed; agents.md and llms.txt are aimed at general AI answer engines reading your site content, a different channel entirely.