Google Sites serves only an address with a subdomain, such as www: point it with a CNAME to ghs.googlehosted.com after verifying the domain in Search Console. The bare root cannot host the site — Google Workspace customers can redirect it to www with Google’s A records, and everyone else with their registrar’s forwarding.
The records to add
| Name | Type | Value |
|---|---|---|
www | CNAME | ghs.googlehosted.com |
@ | TXT | google-site-verification=… (Search Console) |
@ | A | 216.239.32.21, 216.239.34.21, 216.239.36.21, 216.239.38.21 — optional: Workspace’s redirect to www |
Google Workspace’s root redirect works over HTTP only, not HTTPS. Keep the verification TXT record in place — Search Console keeps checking it.
| Root domain | Cannot host the site — redirect it to www |
| Limits | 5 custom addresses per site, 20 new mappings a week |
Check your domain
Enter your domain: we look up its records and compare them with what Google Sites expects — the root, www, and any record left over from before.
Step by step
- Verify the domain in Google Search Console with its TXT record.
- At your DNS host, add a CNAME for www to ghs.googlehosted.com.
- In Google Sites, open Settings → Custom domains and add www.example.com.
- For the root, set up forwarding to www — at the registrar, or with Google Workspace’s redirect.
The certificate
Google supplies the certificate automatically; you cannot bring your own. A CAA record must allow Google’s authority (pki.goog) — the live sites use Google Trust Services. If a site shows no certificate, remove the custom address and add it again.
Common mistakes
- Entering the bare domain — “This isn’t a valid URL”.
- An address already used by Blogger or App Engine.
- A CAA record that blocks Google.
Sources
Records checked on 26 September 2026 against these official sources:
- Use a custom domain for your site — support.google.com
- Map a new URL to a site in Google Sites — knowledge.workspace.google.com
- Configure A records — knowledge.workspace.google.com