Skip to content
50% OFF $299 $599
Lock in
§ 2.2.1 ARTICLE
Published VerifiedEvery 6 weeks Sources5 named Authored bySquareRank Team

Indexing · § 2.2.1 · How-to

The Squarespace sitemap.xml file

Squarespace auto-generates /sitemap.xml on every site3. The file lists every published, indexable page — standard pages, blog posts, product pages, collection items — and omits noindex pages, password-protected pages, and pages on disabled sites automatically. You cannot edit it by hand. The owner action is one-time: verify your Search Console property, submit sitemap.xml once, let Google re-fetch on its own cadence4.

This leaf covers where the file lives, what gets included and what gets omitted, the submission workflow for Google Search Console and Bing Webmaster Tools, how often Squarespace refreshes the file, and the four gotchas that catch first-time owners.

What sitemap.xml actually is

A sitemap is an XML file listing every URL on your site you want search engines to know about. The format is standardised — each entry includes a <loc> tag with the URL, optionally a <lastmod> timestamp, and rarely-used <changefreq> and <priority> fields. Google ignores <changefreq> and <priority> in practice; <lastmod> is honoured if accurate. The format limit per Google: 50,000 URLs and 50 MB uncompressed per file; sites larger than that need multiple sitemaps and a sitemap-index file.

Google's sitemap documentation1 describes the format requirements in detail. The good news on Squarespace: you don't have to know any of them. Squarespace generates the file in the correct format, with valid XML, valid URL entries, and accurate <lastmod> timestamps automatically. Your job is to submit it to Search Console and check the result.

XML What Squarespace's sitemap.xml looks like, abbreviated 
 <?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <url> <loc>https://yoursite.com/</loc> <lastmod>2026-05-18T12:34:56Z</lastmod> </url> <url> <loc>https://yoursite.com/about</loc> <lastmod>2026-05-12T09:21:00Z</lastmod> </url> <!-- ...and so on for every indexable page on the site --> </urlset>

Where the sitemap lives on Squarespace

The file is always at yoursite.com/sitemap.xml — no exceptions, no settings to change. Open it in a private browser window to confirm. The path is hard-coded by the platform; there's no way to move it, rename it, or split it into multiple files. The file is served by Squarespace's CDN, with the correct application/xml content type and a 200 OK status. If yoursite.com/sitemap.xml returns 404 or redirects unexpectedly, the site itself is misconfigured — check that the site is published, not on a development URL, and not password-protected sitewide.

The same path applies to subdomains and custom domains: if your site lives at blog.yourcompany.com via Squarespace, the sitemap is at blog.yourcompany.com/sitemap.xml. Each Squarespace site is its own property in Search Console, so subdomain sites need their own Search Console verification and their own sitemap submission.

What is included, what is omitted

Included: standard pages, blog posts (after they are published, not while in draft), product pages, collection items (portfolio entries, events, etc.), and gallery pages. Omitted: pages marked 'Hide this page from search results' (Page Settings > SEO), pages and collections that are password-protected, drafts and scheduled-future-publish content, the search results page (most templates noindex it by default), and pages on a site set to 'Block search engines' sitewide. Squarespace's help center describes the same scope.

The platform's logic is simple: if a page should appear in Google, it's in the sitemap; if it shouldn't, it isn't. Owners do not manually mark sitemap inclusion — it follows the noindex setting automatically3. The implication: to remove a page from the sitemap, mark it noindex via Page Settings > SEO. The sitemap regenerates within seconds.

Submitting the sitemap to Google Search Console

Three steps: (1) verify the Search Console property using DNS TXT, HTML meta tag, or Google Analytics / GTM (HTML file upload does not work on Squarespace). (2) In Search Console, open Sitemaps in the left sidebar. (3) Type 'sitemap.xml' in the input box and click Submit. The Sitemaps panel updates within minutes to hours with a 'Success' status and the count of URLs discovered. Google then fetches the file periodically and re-crawls URLs whose <lastmod> timestamps have changed since the last fetch.

Google's documentation4 notes that submission is a one-time action. You do not need to re-submit when new pages are added — Squarespace updates the sitemap automatically, and Google re-fetches it on its own cadence. The exception is large-scale changes (a site migration with hundreds of new URLs), where forcing a re-fetch can shorten the discovery timeline by hours to days.

What the sitemap submission actually does

1 time

submission needed. Squarespace auto-updates the file; Google re-fetches on its own cadence.

Google Search Central · 2025-12-10
50,000

URL limit per sitemap file per Google's spec — well above what any Squarespace site needs.

Google Search Central · 2025-12-10
Auto

Squarespace sitemap regeneration when pages are added, edited, or marked noindex.

Squarespace Help · 2026

How often Squarespace refreshes the sitemap

Squarespace updates the sitemap in near-real-time when a page is added, edited, published, removed, or has its noindex setting changed. The <lastmod> timestamps on individual URL entries reflect the actual last-edit time of each page. Google re-fetches the sitemap on its own cadence — typically every few days for active sites, weekly to monthly for less-active ones. There is no Squarespace setting that controls the refresh; it happens automatically.

The implication: you cannot game Google's crawl schedule by “refreshing” the sitemap. The file refreshes when content changes; nothing else triggers it. The fastest way to get Google to recrawl a specific page is the URL Inspection → Request Indexing flow in Search Console, which works regardless of when the sitemap was last regenerated.

Can you edit the Squarespace sitemap by hand?

No. The sitemap is generated by Squarespace's backend and served from the CDN; there is no setting, no plugin, no developer mode option to author a custom sitemap.xml. The platform constraint is identical to the constraint on /robots.txt, /llms.txt, and other root-level files. The only owner-side levers are the inputs: which pages are published, which are noindex, which are password-protected. Change those and the sitemap updates.

The workaround for cases where you genuinely need a different sitemap structure — very rare on a typical Squarespace site — is the URL Mappings + page-based approach described in the AI search pillar's llms.txt cluster. The same pattern (build a page, redirect a path to it) can serve a sitemap-shaped XML document — but the result would not be Google-validated, and the platform's auto-generated /sitemap.xml would still serve at the canonical URL.

Four Squarespace-specific sitemap gotchas

First: the sitemap reflects current settings — checking 'Hide this page from search results' on a page that was previously indexed will remove it from the sitemap, but Google's index may take 2-6 weeks to recognise the removal. Second: site-wide 'Block search engines' in Settings > Crawlers does not blank the sitemap, it just emits noindex sitewide — confusing because the sitemap still exists. Third: password-protected pages are omitted, but Squarespace's behaviour with member-area pages varies by template. Fourth: pages on a development URL (yoursite.squarespace.com) before custom domain DNS propagates are not in the sitemap at the production URL.

The most common owner mistake: marking pages noindex during development, then forgetting to un-mark them at launch. Two weeks after launch, an owner discovers the homepage and three flagship pages have been invisible to Google the whole time — because they were noindex when launched, they never made it into the sitemap. The fix is unchecking the box; Google's index then picks them up over the following days.

Keep reading · § 2.2.1