Developer Changelog / Themes

/llms.txt, /llms-full.txt, and /agents.md:
serve them however you like from your theme

Every store comes with a default agents.md that's served at /agents.md , and/llms.txt and /llms-full.txt also point to it by default. By adding a dedicated template to your theme, you can now return different content for each path.

What's on this page
  1. Understand it in 30 seconds: what's now possible
  2. The three paths and their default behavior
  3. How the fallback works
  4. Templates and what each one controls
  5. Setup steps (3 steps)
  6. 5 key points for developers
  7. 3 practical use cases
  8. A one-line summary for your pitch

1Understand it in 30 seconds: what's now possible

Every Shopify store comes with a descriptor file for AI agents, agents.md built in from the start, and /agents.md is where it's served.
Now,under your theme's templates/ directory, placing a dedicated template lets you return different content for each/agents.md / /llms.txt / /llms-full.txt path.

Before: default content only

All three paths simply returned the Shopify-generated agents.md content, with no way to tailor it per store.

Now: customizable per path

In your theme, add a .liquid template to serve custom content per path. Paths without a template fall back to the default.

2The three paths and their default behavior

PATH

/agents.md

A descriptor file for AI agents.By default, its content also serves as the content for the other two paths(the canonical path).

PATH

/llms.txt

An index-style file for LLMs. By default it mirrors agents.md .

PATH

/llms-full.txt

A full-version file for LLMs. By default it mirrors agents.md .

The three paths return the same content by default (agents.md)). Just add a template to the paths you want to serve differently.

3How the fallback works

Request e.g. /llms.txt ① Dedicated template llms.txt.liquid exists? No ② agents.md template exists? No ③ Shopify default auto-generated agents.md If found, resolve and serve here
If a path has no dedicated template → first the agents.md template, and if that's missing too, the Shopify auto-generated default, falling back in that order.

4Templates and what each controls

TemplatePath it controlsNotes
templates/agents.md.liquid /agents.md Base Also serves as the default for the other two paths
templates/llms.txt.liquid /llms.txt only Specific to this path
templates/llms-full.txt.liquid /llms-full.txt only Specific to this path
(no template) The matching path Falls back in order: agents.md template → Shopify default

5Setup steps (3 steps)

1

Open Edit code

Go to Online Store > Themes > Edit code.

2

Add a file under templates

For the path you want to serve differently, .liquid create the template.

3

Write the content and save

Access each path and confirm that the intended content is returned.

The original article doesn't cover details such as the exact template syntax, the variables available in Liquid, or caching behavior. Refer to the updated documentation.

65 key points for engineers

1. Present in every store by default

Every store comes with a default agents.md provided, /agents.md already served at/llms.txt / /llms-full.txt also returns the same content by default.

.liquid

2. Under the hood, it's a Liquid template

Control is handled by the templates/ file under .liquid file. Everything is done by editing the theme's code—no extra apps required.

dedicated default

3. Choose the granularity per path

agents.md.liquid Control all three paths with a single file, or manage each .liquid individually. Place one only on the paths you want to differentiate.

4. Keep the 3-tier fallback in mind

Dedicated template → agents.md template → Shopify default, in that order. Actually access each path to check that the default isn't being served unintentionally.

5. Check the separate documentation for details on syntax, caching, and more

The original article only explains the paths, template names, and fallback order. Check the updated documentation for things like Liquid variable constraints, the delivery format (MIME), and caching and preview behavior, and verify with the real URLs before pushing to production.

73 use cases you can put to work

USE CASE 1

Optimize your store's "instructions" for AI agents and LLMs

Challenge
AI agents and crawlers can only reference the default agents.md so your brand's support contact paths, handling guidelines, and policies aren't conveyed accurately.
Approach
agents.md.liquid Add a single file and rewrite the store description, contact details, and usage guide to your brand's specifications. Covers all three paths at once.
Impact
Reference accuracy via AI improves, and you can centrally manage the content shared across all three paths in a single file.
Technical note
agents.md This template also serves as the default for the other two paths, so setting it up first delivers the best cost-performance.
llms llms-full Differentiation
USE CASE 2

Serve different content for the index version and the full version

Challenge
/llms.txt(a lightweight, table-of-contents-like version) and /llms-full.txt(the detailed full text) should differ in granularity, but by default they end up with identical content.
Approach
llms.txt.liquid a summary index inllms-full.txt.liquid Write the detailed version in it and optimize it per path.
Benefit
Provides granularity suited to the use case, letting you switch between lightweight and detailed references.
Technical notes
If you place a dedicated template on the two paths, agents.md Independent from the default. You can also place just one and leave the rest to the default.
USE CASE 3

An agency rolls out a standard template across multiple stores

Challenge
AI-facing files are maintained inconsistently from one client project to the next, leaving quality and operations dependent on individuals.
Approach
your in-house standard agents.md.liquid(and the llms files too if needed) into the theme, and deploy it for every new build.
Benefit
Standardizes deliverable quality and builds AI readiness into the initial build as a standard step.
Technical notes
It's done entirely with theme code edits, so there's no app dependency. It rides along with theme distribution and duplication.

8A one-line summary you can use in proposals

"/agents.md /llms.txt /llms-full.txt in the theme's .liquid template,can now be served differently per path.
Present by default on every store; no app required; if no template exists, it automatically falls back to agents.md → Shopify default.
Can be built in as a standard step that optimizes the store's "instruction manual" for AI/LLMs to brand specifications."