Updated: September 2026
Connecting a custom domain to Blogger is usually simple once the DNS records are correct.
The frustrating part is that one small mistake can break the entire setup.
A missing security CNAME can prevent Blogger from accepting the domain. Incorrect A records can stop the naked domain from redirecting. Conflicting DNS records can cause HTTPS problems, and SSL certificates may take time to become available after the DNS changes are made.
This guide explains the complete Blogger custom-domain setup, including the correct CNAME records, root-domain A records, HTTPS settings and a troubleshooting checklist for the most common failures.
Quick Setup Summary
For a typical Blogger custom domain such as www.example.com, you need:
- A CNAME for www pointing to ghs.google.com
- A second security CNAME generated specifically for your Blogger account
- Four Google A records for the root domain if you want example.com to redirect to www.example.com
- HTTPS Availability and HTTPS Redirect enabled after the domain is working
How Blogger Custom Domains Work
Blogger continues hosting the website, but visitors use your own domain instead of the original Blogspot address.
For example:
yourblog.blogspot.com
can become:
www.example.com
Your DNS provider tells browsers that the custom domain should point to Google's Blogger infrastructure.
Blogger then associates that domain with your specific blog.
Why Blogger Uses a Subdomain Such as WWW
Blogger's custom-domain setup requires a hostname such as:
- www.example.com
- blog.example.com
- news.example.com
Google's Blogger settings documentation notes that Blogger custom domains are hosted on a subdomain rather than directly on the naked domain.
You can then redirect the root domain:
example.com
to:
www.example.com
Step 1: Add the Custom Domain in Blogger
Open:
Blogger → Settings → Publishing → Custom domain
Enter the full hostname you want to use.
Example:
www.example.com
Then click Save.
If the DNS records do not exist yet, Blogger normally displays an error containing the CNAME records you need to create.
Step 2: Create the Main Blogger CNAME
The first CNAME normally points your chosen subdomain to Google's Blogger service.
| Type | Name / Host | Target / Destination |
|---|---|---|
| CNAME | www | ghs.google.com |
If you are using another subdomain such as blog.example.com, the host value would normally be blog instead of www.
Step 3: Add the Security CNAME
This is the record many users accidentally skip.
Blogger provides a second CNAME containing unique values for your blog and Google account.
It may look conceptually like this:
| Type | Name / Host | Target / Destination |
|---|---|---|
| CNAME | Unique value from Blogger | Unique Google destination from Blogger |
Do not copy another website's security CNAME.
The values are specific to your own Blogger setup.
Copy them exactly as Blogger displays them.
Step 4: Add the Four A Records for the Root Domain
If you want someone who types:
example.com
to reach:
www.example.com
Google's official Blogger documentation instructs users to add four A records to the root domain.
| Type | Host | Value |
|---|---|---|
| A | @ or blank | 216.239.32.21 |
| A | @ or blank | 216.239.34.21 |
| A | @ or blank | 216.239.36.21 |
| A | @ or blank | 216.239.38.21 |
The exact way your DNS provider represents the root domain varies.
Common values are:
- @
- blank
- the full domain name
Remove Conflicting Root-Domain Records
If your root domain already has A records pointing somewhere else, they can interfere with the Blogger redirect.
Google's Blogger documentation specifically says that existing A records for the naked domain should be removed before adding Blogger's four Google A records.
This does not mean you should delete every DNS record on the domain.
Only remove records that actually conflict with the hostname you are trying to use.
Step 5: Wait for DNS Changes to Propagate
DNS changes are not always visible immediately.
Google advises waiting before trying to complete the Blogger setup again after creating the records.
In many cases changes begin working relatively quickly, but DNS propagation can take longer depending on the registrar, TTL values and DNS provider.
Do not keep deleting and recreating records every few minutes just because Blogger has not accepted them immediately.
Step 6: Save the Custom Domain Again in Blogger
After the DNS records have had time to propagate, return to:
Blogger → Settings → Publishing → Custom domain
Enter your custom domain again and click Save.
If the CNAME records are correct and visible publicly, Blogger should accept the domain.
Step 7: Enable the Naked-Domain Redirect
After Blogger accepts your custom hostname, enable:
Redirect domain
This lets visitors who enter:
example.com
reach:
www.example.com
The four root-domain A records are what allow this redirect to work correctly.
Step 8: Enable HTTPS
Once the custom domain is connected, scroll to Blogger's HTTPS settings.
Enable:
- HTTPS Availability
- HTTPS Redirect
HTTPS Redirect ensures visitors are sent to the encrypted version of your website.
For example:
http://www.example.com
redirects to:
https://www.example.com
Why HTTPS May Not Be Available Immediately
Blogger needs to provision an SSL certificate for the custom domain.
This process may not finish immediately after the DNS records are changed.
If HTTP works but HTTPS is still unavailable shortly after configuration, give Blogger time to issue the certificate before assuming something is broken.
Important: Check CAA Records
This is a less common but important issue.
A CAA record tells certificate authorities which organizations are allowed to issue SSL certificates for your domain.
Google's Blogger documentation states that if your custom domain uses CAA records, you must allow:
letsencrypt.org
Otherwise Blogger may be unable to create or renew the SSL certificate.
When Does This Matter?
If you have never configured CAA records, you probably do not need to add one just for the sake of having one.
But if your DNS already contains restrictive CAA records, make sure Let's Encrypt is permitted.
Blogger Custom Domain DNS Checklist
| Record | Purpose | Required? |
|---|---|---|
| www → ghs.google.com CNAME | Points the Blogger hostname to Google | Yes for a typical www setup |
| Security CNAME | Verifies your specific Blogger configuration | When Blogger provides it |
| Four root A records | Allows naked-domain redirect | If you want example.com → www.example.com |
| CAA allowing letsencrypt.org | Allows Blogger SSL issuance when CAA restrictions exist | Only when your domain uses CAA records |
Common Error: Blogger Says It Cannot Verify the Domain
The most common causes are:
- The main CNAME is missing.
- The security CNAME is missing.
- A CNAME value was copied incorrectly.
- The DNS changes have not propagated yet.
- The record was added to the wrong hostname.
What to Check
Compare each DNS value character by character with the values Blogger provides.
Also remember that some DNS providers automatically append your domain name to the Host field.
For example, entering:
www.example.com
into a provider that expects only:
www
could accidentally create an incorrect record.
Common Error: WWW Works but the Root Domain Does Not
If:
www.example.com
works, but:
example.com
does not, check:
- All four root-domain A records are present.
- Old conflicting root A records have been removed.
- Redirect domain is enabled in Blogger.
Common Error: HTTP Works but HTTPS Does Not
Check the following:
- The domain is accepted by Blogger.
- DNS records are correct.
- HTTPS Availability is enabled.
- You have allowed enough time for certificate creation.
- CAA records are not blocking Let's Encrypt.
If the DNS configuration was only changed recently, waiting is often better than repeatedly rebuilding the records.
Common Error: Too Many Redirects
A redirect loop can happen when Blogger's redirects conflict with forwarding configured at the registrar or another proxy/CDN layer.
Examples include:
- Registrar forwarding from www to root while Blogger redirects root to www
- External HTTPS forwarding layered on top of Blogger's own HTTPS redirect
- Proxy services applying their own redirect rules
For a simple Blogger setup, avoid unnecessary forwarding rules at the registrar when Blogger can handle the redirect itself.
What If You Use Cloudflare?
Cloudflare adds another layer between visitors and Blogger.
If you use it, DNS and proxy settings must still allow Blogger's custom-domain and HTTPS configuration to work correctly.
When troubleshooting, simplifying the setup can help.
If Blogger is failing to verify a domain, make sure the required CNAME records resolve publicly to the destinations Blogger expects.
Should You Change the Blogger Blogspot URL After Adding a Domain?
No special replacement of the original Blogspot address is required.
Blogger keeps the underlying blog while visitors access it through the custom domain.
Once the custom domain and redirects are configured properly, use the custom-domain URL consistently in:
- Internal links
- Search Console
- Analytics
- Social profiles
- Sitemaps and external references where applicable
What About Google Search Console?
After moving a Blogger site to a custom domain, make sure Google Search Console is tracking the custom domain you actually use.
Then submit the Blogger sitemap under the correct property.
The typical Blogger post sitemap is:
https://www.example.com/sitemap.xml
This helps Google discover URLs under the new domain.
Custom Domain Troubleshooting Flow
If Blogger Will Not Accept the Domain
First: check both CNAME records.
If CNAMEs are correct: wait for DNS propagation.
If www works but root does not: check the four A records and Redirect domain.
If HTTP works but HTTPS does not: check HTTPS Availability, allow time for certificate creation and inspect CAA records.
If redirects loop: remove conflicting registrar or proxy forwarding.
Final Checklist
Before considering the setup complete, confirm:
- Your custom domain is saved successfully in Blogger.
- The main CNAME points to ghs.google.com.
- The Blogger security CNAME is present if required.
- The four Google A records exist if you use naked-domain redirect.
- There are no conflicting root-domain A records.
- Redirect domain is enabled.
- HTTPS Availability is enabled.
- HTTPS Redirect is enabled once available.
- CAA settings allow Let's Encrypt if CAA records are used.
- Both www and non-www URLs end up on the secure canonical domain.
Final Thoughts
A Blogger custom domain usually fails for one of three reasons: incorrect DNS records, conflicting redirects or incomplete HTTPS configuration.
The cleanest setup uses Blogger's required CNAME records, Google's root A records where needed and Blogger's own redirect and HTTPS features.
Once those pieces are correct, there is usually no need for complicated forwarding services or third-party redirect tricks.
Most importantly, do not delete and recreate DNS records repeatedly while they are still propagating.
Configure them carefully, verify the values and allow the system time to update.
Related Guides
- How to Submit a Blogger Website to Google Search Console and Get Indexed
- How to Create a Privacy Policy for Blogger
Official Sources & Further Reading
