# How Do I Use a Custom Domain With Google Sites?

Canonical: https://figment.so/blog/google-sites-custom-domain

Open Settings, click Custom domains, and follow the setup. You verify ownership through Search Console, and the address must include a subdomain such as www. DNS changes can take up to 48 hours.

**To use a custom domain with Google Sites, open your site's Settings, click Custom domains, and follow the setup flow, which verifies through Google Search Console that you own the domain.** You need a domain you already own, and the address must include a subdomain such as `www`. Google says DNS changes "may take up to 48 hours" to become visible.

## How do I connect a custom domain to a new Google Site?

Follow these steps from Google's help center:

1. In your site, click **Settings**.
2. Click **Custom domains**.
3. Click **Start setup** and enter your domain.
4. If prompted, verify that you own the domain.
5. Click **Next** and follow the instructions for your domain registrar.
6. Click **Done**.

([Google Sites Help, "Use a custom domain for your site"](https://support.google.com/sites/answer/9068867?hl=en))

Google states that "only the owner of a site can connect it to a domain." A collaborator with edit access cannot add a domain unless they are also the owner. The instructions in step 5 depend on your registrar, because they are DNS changes on a system Google does not control.

## How does domain verification work?

Verification runs through Google Search Console, not through Sites. You add a TXT record to your domain's DNS settings, using the value Search Console gives you, so Google can confirm you control the domain. For this step, Google directs you to "follow the instructions for 'Any DNS Provider'," so it works with any registrar. Finish verification first, because a site cannot connect to a domain it has not confirmed you own.

## What DNS records does Google Sites need, and how long does it take?

Besides the verification TXT record, the domain needs a DNS entry that points traffic at Google's Sites servers. Google's troubleshooting section calls out a CNAME entry. After you update DNS, Google states: "It may take up to 48 hours for changes to your domain to become visible on the Internet." If the domain does not resolve after a few minutes, that is expected.

There is also a rate limit: "there is a limit of 20 mappings made per week for your URL." If you add, remove and re-add domains while testing, you can hit that limit and have to wait out the week.

## How many custom domains can one Google Site have?

Up to five. Google's help page says you can "connect up to five custom domains to one site."

## Can I use a bare (root) domain, or do I need www?

Plan on a subdomain such as `www`. Google's error documentation states, "Your URL must include a subdomain, like 'www'." The self-serve flow above expects `www.yourdomain.com`, not a bare `yourdomain.com`.

Google Workspace documents a separate bare ("naked") domain setup for sites managed through a Workspace **admin console**. It is an admin-level flow, not the Settings panel above. It has a prerequisite: "For your naked domain address to work, you must already host your Google Site at www.example.com." It also has a limit that matters if you need HTTPS: "Address mapping is supported only by HTTP and not HTTPS" for that redirect ([Google Workspace Admin Help, "Set up the naked domain address for your site"](https://knowledge.workspace.google.com/admin/getting-started/set-up-the-naked-domain-address-for-your-site)). Most sites should run on HTTPS, so use `www.yourdomain.com` as the primary address. If you want the bare domain to redirect, set that up through your DNS provider or registrar if they offer it, not through this Google feature.

## What do Google's error messages mean?

Google's help page documents these messages and fixes:

| Error | What it means | Fix |
| --- | --- | --- |
| Invalid DNS | The DNS record Google expects isn't there yet or doesn't match | Add the CNAME entry Google specifies; if you already updated DNS, wait 24–48 hours and try again |
| The URL check failed | The domain didn't pass Google's validation | Change the URL and try again |
| This isn't a valid URL | Typo, or the URL is missing a subdomain | Confirm the full address, with no typos, and include a subdomain like "www" |
| This URL is already in use by another Google service | The address is already mapped to another service such as Blogger, Google Sites, or App Engine | Delete the existing mapping in that service, then assign the address again, or use a different subdomain |

(Google Sites Help, "Use a custom domain for your site")

## What should I check before I start?

- **You are the site owner**, not just an editor. Only the owner can add a domain.
- **You have registrar access.** You need to add DNS records at whatever service manages your domain's DNS.
- **You plan on "www"**, not a bare domain, unless you are using the separate Workspace admin-console flow and accept its HTTPS limit.
- **You can wait up to 48 hours** after DNS changes before troubleshooting. An "Invalid DNS" message right after you save a record is often propagation delay.
- **You are not retesting the same domain too often.** Google caps mappings at 20 per week per URL.

## What if it still won't connect?

Re-check the exact DNS record type and value Google's setup flow showed you. The most common causes of an "Invalid DNS" message that does not clear after 48 hours are a CNAME with an extra character, a missing verification TXT record, or a record added at the wrong subdomain. If the address is already mapped to another Google service, Google's fix is to delete that mapping first. If the mapping is not yours to delete, use a different subdomain.

## What if I am moving off Google Sites instead?

That is a larger project. Start with the [Google Sites alternatives guide](/blog/google-sites-alternatives) to choose a replacement, then check what Google Sites lets you export in our [export capability matrix](/blog/export-your-website-from-a-website-builder). Keep a copy of the domain's current DNS records until the new site works, and read [redirects when changing website builders](/blog/redirects-when-changing-website-builders) before you point the domain elsewhere.
