Setting Up llms.txt in Shopify With the llms.txt.liquid Template

What Shopify does now

During spring 2026 Shopify stores began answering at /agents.md, /llms.txt and /llms-full.txt without any action from the merchant. On 28 May 2026 Shopify's developer changelog documented how to customise them. According to Shopify's documentation, the arrangement works like this:

• Every store has a Shopify-managed agents.md, written for AI shopping agents. It describes how an agent can discover, search and buy from the store through Shopify's agent interfaces.
• By default, /llms.txt and /llms-full.txt show that same content. They are alternative addresses for the agents.md file, not a separate llms.txt about your shop.
• A theme can override each path with its own template: templates/agents.md.liquid, templates/llms.txt.liquid and templates/llms-full.txt.liquid.
• If a path has no template of its own, Shopify falls back to the agents.md template, and if there is none, to its own generated default.
• The files are served at the bare primary domain, with no locale or Markets subfolder in the address.

So an llms.txt "missing" finding is now unusual on Shopify. The more common situation is that a file exists but was written for shopping agents rather than as the short, curated guide to your content that the llms.txt proposal describes: a name, a summary, and sections of links with notes.

Should you override the default at all?

This is a real decision, not a formality. The Shopify default is maintained for you and kept in step with Shopify's agent features. The moment you add your own template, Shopify's documentation is clear that you take responsibility for keeping it current.

A good middle path is to override only /llms.txt and leave /agents.md alone. Shopify's agent content then stays managed at its own address, and your llms.txt links to it for agents that need it. Avoid creating agents.md.liquid unless you mean to replace the agent instructions too, because that template also becomes the fallback for the other two paths.

The limits of the template

The llms.txt.liquid template is not an ordinary theme template, and it helps to know its limits before you start writing.

• Only two Liquid objects are available: request and agents. The usual globals such as shop, collections, products, pages and articles are not provided and render blank. You cannot loop over your catalogue to build the list.
• It must be a Liquid template, named exactly llms.txt.liquid. It cannot be a JSON template, and it has no sections or blocks, so it cannot be edited in the theme customiser.
• The content is text or Markdown with Liquid. Anything you type is output as it stands, apart from Liquid tags.
• The agents object gives a handful of store values, including agents.store_name, agents.store_url, agents.currency and agents.sitemap_url, along with the agent endpoints.
• It lives in the theme. Because the template is a theme file, it goes with the theme. If you publish a different theme, the new one will not have your template until you copy it across.

The practical result is that on Shopify llms.txt is written by hand. That suits the proposal well, since a curated list with useful notes is exactly what it asks for, but it means the file will not update itself when you add a collection. Put it on the checklist you use when launching a new range.

The fix, step by step

An example llms.txt.liquid for a small shop

This template is for a fictional leather goods shop. Everything is typed by hand except the shop name and currency, which come from the agents object. URLs are written out in full so the output is predictable whatever form agents.store_url takes.

{%- comment -%}
  Custom llms.txt. Review when collections, policies or delivery terms change.
{%- endcomment -%}
# {{ agents.store_name }}

> Handmade leather belts, wallets and bags from a small workshop in
> Northamptonshire. Online shop only, shipping to the UK and Europe.
> Prices are in {{ agents.currency }} and include VAT for UK orders.

Every item is made to order; dispatch is usually within 10 working days.

## Collections
- [Belts](https://www.example.co.uk/collections/belts): widths, buckle options, how to measure
- [Wallets and card holders](https://www.example.co.uk/collections/wallets): styles, leather colours, personalisation
- [Bags](https://www.example.co.uk/collections/bags): totes and satchels, sizes and strap lengths

## Help
- [Sizing guide](https://www.example.co.uk/pages/belt-sizing): measuring an existing belt or your waist
- [Leather care](https://www.example.co.uk/pages/leather-care): cleaning, conditioning, water marks
- [Delivery](https://www.example.co.uk/policies/shipping-policy): costs and times for the UK and Europe
- [Returns](https://www.example.co.uk/policies/refund-policy): returns window, personalised items, refunds

## About
- [Our workshop](https://www.example.co.uk/pages/about): who makes the goods, materials and tannery sources
- [Contact](https://www.example.co.uk/pages/contact): email, response times, trade enquiries

## Optional
- [Agent instructions](https://www.example.co.uk/agents.md): Shopify's guide for AI shopping agents
- [Journal](https://www.example.co.uk/blogs/journal): workshop news and product stories

Shopify's documentation describes agents.store_url as the bare primary domain. If you would rather build links from it, render the file once and check that there are no doubled or missing slashes before relying on it. Structure rules are covered in the format guide.

llms-full.txt and agents.md on Shopify

By default /llms-full.txt also mirrors agents.md, so after you customise llms.txt the two files will describe different things. You have three options:

1. Leave it. It keeps showing the agent content. That is harmless, though a tool expecting the full text of your key pages will not find it there.
2. Write llms-full.txt.liquid. Because the template has no access to products or pages, any full text has to be pasted in by hand, which only makes sense for a few stable pages such as the sizing guide, care instructions and policies. It then needs updating each time those pages change.
3. Override agents.md. Only do this if you intend to replace Shopify's agent instructions, and understand that it becomes the fallback for both other paths.

For most shops the first option is the sensible one. The llms-full.txt guide explains when a full-text file is worth the effort at all.

Robots.txt still matters more

Shopify generates robots.txt and lets you change it through a robots.txt.liquid template. Whatever your llms.txt says, crawlers that you block there will not read your pages. Check it alongside llms.txt using the robots.txt AI blocks guide.

Shopify Markets, languages and multiple stores

• One file for all markets. The file is served at the bare primary domain without Markets subfolders, so a store selling in several countries or languages has one llms.txt. Say in the summary which markets and languages you serve, and link the main collection page for each language version if you have translated URLs. The language guide covers labelling.
• Separate stores per country. If you run expansion stores, such as a separate EU store, each store has its own theme and its own template. Write one per store, in that store's language.
• Headless storefronts. If your customer-facing site is a custom front end, such as Hydrogen or another framework, on its own domain, what visitors and tools see at that domain is controlled by your front end, not by the theme template. Check which host serves your public pages and put the file there.
• Theme changes. When you switch or update to a new theme, copy llms.txt.liquid into it before publishing, then check /llms.txt straight after the switch.