How To Change Domain On Squarespace: Complete DNS & Migration Guide

Changing your primary domain on Squarespace requires registering or connecting your target URL within the Domains panel, configuring host-level DNS zone files, and setting the new address as the Primary Domain. This process triggers automated 301 redirects from legacy URLs to preserve link equity and organic search rankings across all indexable routes. Complete DNS propagation and SSL certificate provisioning finalize globally within 24 to 48 hours.

Pre-Migration Checklist & Infrastructure Benchmarks

Before modifying your domain routing settings or altering primary hostname declarations, you must verify administrative privileges and record existing DNS states. Modifying domain mappings without preparing target infrastructure can result in broken SSL handshakes, indexing dropped paths, and service interruptions for integrated email platforms.

Essential Configuration Tools & Permissions

• Squarespace Administrative Privileges: You must hold Owner or Administrator permissions on the target Squarespace site.
• Domain Registrar Console Access: Full access to your domain registrar dashboard (e.g., GoDaddy, Namecheap, Cloudflare, Google Domains/Namecheap) if connecting a third-party domain.
• Active SSL Capability: Unobstructed access to domain zone files to allow automated ACME challenge checks for Let's Encrypt certificate issuance.

Mandatory Technical Standards & Records

• Squarespace IPv4 Cluster Addresses: Four required A records pointing to:
  1. 198.185.159.144
  2. 198.185.159.145
  3. 198.185.159.146
  4. 198.185.159.147
• Verification CNAME Record: Unique 16-character string pointing to verify.squarespace.com.
• Routing Architecture Standard: Permanent 301 redirects mapped automatically by designated Primary Domain switches inside Squarespace's edge routers.

Estimated Execution Benchmarks

• Administrative Setup Time: 15 to 30 minutes.
• DNS Record Propagation Window: 24 to 48 hours globally (standard TTL decay).
• SSL Provisioning Duration: 1 to 24 hours post-propagation.
• Financial Investment: $0 for existing domains; $20 to $70/year for new custom registrations via Squarespace.

Complete Technical Workflow for Swapping Your Squarespace Domain

Follow this precise execution sequence to attach a new web address, map third-party or internal DNS records, elevate the address to Primary status, and execute essential post-migration SEO maintenance.

Step 1: Attach or Purchase the Target Domain in Squarespace

You must first make the target domain visible inside the target Squarespace site dashboard.

1. Log into your Squarespace Account Dashboard and select the target site.
2. In the Home Menu, navigate to Settings, then select Domains (on version 7.1, navigate to Website > Domains).
3. Choose the appropriate acquisition path:
   
   
   • To Buy a New Domain: Click Get a Domain, search for your available target hostname, select your registration duration, enter payment details, and complete purchase.
   • To Connect an External Domain: Click Use a Domain I Own, enter your full custom domain (e.g., yournewdomain.com), and select Connect Domain. Select your domain provider from the drop-down menu or choose Other.
   • To Move a Domain Between Squarespace Sites: If the target domain is already registered through Squarespace on a different site you own, click the domain under your domain management panel, select Move to Another Site, and select your current active website destination.

Step 2: Configure Advanced DNS Zone Files (For External Registrars)

If your domain is managed by a third-party registrar, you must point its DNS zone file to Squarespace’s server infrastructure before the domain can accept web traffic.

1. Open a new browser tab and sign into your third-party domain registrar account.
2. Locate the DNS Management, Name Server, or Zone File Configuration page.
3. Locate existing A and CNAME records and delete any conflicting entries pointing to old hosts, non-Squarespace IP addresses, or placeholder parking pages.
4. Add the verification CNAME:
   
   
   • Type: CNAME
   • Host/Name: Enter the unique 16-character code generated in your Squarespace DNS Settings panel.
   • Record/Target: verify.squarespace.com
   • TTL: 300 seconds (or 1 Hour / Automatic)
5. Add the primary routing CNAME:
   
   
   • Type: CNAME
   • Host/Name: www
   • Record/Target: ext-cust.squarespace.com
   • TTL: 300 seconds (or Automatic)
6. Add the four core A Records to route root apex traffic:
   
   
   • Type: A | Host/Name: @ (or leave blank depending on registrar) | Value: 198.185.159.144
   • Type: A | Host/Name: @ | Value: 198.185.159.145
   • Type: A | Host/Name: @ | Value: 198.185.159.146
   • Type: A | Host/Name: @ | Value: 198.185.159.147

Warning: Do not delete MX (Mail Exchange), TXT (e.g., SPF, DKIM, DMARC), or SRV records associated with active custom email hosts like Google Workspace or Microsoft 365. Purging email records will instantly halt incoming and outgoing inbox delivery.

Step 3: Promote the Target URL to Primary Domain Status

Once DNS settings show an "Active" or "Connected" status in Squarespace, change the primary domain assignment.

1. Return to the Squarespace Domains panel (Settings > Domains).
2. Locate the list of connected domains under the Domains Managed by Squarespace or Third-Party Domains sub-headings.
3. Click on the domain name you wish to establish as the main public web address.
4. Click the Set as Primary Domain button at the top of the context menu.
5. Confirm the selection when prompted.

Pro-Tip: Keep your old custom domain attached to the site under the Secondary Domains list. Squarespace automatically executes edge-level 301 redirects from all Secondary Domains to the Primary Domain, ensuring that existing backlink equity and indexed URLs automatically resolve to the new address without custom URL mapping rules.

Step 4: Validate SSL Certificate Generation & Force Secure HTTPS Settings

