Somewhere on every Shopify AI checklist handed to merchants, you’ll find the same instruction: add an llms.txt file. So you open yourstore.com/llms.txt to see what you’re working with, and there’s already a file there. You didn’t write it. Shopify serves one for every store by default, and its own documentation says so in as many words, with one exception: if you have added a template of your own at that address, yours is what shows instead.
Which leaves you with a different question: whether to spend any of your limited time customizing or maintaining the Shopify llms.txt that’s already sitting there. The answer is no, and the evidence is stronger than it would have been a few months ago.
The Shopify llms.txt that’s already there
This is the same shape as the robots.txt piece in this series: Shopify already did the thing the checklist tells you to do.
The llms.txt format is a plain text file meant to give an AI model a curated summary of a site: links to the pages that matter most, described the way the site owner would describe them. It caught on with checklist writers for an honest reason. It’s cheap to explain, cheap to build, and it feels like doing something, which matters a lot when the rest of this topic feels like guessing in the dark.
Except now there’s nothing to build. Read the first line of the file at that address and it says Agent Instructions, because what Shopify serves at /llms.txt is your agents.md file, the one the robots.txt piece describes, answering to a second name. Shopify’s changelog on customizing these files says so plainly: /llms.txt and /llms-full.txt point to the agents.md content unless you add a template of your own. Of eight Shopify stores spot-checked in late September 2026, seven were serving that default and one had replaced it with a file of its own. The checklist item that used to take a merchant real effort now costs nothing, and the decision has quietly moved from whether to make one to whether to touch the one you have. The checklists haven’t caught up.
Three files are easy to mix up, and on a Shopify store two of them are the same file by default. Robots.txt tells a crawler what it’s allowed to read. Agents.md is Shopify’s description of your store written for AI shopping assistants: where the product data is, where the checkout endpoints are, and how to transact with you. The llms.txt format was designed as something else, a curated summary handing a model a shortcut instead of making it read the site. What Shopify puts at that address is not that. It is the agents.md file again, and the evidence below is the reason not to mind. Robots.txt has its own piece in this series.
What the evidence says
Google has said, on the record, that Search ignores the file. Google Search Central’s guide to optimizing for generative AI features, updated July 10, 2026, states plainly that you don’t need llms.txt or similar files to appear in Google Search, including its generative AI features, because Google Search itself doesn’t use them. Creating one for other purposes is fine, and doing so “will neither harm nor help your site’s visibility or rankings in Google Search, as Google Search ignores them.” That covers Google’s surfaces only. It says nothing about ChatGPT, Perplexity, or Claude.
For the wider picture, Ahrefs looked at how often the file gets requested. Their June 2026 study covered 137,210 domains that received traffic in May 2026. Of those, 28% publish a valid llms.txt file. Of that group, 97% received zero requests for the file that month. Of the requests that did happen, 96% came from bots, and only 19.5% of fetches came from a named AI tool; the rest were tools scraping the file itself or bots crawling for unrelated reasons. Their own summary: for a store hoping to show up in ChatGPT, Perplexity, or AI Overviews, an llms.txt file is “largely decoration.”
Ahrefs added a caveat worth keeping, and it strengthens the case. Every figure in the study is, in their words, “a ceiling on actual llms.txt consumption.” Real use sits at or below what they measured. It’s also worth naming what kind of measurement this is. It’s an indirect measure: it counts whether crawlers request the file at all. A controlled test of whether having one changes how often a store gets cited is a different experiment, and it is not the one either of these studies ran.
A smaller study from Otterly.ai points the same direction. One site, 90 days, more than 62,000 AI bot visits, 84 of which requested llms.txt. Their own conclusion about the file’s impact on AI crawler behavior and discovery: “marginal at best.” That works out to about 0.1% of the bot traffic on that site, but one site is one site, so I’d hold it loosely.
None of this proves the file does literally nothing. What the evidence supports is the file is close to unread, Google Search ignores it by stated policy, and that combination puts it near the bottom of a Shopify merchant’s list. It keeps turning up on the checklists anyway.
Where to put your time instead
Leave the file Shopify already generated alone. Don’t customize it, don’t write a matching llms-full.txt, don’t spend time deciding what belongs in it. Put that time toward the two things in this series with a clearer return. Check which version of your robots.txt you’re actually on, because that file has been rewritten once already and a frozen customization can quietly keep your policy pages hidden without you ever seeing an error. Then read your own shipping policy the way a stranger would, because there’s a real chance it’s blank, and it’s now visible to everything that comes looking. If you have time left after that, the hub’s next suggestion is alt text on your 20 best sellers. If you have to choose between the first two, do the robots.txt check first. A blank shipping policy is obvious the moment you look at it, but a frozen robots.txt never announces itself.
If you’ve already spent real time customizing your llms.txt, nothing needs to come down. Google’s guide calls it “completely fine” to create and maintain these files for other services that use them, so the file can stay where it is. Most of the evidence above is only a few months old, and may change as AI changes, which is why this piece carries a date.
How to do this today (October 2026). Open yourstore.com/llms.txt and confirm the file Shopify generated is already there. Then close the tab. Mark it done on your checklist.
What would change my mind
This is deliberately the kind of advice that goes stale. If Google starts reading the file, or if the major AI assistants start reading it in earnest, what the file should contain changes. The numbers I’d watch are Ahrefs’ own. If someone reruns the study and named AI tools account for well more than one fetch in five, or the share of files receiving any requests climbs well past 3%, I’d revisit all of this.
Shopify handled this item for you, and it doesn’t need the attention the checklists imply. The fuller case for all of it lives in the hub post, Can AI Find Your Shopify Store?
