Every Shopify store now serves a file at /agents.md, and by default the same content answers at /llms.txt and /llms-full.txt. You did not write it, and for most stores it is fine as far as it goes: it tells an AI agent where your commerce endpoints are. What it does not carry is the merchant-specific facts an agent needs before it commits a shopper’s money: your return window, your cancellation rule, your free-shipping threshold. Below is what Shopify’s docs say the file does, what a live default contains, and what to add. All sources were read on November 19, 2026.

What Shopify’s default agents.md contains

Shopify’s agents.md.liquid documentation calls the file “the canonical, agent-facing description of a store” and lists what it covers:

  • the store’s UCP discovery and MCP endpoints;
  • read-only browsing URLs for products, collections and search;
  • the store’s published policies;
  • guidance for personal shopping agents, such as the Shop skill.

Allbirds’ live /agents.md shows what that looks like in practice. It points agents to /.well-known/ucp and /api/ucp/mcp and describes the WebMCP tools on its checkout page. It also says agents must place orders “only with the buyer’s authorization” and must use Web Bot Auth when they run server-side or in a hosted browser. Its policy section is four links: privacy, terms, refund and shipping. It does not state a single number a shopper would ask about. Its /llms.txt is the same document with one line changed to say it mirrors /agents.md.

Shopify also says the generated file “deliberately omits contact details” because it is cached broadly and served to every agent.

How many merchants edit it: 5 of 122

Search Engine Journal published an audit of 122 top Shopify storefronts by Bill Hunt on October 14, 2026, probed in August and September. On this file:

  • 89 of 122 stores served an /agents.md;
  • 83 of those 89 were near-identical copies of one Shopify-generated template;
  • only five stores in the whole sample had written their own.

Hunt’s conclusion: counting agents.md adoption measures “Shopify’s rollout schedule”, not merchant readiness. The same audit found that 70% of stores whose policy text it could read stated a return window in prose, but only 7% of product pages exposed it as structured merchantReturnDays. Across nine checks for completing a purchase decision, none of the 122 stores passed them all.

How the override works

Per Shopify’s May 28, 2026 changelog and the template docs, you add a theme template under Online Store > Themes > Edit code > Templates:

URL Lookup order
/agents.md agents.md.liquid β†’ Shopify default
/llms.txt llms.txt.liquid β†’ agents.md.liquid β†’ Shopify default
/llms-full.txt llms-full.txt.liquid β†’ agents.md.liquid β†’ Shopify default

Three constraints are worth knowing before you start:

  • It replaces, it does not merge. Once you add agents.md.liquid, you own the whole file and must keep it current. Shopify recommends the managed default “unless you need custom agent instructions.”
  • Restricted Liquid. Only request and an agents object are available. shop, collections, pages and other globals render blank, so store facts have to be hardcoded.
  • Keep the endpoints dynamic. Use agents.ucp_discovery_url, agents.mcp_endpoint_url and agents.ucp_versions rather than pasting URLs, so discovery stays in sync when Shopify changes its setup.

Do not confuse it with the theme-root AGENTS.md. Shopify’s AGENTS.md page says that file instructs coding agents such as Sidekick on how your theme is built and “isn’t served on the storefront.”

What to add

Hunt’s audit recommends replacing or extending the default with “your actual return window, cancellation rule, shipping threshold, and pickup options.” As a checklist:

  1. Copy the structure of your current /agents.md so you keep the UCP, MCP, WebMCP and buyer-authorization sections. Swap the hardcoded endpoint URLs for the agents variables.
  2. Add a short Store facts section with numbers, not prose: return window in days, final-sale categories, return shipping fee, cancellation window, free-shipping threshold, and typical dispatch time.
  3. Leave out emails and phone numbers. The file is cached and public.
  4. Put the same values in product structured data (MerchantReturnPolicy, OfferShippingDetails), so an agent reading a product page gets the same answer. The fields are covered in our machine-readable product data guide.

For the rest of the Shopify-specific settings an agent depends on, see Is my Shopify store ready for AI agents?

FAQ

Does every Shopify store have an agents.md file?

Shopify says it manages an agents.md file by default for every store, served at the bare primary domain with no locale or Markets prefix. By default the same content also answers at /llms.txt and /llms-full.txt. In Search Engine Journal’s sample of 122 top Shopify stores, probed in August and September 2026, 89 served one.

Will editing agents.md.liquid break my llms.txt?

Adding an agents.md.liquid template replaces the default content at /agents.md, and also at /llms.txt and /llms-full.txt unless you add a dedicated llms.txt.liquid or llms-full.txt.liquid template. Shopify checks the path-specific template first, then agents.md.liquid, then its own generated default.

What should a Shopify merchant add to agents.md?

Keep the UCP and MCP discovery lines by using the template’s agents object, then add the facts a buyer asks before purchasing. These include the return window in days, the cancellation rule, return shipping fees, the free-shipping threshold and pickup options. Shopify warns against including contact details, because the file is cached and served to every agent.

Sources

A file that tells an agent where to buy is discovery. The return window it reads before buying is the transaction, and that part is still yours to write.