Every primary domain assignment requires a valid SSL certificate to avoid browser security warnings (ERR_CERT_COMMON_NAME_INVALID).

1. In the main menu, navigate to Settings > Advanced > SSL.
2. Under Certificate Status, confirm the system displays Active. If it reads Pending, allow up to 24 hours for automated domain ownership verification and certificate issuance.
3. Under Security Option, select Secure (Preferred). This forces HTTP requests to instantly rewrite to encrypted HTTPS strings.
4. Ensure HSTS Secure is enabled if your site requires strict transport security compliance.

Step 5: Execute Post-Domain Migration SEO Realignment

Changing your domain changes your canonical URL structure across search indexes. Perform these post-launch SEO steps immediately to avoid traffic drops:

1. Google Search Console Change of Address: Log into Google Search Console using your verified property. Select your old domain property, go to Settings > Change of Address, and enter your newly verified primary domain.
2. Submit Updated XML Sitemaps: Open your new domain’s Search Console property and submit your main XML index file: https://yournewdomain.com/sitemap.xml.
3. Update External Integrations: Re-authorize third-party APIs, OAuth integrations, payment gateway callback URLs (e.g., Stripe, PayPal), and web analytics properties (e.g., Google Analytics 4 Data Streams).

Domain Connection Parameters & Technical Specifications

The following reference table outlines the exact DNS records and protocols required to successfully change and bind custom domains on the Squarespace platform architecture.

Technical Failures & DNS Resolution Remedies

Scenario 1: Domain Status Displays "Record Issue" or "Connection Incomplete"

• Root Cause: Conflicting legacy A/AAAA records exist at the registrar level, or the unique CNAME verification string was mistyped.
• Actionable Fix: Open your external registrar's DNS zone file manager. Remove all pre-existing A records pointing to legacy web hosts (such as WordPress hosting, Wix, or Shopify). Search for and delete all AAAA (IPv6) records, as Squarespace does not utilize IPv6 AAAA records for custom domain routing. Double-check the 16-character verification string for capitalization errors and save changes.

Scenario 2: SSL Certificate Stuck in "Pending" for Over 24 Hours

• Root Cause: A CAA (Certification Authority Authorization) record at your registrar restricts SSL issuance, or DNS records haven't fully propagated globally.
• Actionable Fix: Inspect your domain's zone file for CAA records. If CAA records are present, add a record explicitly allowing Let's Encrypt to issue certificates: set Tag to issue and Value to letsencrypt.org. Alternatively, remove all CAA restrictions. Once updated, navigate to Settings > Advanced > SSL in Squarespace, switch the setting to Insecure, wait 5 minutes, and switch it back to Secure to re-trigger the automated provisioning process.

Scenario 3: Secondary Domain Access Displays "404 Not Found" or Circular Redirects

• Root Cause: The legacy domain was completely disconnected or removed from the site's dashboard instead of being retained as a secondary domain, breaking dynamic edge redirects.
• Actionable Fix: Do not remove the old domain from your Squarespace account. Ensure the old domain remains attached under Settings > Domains. As long as it appears in the list alongside your Primary Domain, Squarespace's web server will catch all requests to the legacy domain and issue standard 301 redirects to the corresponding path on your new primary domain.

Scenario 4: Custom Email Service Stops Working After Domain Switch

• Root Cause: MX, SPF, DKIM, or DMARC records were altered or deleted during the DNS zone clean-up phase at your third-party registrar.
• Actionable Fix: Log into your email hosting admin console (e.g., Google Workspace Admin or Microsoft 365 Admin Center) to retrieve your specific MX and TXT record values. Re-enter the primary MX records (e.g., 10 ASPMX.L.GOOGLE.COM) and restore TXT records containing your v=spf1 string and DKIM selectors. These records run parallel to Squarespace's website routing records and must remain intact.

Frequently Asked Questions

Will changing my domain on Squarespace break my existing email accounts?

Changing your primary website domain does not affect custom email services if you leave your MX and TXT (SPF/DKIM) records intact in your DNS zone file. However, if your target domain is completely new, you will need to provision a new email account or alias configured specifically for that new hostname.

How long does it take for a new Squarespace domain to start working globally?

While internal settings within the Squarespace interface update instantly, global DNS propagation requires between 24 and 48 hours. Most major internet service providers (ISPs) and local caches refresh their DNS tables within 2 to 6 hours, during which time some visitors may still land on the old domain.

Do I lose my search engine rankings when changing domains on Squarespace?

You can minimize organic search ranking loss by leaving your old domain connected to your Squarespace site as a Secondary Domain. Squarespace automatically sets up 301 permanent redirects from the old domain to the new primary domain, passing link equity and guiding search crawlers to the new canonical URLs.

Can I move a domain registered through Squarespace to another Squarespace site?

Yes. Open the site dashboard where the domain currently resides, navigate to Settings > Domains, click the target domain, and scroll to select Move to Another Site. Select your destination website from your account list to instantly transfer management without altering underlying DNS configurations.

Should I delete my old domain after setting a new primary domain on Squarespace?

No, you should not delete your old domain immediately. Maintain ownership of your old domain and leave it linked as a Secondary Domain on your Squarespace site for at least 12 months. This maintains legacy backlinks, preserves direct bookmark traffic, and allows search engines time to fully index the new domain structure.

Optimize Your Website Migration Architecture

Transitioning your web infrastructure requires strict adherence to DNS protocols and search engine index management to prevent traffic loss. Implement these technical configurations today to safely migrate your primary domain and maintain unbroken brand authority.