robot AI looking at a store door that has a sign saying "Do Not Enter!" The store is meant to represent a Shopify store that has not updated their robots.txt file.

Did you kill your robots.txt for AI crawlers?

Have you ever opened your robots.txt file? There is no real reason you would have. It sounds like something a developer handles, it sits at an address nobody types by accident, and for years nothing about it changed enough to matter.

That stopped being true recently, and quietly. The default Shopify robots.txt was rewritten with AI crawlers in mind, and the rewrite is bigger than the Shopify AI checklists circulating about it seem to know. Which has produced a strange situation. A merchant reads a guide telling her to fix a problem in her robots.txt, goes and looks, and the problem is not there. She was sent looking for something Shopify already removed.

The merchants this actually catches are the ones who did the old advice properly, by hand, years ago.

This is a short piece, on purpose, because the fix is short. It is also the kind of fix that only exists because Shopify moved and nobody told you.

The fix everyone is still recommending

The old Shopify robots.txt default hid your policy pages, everything under /policies/, from crawlers entirely, AI crawlers included. Your shipping policy, your return policy, your terms, none of it was needed for SEO, so leaving it out made room for a deeper crawl into products and more interesting things. 

Shopify quietly updated the robots.txt file to include the policy pages along with instructions for bots and AI. The update skipped any files that had been changed to avoid destroying custom coding the themes might need. Which means a merchant who never touched the file is fine. A merchant who touched it years ago, to do exactly what the old advice said, is the one who has a problem. So does the merchant who paid someone to set up their site properly years ago and doesn’t even know the robots.txt file was customized.

What the new Shopify robots.txt tells AI crawlers

Open the robots.txt of a store on the current default and the file opens with a comment. It states plainly that product pages, collection pages, standard pages, blog content, and policy HTML are crawlable. Below that, it points to a file called agents.md, and to something called a UCP endpoint.

Agents.md is Shopify’s description of your store written for AI shopping agents, the kind of software built to browse a store and act on a shopper’s behalf rather than simply index it for a search result. It tells an agent where your product data lives, where your checkout endpoints are, and how to transact with you. Shopify manages that file for every store by default. You did not have to write it, hire someone to write it, or know it existed. It is there whether or not you have ever looked.

Being on the current default doesn’t get you recommended by anything. It just makes your store readable. There is a real difference between the two. Matching is whether an engine can work out that what you sell is what someone meant. Recommendation, is whether anything decides to name you out loud. Agents.md and the UCP endpoint sit entirely on the matching side. They tell an agent how to browse you and how to transact with you cleanly if it gets that far. Neither one is a vote of confidence. Neither one is new visibility. It is plumbing, and plumbing does not choose winners. It just stops you from being ruled out by accident.

I want to be specific about what I’m not claiming, because it would be easy to read this section as “get on the current default and AI agents will start buying from you.” They won’t, at least not because of this file. Agents.md is instructions for an agent that has already decided to look at your store. It says nothing about why an agent would decide that in the first place. We’ll cover that question in a later post in this series, which is about where recommendations actually come from. This post is only about not being locked out of the conversation before it starts.

How to tell which version you have

I opened five robots.txt files from large Shopify stores in late September 2026. Two were on the new file. Three were still on the old one, which is exactly why the check below is worth running rather than assuming.

The diagnostic is short. Open “yourstore.com”/robots.txt and read the first 10 lines. If you see the crawlable-content comment and a pointer to agents.md, you are current, and there is nothing else to do here. It should start with the line below.

First line of Shopify's new robot.txt file

If instead you see a line reading Disallow: /policies/, one of two things is true. Either Shopify is still serving your store the old default, or somebody customized this file at some point and Shopify stopped updating it the day they did. Shopify’s own documentation on editing robots.txt is plain about the second case: a custom file written out as plain text is one Shopify can no longer change with future updates. It freezes at whatever the default looked like that day. Any change at any time freezes that file and it will never be automatically updated when Shopify updates the default. 

If you want to dig into the code, in your admin, go to Online Store, then Themes, then Edit code, and look under Templates for a file called robots.txt.liquid. That file only exists if someone made it. If it is there, your robots.txt has been customized. If it is not, just close the file and rejoice that you are already showing the default Shopify robots.txt file.

The fix may be as simple as deleting the customized file. Ask whoever handles your theme whether anything in that custom robots.txt is still doing a job that matters. Usually nothing is. Shopify’s own instruction for going back to the default is to delete the custom robots.txt.liquid file, with a warning attached that Support will not help with this file and that getting it wrong can cost a store all of its traffic. No pressure. That’s the reason to hand it to your theme person rather than do it yourself. Once the custom file is gone the current default takes back over, with its pointer to agents.md, the UCP endpoint, and open policy pages, all at once, and it holds up better than editing around the old block by hand.

Quick summary of how to do this today (October 2026). Open “yourstore”.com/robots.txt and read the first 10 lines. Look for a comment describing what’s crawlable and a line pointing to agents.md. If you see Disallow: /policies/ anywhere in the file, go to Online Store, then Themes, then Edit code, and look under Templates for robots.txt.liquid. If it is there, ask whoever manages your theme whether it is still needed. If it isn’t, ask them to delete it and let the current default take over.

None of this gets you chosen. It gets you read, which is the floor and not the ceiling, and everything fails without it. The post, “Can AI Find Your Shopify Store?“, goes into where the actual recommendation decision gets made, and it is mostly made off your site entirely. If you want a broader read on where your store’s SEO stands beyond this one file, the “Shopify SEO Survival Quiz” is built for exactly that.

Picture of Stylaquin

Stylaquin

Helping you engage and delight shoppers!

Leave a Reply

Your email address will not be published. Required fields are marked *