Shopify "Indexed, though blocked by robots.txt": What This Warning Means and How to Resolve It Correctly
Google Search Console's "Indexed, though blocked by robots.txt" warning means Google indexed a URL even though your robots.txt disallows crawling it, usually because the URL was found via links; Google indexes it without crawling the content, often with a blank or poor snippet. On Shopify the robots.txt is auto-generated and disallows paths like /cart, /checkout, /search and filtered collection URLs, but you can override it through the robots.txt.liquid template, and SEO apps can inject their own Disallow rules. The fix depends on intent, and this is the common trap: robots.txt alone will not REMOVE a page from the index, because a blocked page can't be crawled to even see a noindex tag. Shopify does not version robots.txt.liquid edits or app-injected rules, so once a rule is added or a theme is changed there is no native history of the previous robots or meta-robots state to restore.
If you didn't already have a backup, those old values are gone โ Shopify keeps no history.
The steps below recover what you can. To make the next time a 1-click undo instead of hours of CSV work: a daily snapshot of every SEO field. Free to monitor, no card โ and SEO Vault only reads your store unless you click restore.
Stop and diagnose: in GSC open the "Indexed, though blocked by robots.txt" report and inspect sample URLs, deciding per URL whether it should be indexed. View yourstore.com/robots.txt, locate the matching Disallow rule, and determine whether it is Shopify's default, a custom edit in robots.txt.liquid (Online Store > Themes > Edit code), or a rule added by an SEO app.
If the page should be OUT of the index: remove the Disallow first so Google can crawl it, then add a noindex meta robots tag to those URLs (via your theme or SEO app) so Google can actually read it; for filtered or parameter collection URLs rely on Shopify's existing canonical handling. Use the GSC Removals tool only for urgent temporary removal.
If the page should be IN the index: edit robots.txt.liquid to remove the Disallow (or revert the app rule), test with URL Inspection > Test Live URL and the robots tester, then click Validate Fix and Request Indexing. If a theme or app edit changed your robots or meta config and you lack the prior version, recover the previous robots.txt.liquid from a theme backup or a Wayback Machine snapshot of /robots.txt.
Stay ahead with daily snapshots: robots.txt and meta-robots changes are silent, unversioned in Shopify, and directly control whether pages can rank. A daily backup of your SEO fields plus alerts when an app makes bulk changes means you catch an unwanted Disallow or noindex the day it appears. SEO Vault keeps a daily history of products and collections so you can compare and restore the last good state.
Source: Google Search Console Help โ "Indexed, though blocked by robots.txt," support.google.com/webmasters/answer/7440203; Shopify Help Center โ "Edit your robots.txt.liquid file"
SEO Vault keeps a daily snapshot of every SEO field on your store โ meta titles, descriptions, alt-text, tags, handles (products AND collections) โ and emails you the moment something changes in bulk, with the likely app responsible. One click restores yesterday's state, just the SEO fields. Free to monitor and get alerted; $14/mo for 1-click restore.