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

Key takeaways

What to remember

• Shopify is testing default `/llms.txt`, `/agents.md`, and `/sitemap_agentic_discovery.xml` endpoints on some stores.
• The generated files are useful but thin: they usually point agents to browse, search, contact, sitemap, UCP, and MCP endpoints.
• A theme file named `templates/llms.txt.liquid` can override Shopify's default `/llms.txt` response.
• Overriding is a replacement, not a merge, so merchants should preserve Shopify's agent/developer section unless they intentionally want to remove it.
• There is still no proven SEO lift from llms.txt, so the safest posture is measured testing rather than urgent rewrites.

Shopify is starting to expose a new set of machine-readable storefront files:

• /llms.txt
• /agents.md
• /sitemap_agentic_discovery.xml

The current behavior is clear enough to plan around: Shopify appears to be testing a native llms.txt file for storefronts, and if a merchant creates templates/llms.txt.liquid in the theme, that file can replace Shopify’s default response.

The more important version: this is not just another SEO text file. Shopify’s default file points AI crawlers and commerce agents toward the store’s search, catalog, sitemap, Universal Commerce Protocol discovery, and MCP endpoint. If you override it casually, you may remove the exact agent-discovery hooks Shopify is experimenting with.

What Shopify is auto-generating

On stores where the test is active, /llms.txt looks like a compact map for AI systems. The default response commonly includes:

• Store name and short description
• Browse links such as /collections/all
• Search pattern such as /search?q={query}
• Store contact and currency information
• A For Agents & Developers section
• Link to /agents.md
• Link to /.well-known/ucp
• Link to /api/ucp/mcp
• Link to /sitemap.xml
• Shopify platform attribution

The companion /agents.md is more operational. It explains how an agent should interact with the store, including discovery, product search, cart or checkout flow, and human-approval expectations around payment.

The third file, /sitemap_agentic_discovery.xml, acts like a mini sitemap for agent-oriented resources. In observed storefronts it points to /llms.txt, /llms-full.txt, and /agents.md.

That matters because an AI system may not begin with your visual storefront. It may first ask: “What files does this merchant expose for agents?” Shopify is testing an answer.

Why the default llms.txt is thin

The generated file is useful, but it is intentionally generic. It does not know your highest-margin collections, your product education pages, your shipping constraints, your support policies, or the pages that best explain why a buyer should trust you.

A stronger merchant-authored llms.txt might point to:

• Top category and collection pages
• Buying guides
• FAQ and policy pages
• Fit, sizing, warranty, or ingredient explainers
• Storefront search syntax
• Best canonical URLs for products and collections
• Content that answers common pre-purchase questions

That does not mean every merchant should rewrite the file today. It means Shopify’s default is a baseline, not a content strategy.

How to override Shopify’s llms.txt

The current override path is theme-based:

1. Open the Shopify theme code editor.
2. Go to the Templates directory.
3. Create a new file named llms.txt.liquid.
4. Add the content you want served at /llms.txt.
5. Save and verify the live /llms.txt URL.

If you work in a theme repository, the file path is usually:

templates/llms.txt.liquid

The important detail is that this is an override. Shopify does not merge your additions into the generated file. Once the template exists, your theme owns the response.

So do not create an empty file. Do not paste a generic AI prompt. Do not remove the agent/developer section unless you understand what you are removing.

A safer override template

If you decide to customize the file, start by preserving the useful Shopify-generated pieces and adding merchant-specific discovery links above them.

# {{ shop.name }}

> Short, factual description of the store and what customers can buy here.

{{ shop.name }} is an online store at {{ shop.url }}, powered by Shopify.

## Recommended pages

- Homepage: {{ shop.url }}
- All products: {{ shop.url }}/collections/all
- Search: {{ shop.url }}/search?q={query}
- Contact: {{ shop.url }}/pages/contact
- Shipping policy: {{ shop.url }}/policies/shipping-policy
- Refund policy: {{ shop.url }}/policies/refund-policy
- Privacy policy: {{ shop.url }}/policies/privacy-policy

