The Shopify sitemap error on sitemap_collections_1.xml — usually reported in Google Search Console as "Couldn't fetch," "HTTP error," or "Sitemap could not be read" — looks alarming and is almost always fixable in minutes. This guide explains what the file is, why the error appears, and the exact sequence of checks that resolves it, in the order of how often each cause turns out to be the real one.

What sitemap_collections_1.xml actually is

Shopify's sitemap.xml is automatically generated — you cannot edit it, and that is by design. The root file at your-store.com/sitemap.xml is a sitemap index: it does not list your pages directly, it points to child sitemaps that Shopify creates per resource type — sitemap_products_1.xml, sitemap_collections_1.xml, sitemap_pages_1.xml, and sitemap_blogs_1.xml. Large catalogs get numbered continuations (_2, _3) as each file fills. The collections child simply lists every published collection URL with its last-modified date.

Because the children are generated from your live catalog, they update themselves when you add, remove, or hide resources. That is the good news underneath this error: the file itself is rarely broken, because Shopify builds it. The error is almost always about access — Google could not fetch the file — or about a stale report. The Shopify sitemap guide covers the system end to end; this article is the troubleshooting path for the error itself.

Step 1: Open the file yourself

Before changing anything, open your-store.com/sitemap_collections_1.xml in a browser (and the root sitemap.xml). Three outcomes tell you three different things.

If you see XML with a list of collection URLs, the file is fine — the problem is access or reporting, so continue to steps 2–5. If you are redirected to a password page, that is your answer: a password-protected store blocks Googlebot from every URL, sitemaps included, and the fix is removing the storefront password under Online Store → Preferences. If you get a 404, check which domain you tested — the sitemap only serves on your primary domain, so the .myshopify.com variant or an unredirected alias can 404 while the real file is healthy.

Step 2: Check the domain you submitted

In Search Console, sitemap URLs are matched against the property's exact domain. The classic mistake is submitting a sitemap under a www property when the primary domain is bare (or vice versa), or under the .myshopify.com address. Confirm your primary domain in Settings → Domains in the Shopify admin, make sure every other variant 301-redirects to it, and submit only https://your-primary-domain/sitemap.xml in the matching GSC property. If you have recently changed the primary domain, delete the old sitemap submission and resubmit on the new property.

Step 3: Understand the "Couldn't fetch" pending state

Here is the one that wastes the most merchant hours: "Couldn't fetch" is often not an error at all. When you first submit a sitemap, Search Console displays "Couldn't fetch" as the status until Google's first successful crawl of the file, which can take anywhere from hours to a couple of weeks on a new property. If the file opens fine in your browser (step 1 passed) and you submitted it recently, the correct action is to wait several days before treating it as a real failure. Re-submitting repeatedly does not speed this up.

The reliable tie-breaker is the URL Inspection tool: inspect the sitemap child URL directly. If a live test shows Google can fetch it, the report row is stale and will clear on its own.

Step 4: Rule out firewall and bot-protection blocks

If the file loads for you but Google genuinely cannot fetch it over days, something between Google and Shopify is refusing the request. The usual suspect is a CDN or security layer in front of a custom domain — Cloudflare's Bot Fight Mode and similar features are known to challenge or block legitimate crawlers, including Googlebot and the sitemap fetcher. If your DNS or proxy sits on Cloudflare or another CDN, check its firewall events for blocked Googlebot requests and disable bot-challenge rules for verified search crawlers. The same layer often blocks AI crawlers too, which quietly costs you answer-engine visibility on top of the sitemap error.

Also confirm your robots.txt still references the sitemap and has not gained a rule that disallows it — Shopify's default is correct, but customized robots.txt.liquid templates can break it.

Step 5: Check for an empty or genuinely broken child

Rarely, the child itself is the issue. A store with zero published collections produces an empty collections sitemap that some validators flag. A collection published only to a sales channel other than Online Store will be absent, and a collection hidden after the sitemap was cached may briefly linger. These states resolve as Shopify regenerates the file; your lever is making sure the resources you want indexed are published to the Online Store channel and visible.

What this error does and does not affect

Keep perspective while you fix it: a sitemap fetch error does not deindex your site. Google discovers URLs through links regardless; the sitemap accelerates discovery and feeds the Pages report. Fix the access problem, resubmit the root sitemap.xml once, and move on — the row typically flips to Success on the next crawl cycle. If your collections still are not getting indexed afterward, the cause is elsewhere: thin collection pages, canonical issues, or internal linking, covered in Shopify collections SEO and the Google Search Console for Shopify guide.

A free store audit checks the sitemap, robots rules, and indexation state in one pass — including whether each sitemap child returns 200 and whether the pages it lists are actually indexable — so you can confirm the whole chain instead of one file.