Connect a Squarespace or Google Domains domain to ScaleEdges

Use this guide when your domain is registered with Squarespace Domains. This includes domains that were registered with Google Domains, which moved to Squarespace. Your domain must use the Squarespace nameservers: when it uses custom nameservers, Squarespace does not let you edit its DNS, and you must add the records with the company that runs those nameservers. See Find where your DNS is managed.

Step 1: Get your records in ScaleEdges

In your ScaleEdges dashboard, open Settings and select the Storefront tab.
In the Custom domain card, enter your domain in Domain you own, for example shop.yourbrand.com or yourbrand.com.
Select Connect domain and wait for the DNS records to add table.
Keep this tab open. You will copy the Type, Name / host and Value of each row.

ScaleEdges shows a CNAME record for a subdomain, an A record for a root domain, and sometimes a TXT verification record.

Step 2: Open the DNS settings in Squarespace

Open your Squarespace domains dashboard and sign in.
Select the domain you want to connect.
Select DNS, then DNS settings.

The DNS settings are organized in sections. Squarespace Defaults contains the records that connect your domain to a Squarespace website, other presets can contain your email records, for example for Google Workspace, and Custom Records contains the records you add yourself.

Step 3: Decide whether to keep the Squarespace Defaults

You connect a subdomain, such as shop.yourbrand.com: keep the Squarespace Defaults. Your Squarespace website stays on yourbrand.com and www.yourbrand.com, and your store uses the subdomain.
You connect the root domain or www: delete the Squarespace Defaults with the red trash icon, then confirm. Squarespace explains that a domain cannot point to another site while these defaults are in place. This disconnects your domain from any Squarespace website.

Never delete the presets and records used by your email, such as Google Workspace or MX records.

Step 4: Add the records

All records are added in Custom Records with Add record. Each record has a Type, a Name, a TTL and a Data field. Leave Priority empty, as it is only used by some record types, such as MX.

For a subdomain (CNAME)

In Custom Records, check that no A, AAAA or CNAME record already uses the same name, for example shop. Delete it if needed.
Select Add record.
Set Type to CNAME.
In Name, enter only the subdomain, for example shop.
In Data, paste the Value shown in ScaleEdges.
Keep the default TTL and save the record.

For a root domain (A)

After deleting the Squarespace Defaults, check that no other A, AAAA or CNAME record remains on @.
Select Add record.
Set Type to A.
In Name, enter @.
In Data, paste the IPv4 address shown in ScaleEdges.
Keep the default TTL and save the record.

At the end, @ must have exactly one A record, with the address shown in ScaleEdges, and no AAAA record.

If ScaleEdges shows a TXT record

Select Add record and set Type to TXT.
In Name, enter the part of the name before your domain, usually _vercel.
In Data, paste the value shown in ScaleEdges. It starts with vc-domain-verify=.
Save the record. Keep your other TXT records, such as SPF or Google verification.

Step 5: Check the configuration

Return to Settings → Storefront → Custom domain in ScaleEdges.
Select Check DNS configuration.
When the status changes to Configuring HTTPS, wait a few minutes, then check again.
When the status shows Active, select Open domain to view your store.

The default TTL of custom records at Squarespace is 4 hours, and Squarespace indicates that DNS changes can take 24 to 48 hours to work everywhere. They are often visible much sooner. HTTPS is activated automatically by ScaleEdges.

Troubleshooting

The status stays on Waiting for DNS: make sure the Squarespace Defaults were deleted if you connected the root domain or www, and that the Name field contains only shop, not shop.yourbrand.com.
You cannot edit the DNS: your domain uses custom nameservers. Add the records with the company that runs them.
The status stays on Configuring HTTPS: if your DNS contains CAA records, one of them must allow letsencrypt.org.
Redirecting www: a store uses one custom domain. If you connected the root domain, www no longer points anywhere once the defaults are deleted. You can connect www instead, or redirect it to your connected domain with a forwarding service, then test it with http:// and https://.

For every other situation, read Custom domain troubleshooting.