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.
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.
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.
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.
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.
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.