Shopify agents.md vs llms.txt: What Changed in 2026

Yesterday Shopify shipped a small changelog entry with an outsized implication: /agents.md is now the canonical AI-discovery surface on every Shopify store, and /llms.txt and /llms-full.txt default to mirroring it. The three paths are now customizable independently via three new Liquid theme templates — but the fallback chain reveals where Shopify thinks the agentic-discovery standard is actually consolidating.

For Hydrogen teams, this is a small but useful signal about platform direction. The /llms.txt file Shopify auto-deployed across seven million storefronts in May has effectively been demoted to a pointer. The new primary is /agents.md. Here's what changed, what the customization model looks like, and what Hydrogen storefronts should do about it before Editions Summer.

What the May 28 changelog actually does

The official entry on shopify.dev is short. Three things:

1. Every Shopify store now has a default /agents.md

Accessible at /agents.md on any Shopify-hosted storefront. The path /llms.txt and /llms-full.txt both point to the same content by default. So unless a merchant overrides anything, all three URLs serve identical bytes — the Shopify-generated default agents.md.

2. Three new Liquid theme templates allow per-path customization

Under Online Store > Themes > Edit code, merchants can now add any combination of:

templates/agents.md.liquid — controls /agents.md (and is the default for the other two paths)
templates/llms.txt.liquid — controls /llms.txt only
templates/llms-full.txt.liquid — controls /llms-full.txt only

If a template is present, it serves at its path. If absent, the path falls back through the chain.

3. The fallback chain has an opinion baked in

The fallback order Shopify documented:

The specific template (llms.txt.liquid for /llms.txt, etc.)
The agents.md.liquid template
The Shopify-generated default

That ordering is the most interesting part of the announcement. Shopify is treating agents.md as the canonical authoring surface — the file you maintain when you maintain any of them — and the two llms.txt paths as derivative views that exist for backward compatibility with the older llms.txt standard.

Why /agents.md as canonical is a meaningful platform call

There's been a real format debate in the AI-discovery space all year. Three competing conventions, none with full consensus:

/llms.txt — proposed by Jeremy Howard in late 2024. Lightweight, single-file, designed for "what is this site, what should an LLM know about it." Adopted broadly through 2025; Shopify auto-deployed it across the platform in early May 2026.

/llms-full.txt — same author, longer form, more detailed product/inventory data. Companion to /llms.txt for sites where the short version isn't enough.

/agents.md — emerged in late 2025 as a more agent-oriented evolution. Treated as a Markdown spec describing the site's capabilities, the agent contracts it supports (MCP endpoints, structured-data feeds, supported actions), and operational metadata. More like a robots.txt for agents than a brand bio.

The Shopify decision to make /agents.md the canonical fallback — even for legacy /llms.txt requests — is a quiet endorsement that the platform thinks /agents.md is where the standard is going. The two llms.txt paths still exist, but they're now satellites of the primary.

This also aligns with two earlier Shopify moves this quarter. The April 22 Storefront Catalog MCP UCP rollout made every Shopify storefront agent-readable by default through the Universal Commerce Protocol. The May 7 Web Bot Auth requirement for bots and agents tightened identity expectations at the request layer. The May 28 /agents.md canonicalization is the third move in the same arc: Shopify is consolidating the agentic-discovery surface area into one place it controls, with one canonical file name.

What Hydrogen storefronts should do about this

Hydrogen storefronts don't have an Online Store > Themes > Edit code surface. The three Liquid templates are a Liquid-store feature. But Hydrogen has a more powerful equivalent: every URL is a route, and you own all of them.

The three things worth doing this sprint:

1. Add an /agents.md route to your Hydrogen project

If you haven't already, create the route. In Hydrogen on React Router 7, add app/routes/agents[.]md.tsx (or your project's equivalent file-routing convention) that returns a static Markdown response with the correct Content-Type: text/markdown header. Treat this as the canonical agent-facing description of your store.

The content should answer four questions for any agent that lands on it:

What is this store, in two or three sentences?
What does it sell, in structured form (categories, price ranges, geographies served)?
What MCP or structured endpoints are available (Storefront Catalog MCP URL, JSON-LD product feeds, etc.)?
What's the contact, support, and policy surface (returns, shipping cutoffs, customer-account portal URL)?

Keep it short — a few hundred lines of well-structured Markdown beats a 10,000-line dump that no agent will read.

2. Decide whether /llms.txt and /llms-full.txt should diverge

For most stores, the right answer for the next two quarters is "all three URLs serve the same content as /agents.md." That matches Shopify's default behavior and avoids maintaining three files.

A small minority of stores will want divergence:

/llms.txt as a curated brand-positioning blurb for older AI tools that only read llms.txt
/llms-full.txt as the full agent contract including endpoint URLs and structured data
/agents.md as a clean middle ground

