Shopify Already Generates agents.md and llms.txt — Here's What That Means

Short answer first: every Shopify store already serves /agents.md, /llms.txt, and /llms-full.txt, automatically, with no theme edit and no app install. If you're here because you want to "add llms.txt to Shopify," you likely don't need to do anything — Shopify built agent discovery into every store, and for most merchants the default is already the right answer. This guide covers what's generated automatically, how /agents.md and /llms.txt actually differ, when customizing is worth the effort, and what to leave alone. For the underlying format itself — what llms.txt is, its Markdown structure, adoption data — see What is llms.txt.

What Shopify generates automatically

Three files, zero setup, on every store:

• /agents.md — the canonical, agent-facing description of the store. Per Shopify's own documentation, "agents.md is the canonical agent-discovery document. It tells AI agents and shopping assistants how to discover the store's commerce capabilities and how to transact with it" (shopify.dev, agents.md.liquid reference page, accessed 2026-09-01). Shopify's managed default includes the store's Universal Commerce Protocol (UCP) and Model Context Protocol (MCP) endpoints, read-only browsing URLs for product, collection, and search data, and the store's published policies — assembled automatically from the store's own configuration, with no theme maintenance required (same source).
• /llms.txt — described as "an alternate agent-discovery URL that mirrors /agents.md by default" (shopify.dev, llms.txt.liquid reference page, accessed 2026-09-01). Visit it on any live store and, unless someone has added a custom template, you'll see the same content as /agents.md.
• /llms-full.txt — the same mirroring behavior: "By default, /llms-full.txt mirrors the content of /agents.md" (shopify.dev, llms-full.txt.liquid reference page, accessed 2026-09-01).

One deliberate omission is worth calling out: the managed default for /agents.md "deliberately omits contact details because the file is broadly cached and served to every agent that requests it" (same source) — so don't expect to find a support email or phone number in the default output, and don't add one yourself without reading the risk note below.

agents.md vs llms.txt: canonical vs compatibility

The two files aren't redundant copies of the same idea — they play different roles. agents.md is Shopify's own term for the canonical document: it's built around Shopify's UCP/MCP agent-commerce surface, and it's the file Shopify's own systems treat as the source of truth. llms.txt and llms-full.txt exist as alternate URLs largely for compatibility with the wider llms.txt convention that already exists across the web — the format this site's pillar guide covers — so that crawlers and tools built to check /llms.txt specifically still find something useful, even on a platform whose own agent-discovery model is centered on /agents.md.

In practice, that means: change /agents.md and, by default, both mirrors change with it. The only reason to touch /llms.txt or /llms-full.txt separately is if you want one of them to say something different from the canonical file — which is the advanced case covered next.

Do you need to customize anything?

For most merchants: no. The managed defaults are already live, already synchronized with store configuration, and already maintained by Shopify without any theme work. Customizing only makes sense in a few specific cases:

• You want custom agent instructions across the board. Add an agents.md.liquid template in your theme. Since the other two files mirror /agents.md by default, this single template can update all three at once — no need to touch llms.txt.liquid or llms-full.txt.liquid unless you also want one of them to diverge.
• You want /llms.txt specifically to say something different from /agents.md — say, a shorter, curated list distinct from the canonical agent-commerce description. Shopify frames this explicitly as an edge case: "Add an llms.txt.liquid template only when you have an advanced requirement for /llms.txt to diverge from /agents.md" (shopify.dev, accessed 2026-09-01).
• You want /llms-full.txt to carry a longer or more exhaustive version that isn't appropriate for the canonical file. Same logic, separate template: llms-full.txt.liquid.

To add any of these: in Shopify admin, go to Online Store → Themes → [your theme] → Edit code, and in the Templates directory add a file named exactly agents.md.liquid, llms.txt.liquid, or llms-full.txt.liquid — plain text/Markdown with Liquid, never a JSON template. Static Markdown is the bulk of the content; the free llms.txt generator can produce a starting draft to paste in and adapt.

Whichever template you add, own the maintenance going forward: "When you add this template, you hand-edit the Liquid template and take responsibility for keeping its content current" (shopify.dev, accessed 2026-09-01). The managed default updates itself as your store configuration changes; a custom file only updates when you edit it.

What not to change

• Don't add contact details. Shopify's own guidance is explicit: "Avoid outputting potentially private merchant data, such as contact email addresses or phone numbers, in this file" (shopify.dev, agents.md.liquid reference page, accessed 2026-09-01) — these files are broadly cached and served to any agent that asks.
• Don't hardcode UCP/MCP URLs. If you customize agents.md.liquid, "keep the UCP and MCP endpoints discoverable by using the agents object rather than hardcoding URLs" (same source) — hardcoded endpoints break the moment Shopify's agent infrastructure changes underneath them.
• Don't expect a dynamic product/collection loop. All three templates render with a restricted Liquid context: "only the request object and the agents object are available, and the standard global Liquid objects such as shop, articles, and collections are not injected" (shopify.dev, llms.txt.liquid reference page, accessed 2026-09-01). You're writing close to static text — link to canonical product, collection, and page URLs by hand.
• Don't confuse this with crawler permissions. These files describe the store to agents; they don't control who's allowed to crawl it. That's robots.txt.liquid's job, a separate, pre-existing template (help.shopify.com, "Editing robots.txt.liquid," accessed 2026-09-01). Publishing a rich /agents.md doesn't override a robots.txt block on the pages it links to.
• Don't customize all three "just in case." If you only need one file to diverge, template only that one. Customizing agents.md.liquid, llms.txt.liquid, and llms-full.txt.liquid separately when you didn't need to means three hand-maintained files instead of one managed default — more places for the content to go stale.

Verify what your store is actually serving

Don't take any of this on faith — check your own store:

curl -I yourdomain.com/agents.md
curl -I yourdomain.com/llms.txt
curl -I yourdomain.com/llms-full.txt

A 200 on all three confirms Shopify's native support is live, exactly as documented, with no theme work on your part. Then open each in a browser and compare the content: if /llms.txt and /llms-full.txt read identically to /agents.md, you're on the managed defaults. If one reads differently, a custom template already exists somewhere in the theme — worth knowing before you assume you're starting from a blank slate.

Honest limits

Shopify's native support solves the "does this file exist" problem completely, for free, on every store. It doesn't solve a different problem: whether AI engines actually read /agents.md or /llms.txt and change their answers because of it. No AI vendor — not OpenAI, Anthropic, Google, or Perplexity — has published confirmation that its crawlers fetch these files or weight them in what gets cited. llms.txt itself is a community convention, not a web standard any browser or search engine is obligated to honor; see What is llms.txt for the adoption picture across the wider web. Shopify shipping the file natively is a real, verifiable engineering fact. Whether it moves citations is not yet a fact anyone can verify — treat it as free insurance, not a growth lever.

Check your Shopify store's AI visibility

Whether you're relying on the managed defaults or a custom template, a GEO audit checks what's actually being served at /agents.md, /llms.txt, and /llms-full.txt today — plus robots.txt access across AI crawlers, structured data, and content signals — on any live URL, Shopify included, with no theme access required.

Run a free AI SEO audit · Want to draft custom content before you template it? Use the free llms.txt generator to build a starting Markdown draft, then paste it into whichever .liquid template you actually need.

Doing this on WordPress instead? See the llms.txt for WordPress guide.