llms.txt for Shopify: what it does and how to add one

The short answer

llms.txt is a markdown agent-discovery file. Jeremy Howard published the original proposal on 3 September 2024; the current v2 was modified on 10 August 2026 (llmstxt.org, The /llms.txt file, v2, read 10 September 2026). Shopify already serves /llms.txt for every store by mirroring its canonical /agents.md document, a change it announced in its developer changelog on 28 May 2026. Shopify says that managed file is enough for most stores (Shopify, llms.txt.liquid, read 10 September and again 25 September 2026). Open yours and verify it. Customize it only when you can name what the managed document is missing and who will maintain the replacement.

Publishing a custom file will not make an assistant recommend you. No search or AI vendor has documented llms.txt as a ranking or citation signal. The pages behind the discovery file still do the substantive work.

What the proposal actually says

The v2 proposal allows an llms.txt file at the site root or at a subpath such as /docs/llms.txt; a subpath file covers the pages beneath that path. Shopify's theme route is the root /llms.txt. The proposal specifies the file's shape:

• an H1 with the project or site name, which is the only required section
• a blockquote with a brief summary carrying the key information
• zero or more markdown sections with detail
• zero or more H2 sections holding file lists: markdown links, each with an optional note

There is one convention worth knowing. An H2 named Optional holds secondary material that an agent can skip when it needs shorter context (llmstxt.org, The /llms.txt file, v2, read 10 September 2026). V2 also recommends clean markdown versions of linked pages and standard alternate and describedby link relations. Those are proposal features, not Shopify requirements, and Shopify does not create markdown copies of every storefront page for you.

The proposal does not mention llms-full.txt. Shopify nevertheless serves /llms-full.txt as an alternate URL for /agents.md and supports a dedicated template for advanced cases.

What llms.txt does not do

It does not get you indexed. It does not get you cited. It is not a ranking signal at any engine that has said anything on the record.

Google is explicit about the class of file: "You don't need to create new machine readable files, AI text files, or markup to appear in these features. There's also no special schema.org structured data that you need to add" (Google, AI features and your website, read 9 September 2026). The same page says a page only has to be indexed and eligible to be shown with a snippet.

Two independent studies point the same way. SE Ranking examined roughly 300,000 domains and found no relationship between having an llms.txt file and how often a domain is cited in major LLM answers (Search Engine Journal, LLMs.txt shows no clear effect on AI citations, read 23 September 2026). Ahrefs found that 28% of 137,000 domains in its web analytics publish the file, and that 97% of the roughly 38,000 domains with a valid one received zero requests for it in May 2026 (Ahrefs, What is llms.txt, read 23 September 2026). Neither study proves the file can never matter. Both say it is not what decides citations today.

The assistants say so too. On 23 September 2026 we asked consumer ChatGPT and Claude "Does llms.txt actually help SEO or AI search visibility?" once each. ChatGPT answered "not meaningfully" and rated it "very low / speculative"; Claude answered "on current evidence, no" and advised being "skeptical of any agency or app that sells llms.txt as a way to boost your AI visibility". Two single answers are an observation, not a measurement; the wider set is in what ChatGPT and Claude recommend in six DTC categories.

Treat a custom editorial llms.txt as navigation for automated readers. It is not the work. If you have one afternoon and you are choosing between replacing Shopify's managed file and writing an article that answers a question your buyers actually ask an assistant, write the article. The free tool will still be there tomorrow.

How Shopify serves /llms.txt today

This is the part most guides get wrong, so here is what Shopify's own documentation says.

Shopify themes support robots.txt.liquid, agents.md.liquid, llms.txt.liquid and llms-full.txt.liquid. Those templates cannot be JSON (Shopify, Templates, read 10 September 2026).

Four details matter:

Shopify already generates one. Shopify manages /agents.md for every store and mirrors it at /llms.txt and /llms-full.txt. That canonical document describes agent-facing commerce capabilities, including UCP and MCP discovery, read-only browsing URLs, published policies and shopping-agent guidance (Shopify, agents.md.liquid, read 10 September 2026). Before you build anything, open https://yourstore.com/agents.md and https://yourstore.com/llms.txt.

