Different platforms give you very different levels of control over robots.txt. This guide shows exactly what you can and cannot change on your setup, and how to make AI crawlers welcome.
In this guide you will learn how to edit Shopify robots.txt.liquid for AI access. We will keep it practical, with clear steps, visual breakdowns, and specific actions you can take today. The first step in any AI visibility project is to run a free AI crawler check on your website so you know exactly where you stand against the 196 bots we track across 8 categories.
Key Takeaways
- robots.txt for Shopify: What You Can and Cannot Change is a practical, repeatable process, not a one-time fix.
- Most AI visibility problems trace back to access, not content.
- You can verify every change with the free AI crawler check and the robots.txt check.
- Document your approach so the whole team applies it consistently.
Working With a Platform That Owns the File
On a managed platform the question is not what the ideal file contains but where the file comes from, so establishing ownership precedes every other step.
Find out what is actually serving the file
Determine whether robots.txt comes from the platform default, a plugin setting, a theme template or a physical file. Editing the wrong one produces changes that appear to work and then revert, which is the single most common support case.
Establish a single owner and stop editing elsewhere
When two mechanisms both write the file, the result changes unpredictably and looks like a caching problem. Pick one, document it, and leave the others alone permanently.
Record the served baseline from the live domain
Run an AI crawler checker against the public URL, not the editor preview. On managed platforms these differ often enough that the preview should never be trusted.
Make the change through the owning mechanism
Generate the intended rules with a robots.txt creator, then apply them through whichever mechanism you established as the owner, and publish if the platform requires a separate publish step.
Verify at the custom domain, and again after any theme or platform update
Confirm with a robots.txt check at the domain your audience actually uses. Platform updates and theme changes silently discard customisations, so this check belongs in your release routine.
Where the Rules Really Live on Shopify
Shopify did not permit robots.txt editing at all for most of its history, and now exposes it only through a Liquid theme template. The editing model is therefore fundamentally different from a normal host: there is no file to upload, the rules are generated from a template, and that template lives inside the theme rather than alongside your content.
Two consequences follow that catch people out. Advice written for a generic host does not apply mechanically, because the instruction to upload a file has no equivalent action. And because the rules are part of the theme, anything that replaces the theme also replaces the rules.
Four Things to Get Right on Shopify
Rules are edited in robots.txt.liquid, not uploaded
Shopify builds robots.txt from a Liquid template that you add to the theme, then modifies by appending or removing rules programmatically. This means changes are made in the theme code editor and take effect for the published theme only. It also means you are editing a generator rather than a file, so a syntax error in the template can produce output very different from what you intended. Always view the rendered result at the live URL afterwards.
The defaults already block the paths that should be blocked
Shopify ships sensible defaults that disallow cart, checkout, account and internal search paths. Those defaults are correct and undoing them causes real problems, including crawl waste on infinite search permutations and indexing of session-specific URLs. Start from the assumption that the defaults stay and that you are adding to them, not replacing them.
Collection filters generate heavy duplication
Faceted collection URLs, particularly tag and filter combinations, multiply quickly and consume crawl attention that should be reaching product pages. On a large catalogue this is the dominant crawl problem, and it is worse on Shopify than on many platforms because filter URLs are generated liberally. Constraining which combinations are crawlable transfers attention directly to the pages that can convert or be cited.
Theme updates and theme swaps discard your edits
Because the rules live in the theme, installing a new theme, duplicating and switching, or accepting a major theme update can silently drop your robots.txt customisation. The store keeps working, nothing errors, and the rules are simply gone. Record your customisations outside the theme and re-check the live file after any theme change.
The Shopify Failure Nobody Notices
Following generic robots.txt advice literally
Almost every robots.txt guide on the web tells you to create or upload a file at the root of your site. On Shopify there is no such action, so people either conclude it is impossible and give up, or find an unrelated file upload location and edit something that is never served. The correct action is a theme template, and knowing that is most of the difficulty.
How to Tell If Your Shopify Setup Is Working
The check that matters here: After any theme change, request robots.txt at your live storefront domain and confirm your custom rules are still present in the rendered output.
Where to Go From Here
Shopify is one piece of a larger picture. The AI bot directory documents every crawler we track with its operator, purpose and safety rating, and the batch URL checker audits many sites in one pass if you manage a portfolio.
Platform defaults change with every theme and plugin update. Re-run the robots.txt check after any migration, and verify end to end with an AI crawler checker.
Your Shopify Action Checklist
Five concrete steps, specific to what this guide covered. Work through them in order, changing one thing at a time so you can tell which change produced the result.
- □Identify whether your platform generates robots.txt dynamically, which overrides any static file you upload.
- □Check for an SEO plugin writing its own rules, a frequent source of inherited blocks.
- □Apply the platform-specific pattern from this guide rather than a generic template.
- □Validate the published file at your live domain, not in the editor preview.
- □Re-check after the next theme or plugin update, since these commonly reset the file.
