llms.txt is a plain-text file at the root of your domain (yourstore.com/llms.txt) that gives AI assistants a curated map of your most important pages and policies, with a little context for each. Think of it as a sitemap written for language models rather than search crawlers, pointing them at what matters instead of making them guess from your whole site.

Do AI assistants actually use llms.txt?

The major assistants increasingly look for it as a low-cost way to understand a site without crawling everything. It is a fast-emerging convention, not a guaranteed ranking factor, but it is cheap to publish and it removes ambiguity about which pages you want read. Stores that publish a clean one give agents a curated path; stores that do not leave it to chance.

How is llms.txt different from robots.txt and sitemap.xml?

robots.txt controls who is allowed to crawl. sitemap.xml lists every URL for search crawlers. llms.txt is curated and contextual: it points AI assistants at your best, most relevant pages (key collections, best sellers, policies) with a sentence of context each, rather than dumping the full URL set.

How do I add llms.txt to a Shopify store?

You serve a plain-text file at your domain root. On Shopify that usually means an app or app proxy, since the platform does not let you drop arbitrary root files into the theme. AgentReady generates and serves a maintained llms.txt for you, refreshed as your catalog and policies change.

llms.txt for Shopify: The AI Discovery File, Explained

Three files at the root of your domain decide whether AI assistants can find and understand your store: robots.txt, sitemap.xml, and the newest of the three, llms.txt. This post is about the last one, because it is the one most Shopify stores do not have yet, and the one that is cheapest to get right.

What llms.txt is

llms.txt is a plain-text file you serve at yourstore.com/llms.txt. It gives an AI assistant a curated, human-written map of your most important pages: your best collections, your best sellers, your shipping and returns policies, your about page, each with a short line of context.

A sitemap lists every URL for a search crawler to chew through. llms.txt does something different. It says, in effect, "if you only read a few things about this store, read these, and here is what each one is." That curation is the whole point. It removes the guesswork an assistant would otherwise do against your entire site.

Why it matters for a store

AI assistants answer shopping questions on a budget. They are not going to crawl and reason over every page of your store for one recommendation. A clean llms.txt gives them a shortcut to the pages you actually want represented, with context that helps them describe you correctly: what you sell, who you are, what your policies are.

It is a fast-emerging convention rather than a guaranteed ranking factor. But it costs almost nothing to publish, and the downside of not having one is simple: you leave it to the assistant to decide which of your pages matter, instead of telling it.

What a good one contains

A useful llms.txt for a store points at:

Your homepage and brand description.
Your top collections and a few flagship products.
Your shipping and return policies (the questions shoppers ask agents most).
Your FAQ or help content.
Your contact and about pages.

Each entry gets a short, plain sentence of context. Keep it curated. A llms.txt that just dumps every URL is back to being a sitemap.

The Shopify wrinkle

On most platforms you would drop a text file at the web root and be done. Shopify does not let you place arbitrary files at your domain root through the theme, so a real llms.txt needs an app or an app proxy to serve it at the correct path. That is why most Shopify stores simply do not have one, even ones that are otherwise well optimized.

Check whether you have one (and whether it is any good)

The free AI-readiness checker looks for /llms.txt on your store the way an assistant would, reports whether it exists, and flags it among the other discovery files and structured data that decide your visibility. For the full picture, the discoverability playbook covers all five pillars.

The hands-off version

You can write and host llms.txt yourself, but like the rest of your machine-readable data, it has to stay current as your catalog and policies change. AgentReady generates and serves a maintained llms.txt for your store, refreshes it automatically, and pairs it with the structured data and policy signals assistants read alongside it. It is free, needs no theme edits, and shows you what an agent sees about your store at any time.

Run the checker to see whether yours is there yet.