Skip to content

Fix

Shopify sitemap "Couldn't fetch" in Google Search Console: 6 causes, checked in order

Search Console says "Couldn't fetch" for your Shopify sitemap? Six causes in the order to check them, with the test and the fix for each.

· 4 min read · Ahoi Apps team

Quick answer

"Couldn't fetch" means Google tried to load your sitemap and didn't get it. On Shopify the file itself is rarely the problem, because Shopify generates it. Check these in order: the store is still in private mode, you submitted the wrong address, Google simply hasn't retried yet, or something blocks Google from the file. Test the sitemap URL with URL Inspection › Live test; if it says the page can be fetched, resubmit and wait a few days.

The symptom

In Google Search Console, under Indexing › Sitemaps, every submitted sitemap has a status: Success, Has errors, or Couldn’t fetch. The last one means Google couldn’t retrieve the file at all (Google’s Sitemaps report help).

First, the one test that tells you most

Click the sitemap in the report and copy its URL. Paste it into URL Inspection at the top of Search Console, press Enter and click Live test. Open Page availability. You want “Crawl allowed? Yes” and “Page fetch: Successful”.

If both are there, the cause is 3 or 6 below.

The store is in private mode

In private mode, all pages are hidden from visitors and search engines behind the password page. New stores start this way.

Check

In the Shopify admin, open Online Store. The access menu reads Private or Public.

Fix

Click Private, select Public and click Update. Then resubmit the sitemap. Shopify’s Help Center says the store has to be accessible for the crawler to work.

The wrong address

The myshopify.com address instead of your primary domain, http instead of https, a www the store doesn’t use, a typo, or the right sitemap in a Search Console property for a different domain. Google doesn’t follow redirects from a submitted sitemap URL, and the report only covers sitemaps inside the current property.

Check

The property name and the submitted URL both match the address in your browser bar when you visit your store.

Fix

Click the wrong entry, open the more options menu and choose Remove sitemap. Then submit sitemap.xml in the right property. A domain that only redirects to your primary domain needs no sitemap of its own.

Google hasn’t come back yet

A fetch can fail for a passing reason, such as the server being unavailable for a moment. Google retries for a few days.

Check

The Last read column. It’s only filled once Google has fetched the file.

Fix

Nothing for a few days. If the live test passes and the status hasn’t changed, resubmit once. There’s no need to do it daily; Google retries on its own.

robots.txt blocks it

Worth checking if anyone has edited robots.txt.liquid. Google respects robots.txt when it fetches sitemaps.

Check

Open yourstore.com/robots.txt and look for a Disallow rule that matches /sitemap.

Fix

Remove the rule. To go back to Shopify’s default, delete robots.txt.liquid from the theme’s templates in Edit code (Shopify Help Center).

A manual action on the site

Google doesn’t read sitemaps while a site has an unresolved manual action.

Check

The Manual actions report in Search Console.

Fix

Resolve what it lists, then resubmit the sitemap.

Low crawl demand on a new store

Google lists this as a cause and ties crawl demand to the quality of a site’s content. There is nothing to fix in the sitemap. The store needs content and time.

What it is not

  • A broken Shopify sitemap. Shopify generates and updates the file. There’s nothing to regenerate.
  • A sign that Google can’t find your pages. Google says it can usually discover most of a site through its links when pages are properly linked (Google Search Central).

“Sitemap could not be read” and “General HTTP error”

“Sitemap could not be read” is what the sitemap’s details page says when the fetch failed. “General HTTP error” covers HTTP errors without a more specific message, and Google notes it can be a 404, which points back to cause 2. Run the same six checks.

Checklist

  1. Online Store shows Public, not Private.
  2. The submitted URL and the Search Console property match your primary domain, with https.
  3. URL Inspection › Live test on the sitemap URL: crawl allowed, page fetch successful.
  4. robots.txt has no Disallow that matches /sitemap.
  5. The Manual actions report is empty.
  6. A few days have passed since the last submit; then resubmit once.

If it’s still not working

Ask in Google’s Search Console Help Community, and contact Shopify Support for anything that points at the store’s availability.

Our own Easy Sitemap Builder for SEO can’t fix this error: it doesn’t create Shopify’s sitemap.xml and can’t change how Google fetches it. If you use it and aren’t sure what you submitted, write to service@ahoiapps.com with your store’s address.

More: our Shopify sitemap guide, sitemap apps for Shopify, compared, and the sibling fix post Shopify rich results not showing.

FAQ

Why does my Shopify sitemap say "Couldn't fetch"?

Google tried to load the sitemap file and didn't get it. On a Shopify store the usual reasons are private mode, a wrong address or property in Search Console, or a first attempt Google hasn't repeated yet. Shopify generates the file, so the file itself is rarely the problem.

How long does Google take to fetch a Shopify sitemap?

Google says a submitted sitemap should be fetched immediately. If the fetch fails, it retries for a few days and then stops. Crawling the URLs listed in the sitemap takes longer, and Google gives no timeframe for that.

How do I resubmit a sitemap in Search Console?

Open Indexing › Sitemaps, enter sitemap.xml under Add a new sitemap and click Submit. To clear a wrong entry first, click it in the list, open the more options menu and choose Remove sitemap.

Do I need a sitemap app to fix "Couldn't fetch"?

No. Shopify creates and updates sitemap.xml, and no app changes how Google fetches it. The fix is in your store's access setting, the address you submitted, or time.

Read time by our Estimated Read Time logic.

Related