Squarespace to Google Sites - How to Connect Your Domain to Google Sites Step by Step
By Impran M N
Moving your published site to Google Sites while keeping a domain you originally bought through Squarespace involves a specific sequence: publish the Google Site, prove you own the domain, point the right DNS records at Google, and wait for everything to propagate. None of that happens inside Squarespace or Google Sites alone — it's a handoff between the two, and skipping a step is the most common reason people end up staring at an unverified domain. This guide walks through that handoff in order, including what the domain-connection screen actually looks like when verification hasn't gone through yet.
01Publish your Google Site before touching DNS
Google Sites needs a live, published site before it will let you attach a custom domain to it, so finish your pages and hit Publish first. Trying to connect a domain to an unpublished or half-built site just adds a variable to troubleshoot later if something doesn't work, so get the site itself in a state you're happy with before moving on to domain settings.
02Open Custom domains in Site settings
From your published site, open the settings menu and go to Custom domains. This is where Google Sites separates itself from the free `sites.google.com` address — the panel explains plainly that using your own domain means a domain you already own, and that you'll need to verify ownership with your domain provider before it takes effect. There's also a shortcut here to buy a new domain through Google Workspace if you don't already have one, but since the domain already exists on Squarespace, you'll use Connect domain instead.

03Enter your domain and expect the unverified warning
Clicking Connect domain opens a two-part field — a subdomain prefix like www, and your root domain, for example pmntechfix.nl. The moment you enter it and try to continue, Google shows "This domain is not verified.
Please verify your ownership" with a link straight into that flow. This message is expected at this stage, not an error — no domain passes this screen until you've proven ownership, which happens through a TXT record you add in Squarespace's DNS settings, not anything inside Google Sites itself.

04Verify ownership through Google Search Console
Following the verify-ownership link takes you into Google Search Console's domain verification flow, which generates a TXT record containing a unique token. Copy that token exactly, then add it as a new TXT record in your Squarespace domain's DNS settings — found under Domains > DNS/Advanced in the Squarespace dashboard. Once that record is saved and has propagated, Search Console can confirm you control the domain, which unlocks the rest of the Google Sites connection flow.
05Point the domain at Google with a CNAME
With ownership verified, add a CNAME record in Squarespace's DNS settings mapping your www subdomain to ghs.googlehosted.com — this is the record that actually tells browsers where to fetch your Google Site from. For the bare root domain (no www), Google Sites doesn't accept a CNAME the way subdomains do, so the more reliable approach is a 301 redirect from the root to your www address inside Squarespace's domain settings, rather than fighting with apex-record workarounds.
06Wait for propagation and confirm HTTPS
Once the CNAME and any redirect are saved, DNS propagation can take anywhere from a few minutes up to 48 hours depending on your domain's settings and your ISP's caching. If the domain doesn't resolve right away, a DNS lookup tool will show you whether the CNAME has actually taken effect yet rather than leaving you guessing. When it does resolve, visit the domain directly and confirm it loads your Google Site over HTTPS with no certificate warning — Google issues the SSL certificate automatically once the domain mapping is confirmed, but that can lag slightly behind DNS propagation itself.
Frequently asked questions
Do I need to keep my domain registered with Squarespace?
Yes, in this setup the domain stays registered with Squarespace while its DNS records are configured to point to Google Sites — you're not transferring the domain, just redirecting where it resolves.
How long does DNS propagation take after adding the records?
DNS changes can take anywhere from a few minutes to 48 hours to fully propagate, depending on your domain's settings and caching along the way.
Why does Google Sites say my domain isn't verified?
That message appears by default until you complete ownership verification through Google Search Console, usually via a TXT record added to your Squarespace DNS settings. It's an expected step, not a sign something is broken.
Should I point the root domain or the www version at Google Sites?
Google Sites accepts a CNAME for a subdomain like www, but not cleanly for a bare root domain. The common approach is to CNAME www to ghs.googlehosted.com and set up a 301 redirect from the root domain to www.
Will HTTPS work automatically on my custom domain?
Yes, once the domain is correctly verified and DNS has propagated, Google Sites issues and applies an SSL certificate automatically, though it can take a little longer than the DNS change itself to show up.
About the author

Impran M N
I've been hooked on technology for as long as I can remember — especially the new tools and AI apps that seem to land every other week. Easy Tech Tuts is where I write up whatever I've just worked out: I do the task in the real product, record the screen, and turn it into the guide I wish I'd found first.



