Shopify llms.txt in 2026: agents.md, Catalog, and MCP
Shopify now publishes agent discovery files on eligible storefronts. Those files describe the store, while Catalog, MCP interfaces, and checkout handle separate parts of product discovery and purchasing.
Last updated:
Shopify now serves agent discovery files natively
Eligible Shopify storefronts no longer need an app or reverse proxy simply to expose the common agent discovery URLs. Shopify serves three related endpoints:
/agents.mdis Shopify's canonical agent discovery URL./llms.txtsupports clients that look for the older convention.-
/llms-full.txtprovides the same default discovery information through another compatible URL.
By default, the endpoints return the same store-level context: the store name and URL, sitemap, policies, and links to other discovery surfaces. Merchants can use Shopify's Liquid templates to customize that content. Native support simplifies publication, but it does not turn any of these files into a ranking control.
What these files do not replace
Discovery files help an agent orient itself around a storefront. Shopify Catalog is separate. It carries structured product facts such as titles, descriptions, images, prices, options, and availability for eligible products.
The distinction is practical. A polished llms.txt cannot correct a stale Catalog price,
while a complete Catalog record does not explain every store policy. Store context, product discovery,
cart state, and checkout are connected parts of the journey, but each has its own interface and evidence.
| Layer | Primary role | What it does not prove |
|---|---|---|
/agents.md | Canonical Shopify agent discovery information | Product inclusion, ranking, or recommendation |
/llms.txt | Compatibility endpoint for clients looking for this convention | Adoption by every client |
/llms-full.txt | Another compatible discovery endpoint | A universal standard requirement |
| Shopify Catalog | Structured, current product data for eligible channels | Appearance in a particular answer or position |
| Catalog MCP | Product search, lookup, and detailed retrieval for agents | Cart mutation or completed checkout |
| UCP Cart MCP | Cart operations through the UCP MCP endpoint | Payment authorization or order completion by itself |
| Merchant checkout | The final purchase flow under merchant policies | Better organic placement |
Shopify says that Catalog inclusion does not guarantee appearance in a particular AI answer, a specific position, or every connected channel. The channel controls the final ranking, wording, and shopping experience.
A practical Shopify validation sequence
-
Request
/agents.md,/llms.txt, and/llms-full.txtfrom the public storefront. - Check the status, content type, canonical purpose, and consistency of store-level facts.
- Open the sitemap and policy URLs referenced in those files.
- Inspect product facts in Shopify Catalog separately from the discovery files.
- Treat Catalog MCP, Cart MCP, and checkout as distinct interfaces with different authorization needs.
- Record what was tested, what appeared in logs, and what remains unmeasurable.
The validator can check the llms.txt syntax, while the
generator can help draft a concise file for a non-Shopify site. For the
wider distinction between discovery guidance, crawler rules, and sitemaps, see the
format comparison.
FAQ
Does Shopify's native llms.txt support guarantee AI visibility?
No. It makes the file available at a predictable URL. Shopify does not present that availability as a guarantee of inclusion, recommendation, or rank.
Can llms.txt replace Shopify Catalog?
No. The file provides store-level orientation and links. Catalog carries structured product facts, including current prices and availability for eligible products.