Shopify agents.md and llms.txt: what gets auto-generated, and how to override llms.txt

Key takeaways

What to remember

• Treat this as the news/context article, not the full optimization guide.
• Shopify-generated `llms.txt` can include useful agent discovery links.
• A custom `templates/llms.txt.liquid` replaces Shopify output; it does not merge with it.
• Preserve Storefront MCP/UCP/agent discovery links unless there is a reason to remove them.
• Link readers to the optimization guide for templates, examples, and QA steps.

Shopify is introducing machine-readable storefront files: /llms.txt, /agents.md, and /sitemap_agentic_discovery.xml.

These files help AI systems and commerce agents understand a store’s structure and offerings. Shopify generates a default llms.txt that points agents to key sections like search, catalog, sitemap, Universal Commerce Protocol (UCP) discovery, and the Merchant Control Panel (MCP) endpoint. It also includes store details and platform attribution.

A companion /agents.md file provides operational instructions for agents on how to interact with the store, covering discovery, product search, cart/checkout flows, and human approval requirements for payments. The third file, /sitemap_agentic_discovery.xml, acts as a mini sitemap specifically for agent-oriented resources, linking to the other two files.

Shopify’s default llms.txt is intentionally basic, lacking specific details about a store’s highest-margin products, educational content, shipping policies, or trust-building pages. Merchants can override this by creating a templates/llms.txt.liquid file in their theme. This override replaces the default, so it’s crucial to preserve Shopify’s agent/developer links and add merchant-specific discovery links.

Recommended additions to a customized llms.txt include:

• Top category and collection pages
• Buying guides and FAQs
• Policy pages (shipping, refunds, privacy)
• Product-specific explainers (fit, sizing, ingredients, warranties)
• Storefront search syntax
• Canonical URLs for products and collections
• Content addressing common pre-purchase questions

Avoid including discount codes, internal fulfillment rules, private data, or speculative SEO copy. Think of llms.txt as a map guiding agents to accurate public information.

While agents.md is currently Shopify-owned, it reveals their direction: preparing storefronts for agents capable of browsing, comparing, adding to carts, and initiating checkouts. For now, the primary actionable item for merchants is customizing llms.txt.

Most stores don’t need immediate overrides. Focus on ensuring your store has clean product data, stable URLs, useful collection pages, complete policies, structured data, and content that directly answers buyer questions. llms.txt can point to these assets, but it cannot create them.

Shopify adding these files signals the rise of agentic commerce. The best response is not panic or neglect but careful documentation, preservation of agent discovery links, and selective overrides when enhancing accuracy over the default. Flags: …

Frequently asked questions

Is this the optimization guide?

No. This page explains what Shopify is auto-generating and what can go wrong when merchants override it. The optimization guide covers the practical checklist and templates.

Does Shopify merge custom llms.txt content with its generated file?

No. Based on current behavior, adding `templates/llms.txt.liquid` makes the theme own the response, so merchants should preserve useful generated discovery links manually.

Should every Shopify merchant override llms.txt immediately?

No. Merchants should first inspect the generated file, identify what is missing, and only override when they can preserve or improve the useful discovery information.