If your store has a heavy AI-traffic profile (large catalog, B2B with named-account routing, region-specific assortments), separation is justified. For everyone else, point all three at the same route handler.

3. Don't add anything Google said it doesn't read

Worth a reminder from this month's Google AI Optimization guide coverage: Google's official guidance is that site owners don't need to create llms.txt files for generative AI search, and empirical server-log audits show zero fetches from ChatGPT-User, GPTBot, or any major AI crawler against these files specifically.

The /agents.md consolidation doesn't change that empirical reality. It changes what Shopify treats as canonical, which matters for the platform's UCP, MCP, and Storefront Catalog tooling — those Shopify systems will increasingly read from /agents.md in their own internal discovery. But the headline AI-shopping channels (ChatGPT, Perplexity, Gemini) still aren't hitting these files in measurable volume.

The honest framing: shipping /agents.md is good hygiene for Shopify-internal agentic systems and the next generation of MCP-aware tooling, but it's not the conversion lever. Don't over-invest. Don't under-invest either.

The Liquid-store side: what merchants will actually see

For completeness on the merchant-facing side: Liquid stores get the three Liquid templates as a real upgrade. Before May 28, customizing /llms.txt on a Liquid store meant editing a theme template that didn't formally exist or hacking around it with metafields. Now there are three named templates with a documented fallback chain, all editable in the standard theme editor.

Hydrogen teams supporting hybrid clients (Liquid main store + Hydrogen mini-site, or Liquid B2B + Hydrogen DTC) should:

Confirm the Liquid side has at least an agents.md.liquid template that matches the Hydrogen side's /agents.md content (or intentionally diverges with documented reasons)
Audit any prior workaround that hand-rolled /llms.txt content into a Liquid template — the new canonical pattern supersedes it
Decide whether brand-level agent metadata (operational policies, MCP endpoints, agent contracts) should be authored once and synced, or maintained independently

For agencies running multiple client storefronts on a mix of Liquid and Hydrogen, this is the right moment to standardize an agents.md template library that ports cleanly between both surfaces.

What it tells you about Shopify's next two quarters

Reading Shopify's last 60 days of changelog entries together, the pattern is consistent: every new release tightens the platform's hold on the agentic-commerce surface. Storefront Catalog MCP went UCP-native. Web Bot Auth gave Shopify a way to rate-limit unidentified bots while letting authenticated agents through. The Agentic Storefronts admin section gave merchants visibility into per-AI-channel performance. Today's /agents.md move makes Shopify the canonical describer of every store on the platform.

Three reasonable predictions for Editions Summer:

A Shopify-blessed agents.md schema. Right now the default is unstructured Markdown. Expect a more opinionated schema — sections, fields, content types — that Shopify-internal systems can parse reliably for UCP and MCP routing. The Liquid template will pre-populate it; Hydrogen teams will need to mirror it manually.

Tighter integration between /agents.md and the Agentic Storefronts admin section. The admin section already shows per-AI-channel rank and recommendations. A reasonable next step is letting merchants edit the canonical /agents.md from the admin UI directly, with previews of how each AI channel will read it.

Per-region and per-buyer /agents.md variants. The current default is one file per storefront. With Shopify Markets and Customer Account routing already supporting region- and buyer-specific behavior, expect the Liquid template to gain context-aware Liquid variables, and expect Hydrogen teams to be expected to mirror that behavior in their route handlers.

The teams shipping serious Hydrogen storefronts this year have been quietly evolving into platform-engineering teams: pinned CLI versions, locked-down CI/CD pipelines, per-app credentials with scheduled rotation, calibrated payment customization Functions, agent-aware cache strategies, and now — by Editions Summer — canonical /agents.md routes with intentional content. Each step is small. Stacked, they're the difference between a storefront that's ready for the next agentic-commerce surface Shopify ships and one that gets retrofitted in panic mode the week of the announcement.

The bottom line

/agents.md is the new canonical AI-discovery file on Shopify. The two /llms.txt paths still exist and still work, but they're now pointers unless you intentionally override them. Liquid stores get a real customization upgrade through three new theme templates. Hydrogen storefronts already had full route ownership — the action item is to make sure you actually shipped an /agents.md route and that the content is current.

This isn't a CRO lever. It's platform hygiene with a clear direction-of-travel signal. The teams that ship the /agents.md route this sprint will be ready for whatever Shopify wires into it at Editions Summer. The teams that ignore it will be the ones answering "why are we serving the default?" questions in August.

If your team runs a Hydrogen storefront and the agent-discovery layer feels like work nobody has time to prioritize, the Weaverse team takes on Hydrogen engagements end-to-end — including agents.md route design, MCP endpoint exposure, structured-data audits, and operational alignment between Liquid and Hydrogen surfaces in hybrid setups. Senior engineers, fast scoping, deep platform fluency on the moving Shopify, Hydrogen, and agentic-commerce release cadence. Talk to us →