Have you connected a custom domain to your Blogger website, but it does not redirect correctly? For example, your website opens with www but not without www, shows a redirect error, or displays a security warning when you try to open the HTTPS version.
These problems are common when a Blogger custom domain has incorrect DNS records, missing CNAME entries, incomplete root-domain configuration, or HTTPS settings that have not finished updating.
The good news is that most Blogger custom domain redirect issues can be fixed without changing your Blogger theme or installing additional software. You only need to check a few settings in Blogger and your domain provider's DNS panel.
In this guide, you will learn how to fix Blogger custom domain redirect issues step by step. We will cover www and non-www redirects, DNS records, HTTPS availability, SSL certificate problems, and common domain errors.
'/>
Before changing any settings, identify what is happening with your domain. Different redirect problems can have different causes.
Understanding the exact problem helps you avoid changing settings that are already correct.
Blogger allows you to connect a domain purchased from a third-party domain registrar. For example, you can connect example.com to your Blogger website and use www.example.com as your main blog address.
There are two important versions of a domain:
https://example.comhttps://www.example.com
Blogger normally uses the custom domain with a subdomain, such as www.example.com. The root domain can then be redirected to the www version using the correct DNS configuration and Blogger's Redirect domain setting.
For example, the intended result can look like this:
Using one consistent preferred address helps visitors reach the same version of your website. It also avoids having multiple versions of your homepage accessible as separate URLs.
First, make sure that your custom domain is correctly connected to your Blogger website.
www.example.com.If the custom domain is not connected, enter your domain with the correct subdomain and click Save. Blogger may display an error containing two CNAME records that you must add to your domain provider's DNS settings.
Do not guess these records. Copy the two CNAME entries shown in your own Blogger dashboard because the security CNAME values are unique to your blog.
Info!
If Blogger displays a message asking you to update DNS records, keep that message available. You will need the exact host and destination values in the next step.
Incorrect DNS records are one of the most common reasons a custom domain does not connect or redirect properly.
DNS records tell browsers where to find your website. For a standard Blogger custom domain using www.example.com, you need the correct CNAME records. You also need the Google A records if you want the root domain to redirect to the www version.
Find the CNAME record for your www subdomain. For the standard Blogger setup, the main CNAME record is:
| Type | Host / Name | Destination / Target |
|---|---|---|
| CNAME | www | ghs.google.com |
Some DNS providers automatically add a trailing dot to the destination. That is normal. Follow the format accepted by your provider.
Make sure there is no conflicting record for the same www host. For example, an existing A record for www may conflict with the CNAME record.
Blogger may also provide a second CNAME record containing a unique security code. This record is different for each blog and must be copied from your Blogger dashboard.
It generally looks like this:
| Type | Host / Name | Destination / Target |
|---|---|---|
| CNAME | Your unique Blogger security code | Your unique Google-hosted destination |
Use the exact values Blogger displays. Do not copy another website's security CNAME record because it will not match your blog.
If www.example.com works but example.com does not, your root domain may be missing Google's A records.
To allow the root domain to redirect to your www address, add the following four A records in your DNS panel:
| Type | Host / Name | Points To / Value |
|---|---|---|
| A | @ | 216.239.32.21 |
| A | @ | 216.239.34.21 |
| A | @ | 216.239.36.21 |
| A | @ | 216.239.38.21 |
Depending on your DNS provider, the root-domain host may be shown as @, blank, or your domain name itself.
@ as the host, if that is how your provider represents the root domain.216.239.32.21 as the value.After adding the records, check whether there are other conflicting A records for the root domain. Blogger's instructions say to remove existing root-domain A records that conflict with the required Google records.
Warning!
Do not delete MX records, TXT records, email verification records, or unrelated DNS entries. These may be needed for email, domain verification, or other services. Only change records you have identified as conflicting with the Blogger setup.
Adding the DNS records is not the only step. You must also enable the Redirect domain option in Blogger.
This setting redirects visitors from the root domain to your custom domain with the subdomain.
For example, when a visitor opens https://example.com, Blogger should redirect them to https://www.example.com, provided that the DNS configuration is correct.
HTTPS protects the connection between your website and its visitors. It is also important for avoiding browser security warnings when people open your custom domain.
To enable HTTPS availability:
Blogger needs to configure an SSL certificate for your custom domain. This process may not finish immediately, so allow time for the certificate to become available.
If the option is already enabled, check its status and wait for the certificate process to complete before changing other settings.
After HTTPS availability is enabled and the certificate is ready, turn on HTTPS redirect.
HTTPS redirect helps ensure that visitors use the secure HTTPS version instead of the unencrypted HTTP version.
If your website displays a Too Many Redirects or ERR_TOO_MANY_REDIRECTS error, the browser may be caught in a redirect loop.
This can happen when two or more services repeatedly redirect the same address in different directions.
If your domain provider has a separate forwarding feature, avoid setting up another root-to-www redirect there while Blogger is already handling that redirect. Two competing redirect rules can create unexpected results.
If you use a third-party DNS proxy, check its SSL and redirect settings carefully. For troubleshooting, follow the provider's instructions for configuring Blogger-compatible DNS and avoid making multiple redirect systems compete with each other.
Sometimes the problem is not caused by DNS. An incorrect custom redirect inside Blogger can send visitors to the wrong address or create a redirect loop.
To review custom redirects:
Pay special attention to rules that redirect the homepage to itself or send the same URL between two different versions. Do not delete valid post redirects that you need to preserve.
After changing DNS records, your website may not work correctly immediately. DNS updates take time to become visible across different networks and locations.
Google's Blogger documentation notes that DNS changes can take time to activate. Some domain changes may take up to 24 hours or longer, depending on the provider and DNS caching.
During this period:
Info!
If you recently connected a new domain, a temporary delay does not always mean the configuration is incorrect.
Once the DNS and HTTPS settings are ready, test your domain using different URL versions. This helps you confirm whether the redirects work as expected.
| URL to Test | Expected Result |
|---|---|
| http://example.com | Redirects to HTTPS www |
| https://example.com | Redirects to HTTPS www |
| http://www.example.com | Redirects to HTTPS www |
| https://www.example.com | Opens the Blogger website |
Replace example.com with your actual domain name. Test the URLs in a private or incognito browser window to reduce the effect of previously cached redirects.
If one version still fails, return to the related DNS or Blogger setting instead of changing every setting at once.
| Problem | Possible Cause | What to Check |
|---|---|---|
| WWW not working | Incorrect or missing CNAME | Check the www CNAME and Blogger's security CNAME |
| Root domain not redirecting | Missing A records | Check all four Google A records and Redirect domain |
| HTTPS unavailable | Certificate not ready or DNS issue | Check DNS, CAA records, and HTTPS availability |
| Too many redirects | Conflicting redirect rules | Review forwarding, proxy, and Blogger redirect settings |
| Old website appears | Old DNS records or forwarding | Review existing A, CNAME, and forwarding entries |
| Blogspot URL does not redirect | Custom domain setup incomplete or updating | Check Blogger Publishing settings and allow time for updates |
If your domain uses CAA records, they can affect which certificate authorities are allowed to issue SSL certificates for your domain.
Google's Blogger documentation specifically says that if you use CAA records on your custom domain, you must allow letsencrypt.org. Otherwise, Blogger may not be able to create or renew the SSL certificate.
If HTTPS is unavailable even though your other DNS records look correct, check your CAA configuration with your DNS provider. Do not remove all CAA records without understanding their purpose. If you are unsure, ask your domain provider to help you add the required authorization safely.
Your domain may have missing or incorrect DNS records, an inactive Redirect domain setting, incomplete HTTPS configuration, or conflicting forwarding rules. Check the www CNAME, security CNAME, and root-domain A records first.
Add Google's four required A records for the root domain, make sure your www CNAME is correct, and enable Redirect domain under Blogger Settings → Publishing. Your root domain can then redirect to the www version.
The four Google IP addresses are 216.239.32.21, 216.239.34.21, 216.239.36.21, and 216.239.38.21. Add them as A records for your root domain if you want it to redirect to your www address.
For the standard www setup, the CNAME host is www and the destination is ghs.google.com. Blogger also provides a unique security CNAME that you must copy from your own dashboard.
HTTPS may still be processing, or your DNS and certificate authorization settings may need correction. Check the CNAME and A records, review any CAA records, and allow time for Blogger to issue the certificate.
DNS changes may become active within a few hours, but some updates can take up to 24 hours or longer. SSL certificate processing may also take additional time.
Yes, after HTTPS availability is enabled and the SSL certificate is ready, turn on HTTPS redirect so visitors can access the secure version of your blog.
Blogger custom domains are configured using a subdomain such as www or blog. You can use the root domain for visitors by setting up the required A records and enabling the Redirect domain option.
Correctly configuring the custom domain should not delete your posts or change their content. However, incorrect custom redirects or domain settings can make some URLs unavailable, so review your settings carefully.
No. Most custom domain redirect problems are related to DNS records and Blogger publishing or HTTPS settings. Editing your theme's HTML or JavaScript is generally not necessary.
Blogger custom domain redirect issues can be frustrating, but most of them are caused by a small number of configuration problems. The most important things to check are the www CNAME, unique security CNAME, four Google A records, Redirect domain setting, and HTTPS configuration.
Start with the DNS records, then check the publishing settings in Blogger. Once the domain is connected correctly, enable HTTPS availability and HTTPS redirect. Finally, test the root and www versions of your website.
Do not make unnecessary changes to your Blogger theme or delete unrelated DNS records. Make one change at a time and allow DNS and SSL updates to finish.
By following these steps, you can troubleshoot most common Blogger custom domain redirect issues and help visitors reach the correct secure version of your website.