Skip to content

Indexing · Fix

Search Console says “Couldn’t fetch” for my Squarespace sitemap

Published 5 named sources

Usually nothing is broken yet. Squarespace says a “Couldn’t fetch” message can appear for 24 to 48 hours while Google processes a new sitemap2, and Google says the same about new sitemaps1. If it is still there after two days, the cause is almost always one of three things: the sitemap URL doesn’t load for Google, the site is behind a password or still on a trial, or the sitemap was submitted under a property that doesn’t match your primary domain.

Work through the five steps below in order. Each one takes a couple of minutes, and the fourth tells you exactly why Google can’t read the file.

Steps at a glance

  1. Give it 24-48 hours
  2. Open the sitemap yourself
  3. Match the property and the domain
  4. Run a live URL Inspection on the sitemap URL
  5. Resubmit and recheck
Jump to the fix

Rather not touch code? We fix sitemap fetch errors as part of the $299 install. Start my setup 

What “Couldn’t fetch” means in the Sitemaps report

Couldn't fetch means Google tried to download the sitemap file itself and failed. It says nothing yet about the pages listed inside it. Google's Sitemaps report names the usual reasons: the file is blocked by robots.txt, the URL is wrong and returns a 404, the server was unavailable or returned a transient error, a manual action applies to the site, or crawl demand for the site is low. Two related statuses point somewhere else: Sitemap could not be read means Google fetched the file but hit an error reading it, and URL not allowed means the sitemap lists URLs on a different domain, or higher up the folder tree, than the sitemap file.

Those definitions come straight from Google’s Sitemaps report documentation1. On Squarespace you can rule some of them out quickly. The platform generates the sitemap for you, so the format is not the problem. The usual causes are on the setup side: the site isn’t publicly reachable yet, or the address you submitted doesn’t match the domain Squarespace actually serves.

Step 1: give it 24-48 hours before changing anything

If you submitted the sitemap today or yesterday, wait. Squarespace's own Search Console guide says a Couldn't fetch message doesn't always mean there's an issue with your site and may appear for 24 to 48 hours while Google processes the sitemap. Google's documentation also notes that new sitemaps can show fetch errors temporarily. Resubmitting over and over in the first two days doesn't speed anything up.

Squarespace also recommends waiting 48 hours after connecting a third-party domain before you verify the site in Search Console at all2. If the domain was connected this week, that alone can explain the error.

Step 2: open the sitemap yourself in a private window

Open your sitemap URL in a private browser window, where you are not logged in to Squarespace. On a custom domain it is https://www.yourdomain.com/sitemap.xml; on the built-in domain it is https://sitename.squarespace.com/sitemap.xml. You should see XML with a list of your page URLs. If you see a password prompt, a parking page or an error instead, Google sees the same thing, and that is your fix.

Squarespace documents three situations where there is no sitemap for Google to fetch3:

  • Trial sites and parking pages. Sitemaps aren’t available on either. Publish the site on a paid plan first.
  • Private or password-protected sites. The site availability has to be set to Public for the sitemap to load.
  • A homepage or site-wide password. Squarespace’s Search Console guide says to remove both before you verify, because passwords stop Google indexing your content2.
bash Optional: check the response from a terminal
# Expect a 200 and an XML content type
curl -sI https://www.yourdomain.com/sitemap.xml

# A 301 here means you are testing the non-primary domain.
# Use the URL it redirects to (the Location header) when you submit.

Step 3: make the property match your primary domain

Squarespace serves your site, and your sitemap, on one primary domain. Every other domain you connect redirects to it, and search engines only show the primary. When you connect Search Console through Squarespace, it verifies the primary domain only. So submit the sitemap in a Domain property, which covers www and non-www, http and https, or in the URL-prefix property that matches your primary domain exactly. A sitemap submitted under a property for a different host lists URLs on another domain, which Google reports as URL not allowed.

Squarespace documents the primary-domain redirect and the “search engines only show your primary custom domain” rule on its domains page4, and the primary-only verification in its Search Console guide2. Google defines what each property type covers5. If you aren’t sure which property you have, the Search Console verification guide explains Domain versus URL-prefix and how to add a Domain property with a DNS TXT record.

Step 4: run a live URL Inspection on the sitemap URL

This is the step that tells you the actual reason. Copy the sitemap URL from the Sitemaps report, paste it into the URL Inspection bar at the top of Search Console, click Live test, then expand Page availability. Google's documentation recommends exactly this check. If the live test can fetch the file, the sitemap is reachable, and what is left on Google's list is a transient error, low crawl demand or a manual action. If it can't, the result names the reason, such as a 404 or a block.

Google lists a manual action against the site and low crawl demand as two causes you can’t fix from the sitemap side1. Check the Manual actions report in the same Search Console property. Low crawl demand is common on brand-new sites with few links pointing at them; Google still finds pages through links in that case, so keep the sitemap submitted and keep publishing.

Step 5: resubmit the same URL and recheck in two days

Once the sitemap opens in a private window and the live test passes, submit the same sitemap URL again in the Sitemaps report. Then leave it for another 24 to 48 hours. Squarespace keeps the file up to date on its own: changes usually appear within an hour and can take up to 24 hours, so there's no reason to submit it again every time you publish a page.

The refresh timing is from Squarespace’s sitemap page3. For what the file includes and leaves out, and the normal first-time submission, see the Squarespace sitemap guide. If the sitemap reads fine but pages still aren’t indexed, the site-not-indexed diagnostic is the next stop.