It is served at the bare primary domain. Shopify does not create localized or Markets-subfolder counterparts. If you customize the content, account for every market that depends on the one shared file.

Shopify uses a defined lookup order. A request for /llms.txt uses llms.txt.liquid if present, then agents.md.liquid, then Shopify's generated default. Adding only agents.md.liquid customizes /agents.md, /llms.txt and /llms-full.txt together. A dedicated llms.txt.liquid changes only /llms.txt. Shopify recommends that dedicated template solely when /llms.txt needs to diverge from /agents.md.

Custom templates have a restricted context. Inside agents.md.liquid and llms.txt.liquid, only the request and agents objects are available. Standard globals including shop, articles, blogs, collections, pages and linklists are not injected. Use the agents object for commerce-discovery values that must stay in sync. Hardcoded editorial links require manual upkeep.

What we saw on live stores, 25 September 2026

Forum threads from May 2026 said Shopify had "killed" llms.txt or started redirecting it to agents.md (Shopify Community, 24 May 2026, read 26 September 2026). We checked what stores actually return. On 25 September 2026 we fetched /llms.txt and /agents.md from four Shopify stores (Allbirds, Brooklinen, Tentree and ColourPop), following redirects:

What we checked	What came back
/llms.txt status	200 on all four, with no redirect
Content type	text/markdown; charset=utf-8
Content	Shopify's generated agent file, which says it mirrors /agents.md
/agents.md	200, the same document under its own URL

Six stores on one date is a spot check, not a survey, but the pattern was consistent. Two other Shopify stores, Spiritual Gangster and VRG GRL, served their own llms.txt while their /agents.md stayed on Shopify's default, which is what an llms.txt.liquid template does. So the route was not removed and nothing redirects: Shopify answers /llms.txt itself, and a theme template is the way to change it. What did stop working, according to merchants on Shopify's community forum, is a URL redirect set up before May to point /llms.txt somewhere else, because the platform route now answers first (Shopify Community, read 26 September 2026). The change is in Shopify's developer changelog of 28 May 2026.

If the managed default does not cover an advanced requirement, choose the narrowest override. Add agents.md.liquid when the same custom content should appear at all three agent URLs. Add llms.txt.liquid only when /llms.txt must be different. In Shopify admin, go to Online Store, Themes, open the theme's code editor, create the file in Templates and keep the agents discovery values that your use case needs.

If you need something Liquid cannot build, an app proxy is the other native route. A Shopify app can have one proxy route, configured with a prefix of a, apps, community or tools plus a subpath (Shopify, About app proxies and dynamic data, read 9 September 2026). That means a proxy can serve /a/llms or /tools/llms, not /llms.txt. For the root path the theme template is the route that exists.

What to put in a custom llms.txt

The following editorial index is an optional pattern for a documented divergence from Shopify's canonical commerce-discovery file. It is not a reason by itself to replace the managed default. Write it for a reader who has thirty seconds and no context.

# Sample Store

> Sample Store sells fragrance-free moisturisers and cleansers for
> reactive skin, formulated in the UK and shipped worldwide. Full
> ingredient lists on every product page.

