Connect your domain at Squarespace
Add the certificate and website records in Squarespace Domains (including domains moved from Google Domains), with an ALIAS for your root domain.
Provider steps checked November 18, 2026. Provider dashboards change; if a button has moved, the official help links at the bottom have the current wording.
You’ll add two or three records in your Squarespace account: one that proves you own the domain, and the ones that point it at your site. It takes about 10 minutes, it can be undone, and it doesn’t touch your email.
Your Staticbot deployment page shows the exact values to paste, with a copy button next to each, and checks whether Squarespace is already answering with them. Keep it open next to this guide.
Before you start
- If the domain still has the “Squarespace Defaults” preset (it connects the domain to a Squarespace site), delete it: DNS → DNS Settings → trash icon next to Squarespace Defaults.
- Turn off DNSSEC (DNS → DNSSEC) before adding the ALIAS record.
Open the DNS records at Squarespace
- Open your Squarespace domains dashboard and click the domain.
- Click DNS, then DNS Settings.
- Scroll to Custom Records and click Add record. Squarespace asks for your password or 2FA.
Name and Data are Squarespace’s names for the two boxes you fill in. Type only the part before your domain. Use @ for the domain itself. Squarespace doesn’t allow a CNAME on @; the root uses ALIAS.
Server-rendered app hosted on Cloudflare? Its deployment page lists TXT records and a CNAME on www pointing at apps.staticbot.app instead of the records below. Add them in the same form, with the same Name rule.
Step 1: Add the certificate record
This record lets Amazon issue the HTTPS certificate for your domain. It doesn’t change where your site or email points. Add one record per certificate record shown on the deployment page:
Save, then go back to the deployment page and click Check my records. Staticbot asks Squarespace’s own servers, so you see the answer within seconds. Once it shows Found, the certificate is usually issued within a few minutes.
Step 2: Point your domain at your site
The deployment page shows these records once the certificate is issued. If your site lives on a subdomain such as app.yourdomain.com, you only add one CNAME for it.
For yourdomain.com (the domain itself):
For www.yourdomain.com:
- Google Domains moved its domains to Squarespace. If you bought your domain at Google Domains, this is your guide.
Check it worked
The deployment page checks each record and tells you what it sees: Found, Not found yet, Wrong value, or Domain typed twice (the domain was typed into the Name box). Most records show up within a minute. Your browser may keep showing the old page for a while after that; a private window shows the new one sooner.
Working with an AI agent connected to Staticbot? Ask it whether your DNS records are live; it runs the same check.
Common problems at Squarespace
- Squarespace says it can’t save the record
- Another record or a forwarding rule uses the same name. Remove it (or the Squarespace Defaults preset) and try again.
Advanced: change nameservers instead
Instead of adding records, you can point the domain’s nameservers at Staticbot. You then add no records at all: the certificate and the site, the domain itself included, are set up automatically.
It’s the right choice when you don’t use the domain for anything else yet: no email on it, no other subdomains. The deployment page recommends it in that case. If the domain has email, Staticbot copies the email records it can see on the domain itself before you switch; records on other names (such as blog.yourdomain.com or email signing keys) have to be re-created, so adding records is usually the safer route there. The deployment page only offers the switch when it’s safe to.
At Squarespace:
Open the domain, go to DNS → Domain Nameservers, click Use Custom Nameservers, confirm with your password or 2FA, accept turning off DNSSEC, enter the Staticbot nameservers and save.
Once custom nameservers are active, records in the Squarespace DNS panel no longer apply.
More about what moves and what to check: changing nameservers.
