How To Connect Squarespace Domain To Google Sites 2026 Easily

Start from the Sites project you want the domain attached to. The editor is where you build the site, and the custom domain option sits in the settings menu next to Publish in the top right. Get the site into a publishable state first, even a basic homepage, since Google won't let you finish attaching a domain to a project that has nothing published yet.

Open Set up custom domain and type your domain into the two fields: a subdomain prefix like www, and the root domain itself, for example pmntechfix.nl. Google's own help documentation is specific about the first field: your URL must include a subdomain such as www, because Google Sites has no way to map the bare root domain (pmntechfix.nl with nothing in front) directly.

Click through toward Next and Google checks whether it can confirm you own the domain. On one that hasn't been verified yet, you'll see a red message under the fields reading "This domain is not verified.

Please verify your ownership," with a link that starts the actual verification step. That's expected on a first attempt, not an error in what you typed.

Clicking "verify your ownership" opens Search Console's verification flow for that exact domain. Google recommends the TXT record method by default: it generates a unique string starting with google-site-verification= that you copy, then paste into a new TXT record in your domain's DNS settings.

The dialog lists four steps in order: select the record type, sign in to your domain provider, add the record, then come back and press Verify. Leave this Search Console tab open while you make the DNS change, since you'll need it again to finish confirming.

In Squarespace, open the domain, click DNS, then DNS Settings, and scroll to Custom Records. Click Add record, then enter your password, or complete two-factor authentication if it's turned on; Squarespace requires that reauthentication before it lets a custom record through.

Set Type to TXT. Squarespace auto-fills the Name field with your own domain, so where Search Console's instructions tell you to put your bare domain as the host, leave the default in place or enter @ instead of retyping the full name.

Paste the google-site-verification string into the value field exactly as given; a trimmed or altered value won't verify. Save, then return to the Search Console tab and click Verify. If it doesn't confirm right away, that's normal: Search Console notes it can take up to 48 hours to pick up a new record.

Verification only proves ownership; it doesn't route traffic. Back in Google Sites, finishing the custom domain setup shows you a CNAME record to add.

Because Google Sites only maps to a subdomain such as www, this CNAME is the only routing record Google gives you here, not an A record for the root domain. Add it in the same Squarespace Custom Records screen, alongside the TXT record from the previous step.

If you also want pmntechfix.nl to load the site with no www in front, that's not something Google Sites' own setup handles. It needs a separate domain forwarding rule in Squarespace, pointing the root domain at the www version.

DNS changes spread across the internet gradually, so it's normal for the domain to keep resolving to its old destination for a while after you save the records. Google's documentation puts the window at up to 48 hours, though it's often quicker.

Once propagation catches up, load your domain directly in a browser and confirm it lands on your Google Sites content instead of a Squarespace placeholder page. If the site loads but the browser flags a certificate warning, Google Sites' help pages describe this as a known state: a missing-certificate error on the custom URL, fixed by removing the custom URL from the site and assigning it again, not by changing anything in DNS.