## Start here
- [About Sample Store](https://samplestore.com/pages/about): who
  formulates the products and how they are tested
- [Ingredient glossary](https://samplestore.com/pages/ingredients):
  every active we use and what it does

## Guides
- [Choosing a moisturiser for reactive skin](https://samplestore.com/blogs/news/reactive-skin-moisturiser):
  how to read a label when your skin reacts to fragrance

## Collections
- [Moisturisers](https://samplestore.com/collections/moisturisers)
- [Cleansers](https://samplestore.com/collections/cleansers)

## Optional
- [Shipping and returns](https://samplestore.com/policies/refund-policy)

Four rules make a hand-maintained file useful:

1. Every description says what the page answers, not what it is. "How to read a label when your skin reacts to fragrance" beats "Our ingredient philosophy".
2. Link pages that stand alone. A page that only makes sense after reading two other pages is a poor entry.
3. Keep it selective. Choose the smallest set that covers the questions you want the file to route. If everything is included, the file stops being a guide.
4. Use absolute URLs. The file may be read far from your domain.

Our llms.txt generator builds a draft editorial index from the store name, summary and page links you enter. It does not crawl a store URL, inspect the Shopify-managed document or decide whether you should replace it. If you do publish its output on Shopify, it goes into a templates/llms.txt.liquid file as plain text, because the template cannot read your products, collections or pages for you. Compare the draft with /agents.md, preserve necessary commerce-discovery details and have a theme developer review the override before publishing it.

Checking that it works

Three checks, in order:

curl -sI https://yourstore.com/llms.txt        # 200, text/markdown
curl -s  https://yourstore.com/llms.txt | head -20

Compare /llms.txt with /agents.md. Matching content is expected when Shopify's default or an agents.md.liquid override serves both. If you maintain a dedicated editorial index, click every link and confirm its commerce-discovery references still work. Finally, confirm any override is in the published theme; a template saved only in a draft theme is not public.

Where the real work is

A custom editorial llms.txt can direct a reader to your good pages. It cannot make a page good. Once you have verified Shopify's managed file or published a justified override, the order that pays is:

1. Make sure the agents you want can fetch you at all. The AI crawlers split into training bots, search bots and user-triggered fetchers, and they behave differently. That is a robots.txt question, covered in AI crawlers and robots.txt on Shopify, with a generator at /tools/ai-robots-txt.
2. Write the pages an assistant would want to quote. Specific, dated, answer-shaped, self-contained. The wider method is in generative engine optimization for Shopify.
3. Measure by asking. Pick five buyer questions that do not contain your brand name, ask them in the services you choose and retain the answers. Our free manual checker prepares category questions and analyzes an answer you paste for brand mentions and store-domain links. It does not call an AI API.

Keep that separate from a repeatable AI visibility measurement with fixed questions, source URLs and unavailable answers recorded.

Citelift publishes product-linked articles on selected days and write/publish windows in the store timezone, with ceilings of four, seven or fourteen articles weekly by plan. Paid API visibility checks run monthly on Starter and weekly on Core and Growth; those observations do not establish that an llms.txt file changed visibility. The file itself can be prepared without subscribing to an app.

How it differs from robots.txt and your sitemap

Three files sit at the root of a store and people mix them up constantly. They answer three different questions.

robots.txt answers which automated agents may fetch which paths, subject to each vendor's documented behavior. ChatGPT's documentation says an OAI-SearchBot opt-out prevents site content from appearing in ChatGPT search answers, although a navigational link can still appear; its user-triggered ChatGPT-User agent may not follow robots rules. On Shopify, the file is generated for you and overridden with a robots.txt.liquid template.

Your sitemap answers what exists. It is machine-generated, exhaustive, and dull by design. Shopify maintains it, and you should not be editing it.

The llmstxt.org proposal presents llms.txt as a guided route to useful content. Shopify's managed /llms.txt instead mirrors the store's canonical agent-discovery document, including commerce endpoints and instructions. A custom editorial index can be selective, but that is a merchant choice rather than Shopify's default behavior.

That framing also tells you who owns maintenance. Shopify updates the sitemap and its managed agent-discovery document. A merchant or theme developer owns every custom template and should review it whenever the linked pages, policies or agent endpoints change.

/agents.md is the canonical file on Shopify. Its auto-populated agents object exposes the store name and URL, UCP discovery and MCP endpoint URLs, supported UCP versions, currency and sitemap URL. Since Shopify mirrors the generated document into /llms.txt and /llms-full.txt by default, the three paths match until a theme adds an override.

Common mistakes

Putting the file in the theme Assets folder. Assets are served under an asset URL, not at the root. The proposal is specific about the path.

Redirecting /llms.txt to a normal page. A URL redirect to /pages/llms-manifest returns HTML at the end of it. The point of the file is that it is plain markdown.

Editing a draft theme. Covered above, and worth repeating.

Letting a custom file rot. A hand-maintained template can fall behind Shopify's commerce configuration or retain dead editorial links. Assign an owner and review it when its source facts change.

Expecting it to be the answer. It is a discovery document. Judge your visibility with the five-question method, and judge your articles by whether a stranger could quote a paragraph without checking anything else.