## Collections

- Main collection: {{ shop.url }}/collections/all
- Add your most important collection URLs here.

## Buying guidance

- Add links to sizing, fit, compatibility, ingredients, warranty, or FAQ pages.
- Prefer canonical URLs that answer real buyer questions.

## Store information

- Currency: {{ cart.currency.iso_code | default: shop.currency }}
- Contact: add your public support email or contact page

## For Agents & Developers

This store may support agent-oriented commerce discovery through Shopify.

- Agent instructions: {{ shop.url }}/agents.md
- UCP discovery: {{ shop.url }}/.well-known/ucp
- MCP endpoint: {{ shop.url }}/api/ucp/mcp
- Sitemap: {{ shop.url }}/sitemap.xml

## Platform

This store is built on Shopify (https://www.shopify.com).

Treat that as a starting point, not a universal answer. If the store does not expose a page, remove it. If your best buyer education lives somewhere else, link that instead.

What not to put in llms.txt

A good llms.txt should help machines find accurate public information. It should not be a dumping ground for private instructions or speculative SEO copy.

Avoid:

• Discount codes you do not want broadly surfaced
• Internal fulfillment rules
• Private supplier or margin details
• Claims that are not present on public pages
• Long keyword blocks
• Instructions that conflict with policies, product pages, or checkout behavior

Think of the file as a map. If the map points to weak or contradictory content, it does not make the store more understandable.

What about agents.md?

Right now, agents.md appears to be Shopify-owned on stores where the test is active. The content is focused on agent behavior: how to discover commerce capabilities, what endpoints exist, what read-only product routes are available, and why payment should require human approval.

Merchants should read it because it reveals Shopify’s direction: storefronts are being prepared for agents that can browse, compare, cart, and start checkout flows.

But the practical merchant lever today is still llms.txt. That is the file merchants can currently override through the theme.

Should merchants do this now?

For most stores: not urgently.

There is no public proof that llms.txt materially improves AI search visibility. There is also no stable Shopify documentation explaining the final intended merchant workflow. This is early.

The stores that should consider a careful override are the ones where the default file is obviously incomplete for agent discovery: large catalogs, complex buying criteria, important policy pages, or high-value guides that a generic Shopify file will never know to include.

Even then, the right move is conservative:

1. Fetch the current default /llms.txt.
2. Save a copy.
3. Add merchant-specific links.
4. Preserve Shopify’s agent/developer links.
5. Publish the template.
6. Re-fetch /llms.txt and validate every URL.
7. Re-check after Shopify makes future changes.

The real opportunity

The file itself is not the strategy. The strategy is making your store easier for non-human readers to understand.

That means clean product data, stable canonical URLs, useful collection pages, complete policy pages, structured data, and content that answers buyer questions directly. llms.txt can point to those assets, but it cannot invent them.

Shopify adding these files by default is a signal. Agentic commerce is becoming part of the storefront surface area. The safest response is not panic, and it is not ignoring the feature. It is to document what Shopify generated, preserve the agent-discovery pieces, and only override when you can make the file more accurate than the default.

Frequently asked questions

Does Shopify automatically create llms.txt?

Shopify appears to be testing auto-generated llms.txt files on some storefronts. The feature is not yet something merchants should treat as fully documented or stable.

Can I edit Shopify's default llms.txt file?

Yes. Adding a `templates/llms.txt.liquid` file to the active theme can override the default response, but it replaces Shopify's generated content rather than merging with it.

Should Shopify merchants override llms.txt right now?

Only if they have a specific reason and can preserve the useful default agent-discovery links. For most merchants, monitoring Shopify's rollout is safer than rushing a rewrite.

What is agents.md on a Shopify store?

On stores where Shopify's test is active, agents.md describes how AI agents can discover store capabilities, browse products, use UCP/MCP endpoints, and respect checkout rules.