Shopify Sitemap "Couldn't Fetch" in Google Search Console: Fixes

What does "Couldn't fetch" actually mean?

In the Search Console Sitemaps report, Google uses three outcomes. Success means the sitemap was fetched and read without errors. Has errors means the file was retrieved but had parsing problems. Couldn't fetch means Google was unable to retrieve the file at all. Google's list of reasons for the last one is short: robots.txt blocking the file, an unresolved manual action, a wrong URL returning a 404, server problems, and low crawl demand for the site.

For a Shopify store, robots.txt blocking, a manual action and a server fault are rare. The causes below are the ones that produce the message in practice, and the checks in the next section tell them apart in a few minutes.

What is the Shopify sitemap URL?

Every Shopify store generates a sitemap without any setup. Shopify's help page says it sits at the root of your domain, for example example.com/sitemap.xml, and that it links to separate files for products, collections, blogs and pages, including the primary product image. It updates when you add a page, product, collection, image or blog post.

That main file is an index that points to the others. Its file names look like sitemap_products_1.xml, sitemap_pages_1.xml, sitemap_collections_1.xml and sitemap_blogs_1.xml. You do not edit any of them: a comment inside the live file says the sitemap cannot be edited manually and is kept up to date in real time. The address to give Google is sitemap.xml, and Shopify's own submission steps say the same.

Which cause do you have? Work through these checks in order

Start at the top. Each check takes a minute, and most stores find the cause in the first three.

1. 01The store is still in private mode. Shopify states Google cannot access the sitemap while the store has a password. In admin, open Online Store, then Preferences, and remove the storefront password. Then resubmit.
2. 02The property does not match the address. Google says a sitemap submitted for http://example.com does not appear for https://example.com or http://www.example.com. If your property is https://yourstore.com/ but your primary domain redirects to https://www.yourstore.com, the property and the live address are different sites. Check which one your store really uses (see the next section) and submit under that property.
3. 03The wrong sitemap address. Type yourstore.com/sitemap.xml into a browser on the same host your store redirects to. It should show an XML index. A 404 page means the address is wrong or the domain is not the one connected to Shopify.
4. 04A child sitemap was submitted instead of sitemap.xml. Shopify's steps say to enter sitemap.xml. The child files carry from and to parameters in their addresses, which change as your catalogue grows, so a copied one can go stale. Delete any child sitemaps from the report and submit only sitemap.xml.
5. 05Several domains. Shopify says stores on a Basic plan or higher with international domains generate a separate sitemap for each domain, and that each must be verified and submitted individually. A Shopify staff reply on the developer forum also says each localised sitemap needs its own Search Console property.
6. 06Verification lost. If you verified with an HTML tag in theme.liquid and later changed or updated the theme, the tag may be gone. Reverify the property, ideally by DNS, so a theme change cannot break it.
7. 07robots.txt or a redirect rule. Google lists robots.txt blocking as a cause. Open yourstore.com/robots.txt and check nothing disallows /sitemap.xml.

Domain property or URL-prefix property: which one avoids the mismatch?

Google explains the difference. A Domain property covers all subdomains (www, m and so on) and multiple protocols (http and https), and it needs DNS verification only. A URL-prefix property covers only URLs that begin with the exact prefix you enter, including the protocol, and it supports several verification methods.

For a Shopify store the Domain property is the safer choice, because it does not care whether your customers land on www or the bare domain, or on http before the redirect to https. The price is DNS access: you add a TXT record at your registrar or in Shopify, if Shopify manages the domain. If you use a URL-prefix property, make it match the primary domain character for character, including https and the www.

The how to connect Shopify to Google Search Console guide has the verification steps for both cases.

Apex versus www: how to see which one your store uses

Shopify stores have one primary domain, and the other version redirects to it. You can see this yourself by requesting the header of the other version. On 28 September 2026 a request to a public Shopify store's bare-domain sitemap returned a 301 to the www version, with a header saying the redirect reason was canonical host redirection. That is the normal behaviour, and it is why a property registered for the wrong host looks empty.

Run the same check on yours:

1. 01In a terminal, run curl -I https://yourstore.com/sitemap.xml and read the status line. A 200 means that host serves the sitemap. A 301 shows in the location line which host is primary.
2. 02Repeat with and without www. The primary host should answer with 200 and the other should redirect to it.
3. 03In Shopify admin, open Settings, then Domains, and confirm which domain is marked primary.
4. 04Add or edit the Search Console property so it matches the primary host, then submit sitemap.xml there.

The sitemap loads in my browser but Search Console still says couldn't fetch

This is the most reported case on the Shopify Community and Google Search Central forums: the file opens fine, URL Inspection shows the pages as crawlable, yet the report keeps the error. Shopify staff have answered the same thing on the developer forum without pointing to a fault in the file, in a thread where the merchant says the same sitemap works in Bing.

There are two things to do. First, test with Google's own tool rather than the report. In URL Inspection, enter the full sitemap address and run the live test. Google's guidance is to check that Crawl allowed shows Yes and Page fetch shows Successful. Second, judge success by pages, not by the status line. If your product URLs appear in the Pages report and in a site: search, Google is reading your store, whatever the Sitemaps report says.

Google also says a sitemap does not guarantee that every item is crawled or indexed. For a small, well-linked store of roughly 500 pages or fewer, Google says a sitemap is not even necessary, because internal links do the discovery. That gives you a way to keep perspective while the status catches up.

What to do if it persists

Delete the sitemap entry, wait, and submit sitemap.xml once more. Avoid resubmitting over and over. Then confirm the basics that would hold for any page: the storefront password is off, the pages carry no noindex tag, and a live URL Inspection test on the home page succeeds.

If the home page is fine and the status still will not clear, stop chasing it. Link your important products from collections and the menu so Google finds them by crawling, and check the Pages report after a week. If pages are stuck in "Crawled, currently not indexed" or "Discovered, currently not indexed", the sitemap is not your problem, and the Shopify crawled currently not indexed guide covers that.

For the wider list of things that keep a store out of Google, follow how to get your Shopify store on Google, and use the Shopify store audit checklist for a full pass. To see what a crawler receives from a product page, the free AI readiness checker at /tools/ai-readiness-checker fetches one the way a crawler does, without JavaScript. It checks the page itself, not your sitemap.

Frequently asked questions