Skip to content

Redirects · Fix

Redirect www to non-www (or back) on Squarespace

Published 4 named sources

You don’t write a redirect rule for this. Squarespace sends every connected domain to one primary domain with a 3012, and a single toggle in the Domains panel decides whether that primary uses www3. Set the primary domain, set the toggle, wait up to 48 hours, then test it with one curl command. URL Mappings can’t do this job, because its rules only take a path, never a domain name1.

The five steps below take about five minutes of work plus the processing wait. The last section covers what to change in Search Console once the switch is live.

Steps at a glance

  1. Pick one version
  2. Set the primary domain
  3. Set the www toggle
  4. Allow 24 to 48 hours
  5. Test the redirect
Jump to the fix

Rather not touch code? We fix duplicate www and non-www versions as part of the $299 install. Start my setup 

Why URL Mappings can't redirect www

URL Mappings redirects one path to another on domains already connected to your site. Squarespace's help page says the domain name is removed from a rule and only the URL slug is needed, and that you can only redirect from built-in and custom domains connected to the site. A rule can't say 'when the host is www, go to the bare domain'. Host-level redirects are handled by the primary-domain setting instead, which Squarespace applies to every connected domain automatically.

Both quotes are from Squarespace’s URL mappings page1. For the path-to-path redirects URL Mappings does handle, see the URL Mappings format reference.

Step 1: pick www or non-www, once

Either version works for search, as long as the site answers on one of them and the other redirects to it. Squarespace's default is www: when someone types the bare domain, the address updates to www.yourdomain.com. If you have no reason to change, keep the default. If the brand is printed without www everywhere, switch to the bare domain now, before more links point at the www version.

The default behaviour is described on Squarespace’s www page3. One trap: Chrome hides “www” in the address bar, so what you see in Chrome isn’t proof of which version is live. Squarespace points this out on the same page. Step 5 shows how to check properly.

Step 2: set the primary domain in the Domains panel

Open the Domains panel, click the menu next to the domain you want, choose Set as primary domain, pick the domain or subdomain in the dropdown and click Set. For a domain managed by a third party, click the domain under Domains managed by a third-party and choose Set as primary domain. Every other custom domain on the site then redirects to the primary with a 301, and search engines show only the primary.

Steps and behaviour are from Squarespace’s primary-domain page2, which also notes that the first custom domain you add becomes primary automatically. If you connected an old domain after a rebrand, check that the new one is the primary.

Step 3: switch the www prefix on or off

In the Domains panel, the Use www prefix toggle on the primary domain decides which version is live. Switch it off to make yourdomain.com the address and send www to it. Leave it on to keep www.yourdomain.com and send the bare domain to it. Squarespace only lets you remove www on domains pointing to a Squarespace site, so a domain whose DNS points somewhere else has to be connected properly first.

The toggle and its limits are documented on Squarespace’s www page3.

Step 4: allow 24 to 48 hours

Squarespace says a change to a domain's www setting can take between 24 and 48 hours to process. Until then, either version may still load directly. Don't add URL Mappings rules to force it in the meantime; they can't match a hostname, and they'll stay in the panel after the switch completes.

Processing time is from Squarespace’s www page3. A third-party domain that was connected recently can need up to 48 hours before it can be set as primary at all2.

Step 5: test the 301 with a path, not just the homepage

Request the version you are not using, with a real page path, from a terminal. You want one 301 whose Location header is the same path on your primary version, then a 200 on that URL. Test a deep page as well as the homepage. Squarespace's help page says the redirect from other domains goes to the root domain only, so the path is worth checking on your own site. On two live Squarespace sites we tested on 6 October 2026, both the www redirect and a secondary-domain redirect kept the full path.

bash Check both versions with a real page path
# The version you are NOT using, with a path
curl -sI http://yourdomain.com/about
# Expect: HTTP 301, Location: https://www.yourdomain.com/about

# Follow it to the end
curl -sIL http://yourdomain.com/about
# Expect: one 301, then HTTP 200 on the primary URL

The root-only wording is on Squarespace’s primary-domain page2. If your test does land on the homepage instead of the same page, map the important old paths with URL Mappings 301 rules on the primary domain.

What to change in Search Console afterwards

If you use a Domain property, nothing: it already covers www and non-www, http and https. If you use a URL-prefix property, it covers one exact prefix, so add a property for the version you switched to and submit the sitemap there. Squarespace's sitemap uses the primary domain, so a sitemap submitted under the old prefix will point at URLs on a different host.

Property coverage is defined in Google’s Search Console help4. The Search Console verification guide covers adding a Domain property with a DNS TXT record. If the sitemap then shows an error, see fixing a Couldn’t fetch sitemap.