How to Connect Cloudflare Domain to Blogger Without Errors

Want to connect Cloudflare domain to Blogger, but scared you'll break something?

So was Riya.

It was 1:12 at night when my phone buzzed.

"Didi, my blog is gone. Just gone. It says This site can't be reached."

Riya is my college junior. She bakes the best chocolate walnut cake I've ever eaten, and that week she'd finally started a baking blog on Blogger. She'd also bought her first domain on Cloudflare, all excited, around 400 rupees.

And now? A blank error page. And a very sad emoji.

Funny thing is, I had connected my own domain, clarkopal.org, to Blogger that same morning. Same Cloudflare. Same Blogger. Same six records.

Mine worked. Hers didn't.

The reason turned out to be one tiny cloud icon. I'll tell you exactly which one, but first, let's do this properly, step by step, so it never happens to you.

Why connect Cloudflare domain to Blogger instead of keeping blogspot?

Because yourname.blogspot.com looks like a hobby, and yourname.com looks like a real website.

That's not just my opinion. When Riya shared her blogspot link in a baking group, a few people asked if it was "safe to open." Nobody asks that about a normal .com.

Here's what a custom domain gives you:

• Trust. Readers, brands and ad networks take you more seriously.
• Your own name forever. If you ever move from Blogger to WordPress, the domain moves with you. Your links and Google rankings don't vanish.
• Free hosting still. Blogger stays free. You only pay for the domain, once a year.
• Free HTTPS. Blogger gives you the padlock at no cost, even on your own domain.

And why Cloudflare? Mostly price and honesty. Cloudflare sells domains at cost, with no fancy first-year discount that jumps later, and the DNS screen is clean and fast.

The only catch is that Cloudflare is built for big websites, so its screens keep pushing features a Blogger blog doesn't need. That's exactly where people like Riya get confused. So when you connect Cloudflare domain to Blogger, you'll mostly be ignoring things, not adding them.

What do you need before you connect Cloudflare domain to Blogger?

Short answer: a Blogger blog, a domain on Cloudflare, and about 30 minutes.

That's really it. Here's the small checklist I used:

• A Blogger blog (even a brand-new one with zero posts works).
• A domain you own, bought through Cloudflare Registrar or added to Cloudflare from another company.
• Login to both, ideally in two tabs side by side.
• A notepad. You'll copy a long code from Blogger, and you don't want to lose it.

I paid about $8.50 for clarkopal.org for the first year. Cloudflare sells domains at cost, so there's no big markup.

One thing I'll tell you honestly: renewal is a bit higher than the first year, and an Indian card sometimes fails on auto-renew. Put a reminder in your phone a month before expiry. Losing a domain because a card failed is a terrible way to lose a blog.

Riya had all of this ready. Her problem came later.

Where do you find the Blogger custom domain DNS settings?

They're inside Blogger, but Blogger only shows them after you try once and "fail." That confuses a lot of people.

Here's how it goes:

1. Open Blogger and go to Settings.
2. Scroll to Publishing and click Custom domain.
3. Type your domain with www, like www.clarkopal.org.
4. Click Save.

Now Blogger shows a red error. Something like, "We have not been able to verify your authority to this domain."

Don't panic. That error is actually the useful part.

Under it, Blogger lists two records. These are your Blogger custom domain DNS settings:

• CNAME 1: Name www, Destination ghs.google.com. This is the same for everyone.
• CNAME 2: A random-looking name (mine started with "qrlgvu") pointing to a long address ending in dv.googlehosted.com. This one is unique to you. It proves you own the domain.

Copy both into your notepad. Exactly. One wrong letter and the whole thing fails.

Google explains this in its own Set up a custom domain help page too, if you'd like to read it from the source.

Good news: these Blogger custom domain DNS settings are a one-time job. Once they work, you never touch them again, even when you change your theme, add pages or publish a hundred posts.

My colleague Sana once copied the second record with a space at the end. Blogger kept rejecting it for a whole evening. She thought Google hated her. It was one space.

How do you add the records in Cloudflare?

Now go to the Cloudflare tab.

1. Click your domain.
2. Open DNS, then Records.
3. Click Add record.

Cloudflare's guide on creating DNS records shows the same screen, so you can match it with yours.

Add the first CNAME:

• Type: CNAME
• Name: www
• Target: ghs.google.com
• Proxy status: DNS only (grey cloud)
• TTL: Auto

Click Save. Then add the second CNAME the same way, using your unique name and your unique dv.googlehosted.com target. Again, grey cloud.

If you're curious what a CNAME record actually is, think of it as a signboard. It says, "Looking for www? Go over there, to Google."

Now go back to Blogger, type www.yourdomain.com again and click Save.

If the records are right, the red error disappears. For me it took one try, maybe because I waited about ten minutes before saving again. If yours fails, wait an hour and retry. DNS can be slow to travel around the world.

Which brings me back to Riya.

Should you use the Cloudflare proxy for Blogger?

No. Keep it off. Grey cloud, "DNS only," on every record you add for Blogger.

This was Riya's whole problem.

When I got on a video call with her at 1:20 am, I asked her to share her screen and open Cloudflare DNS. Every single record had a bright orange cloud next to it.

"Why did you turn these orange?"

"Cloudflare told me to! There's a yellow box saying proxying is required for security."

And she's not wrong. Cloudflare does show that banner. I see it on clarkopal.org too, right now.

Here's what's going on.

When the cloud is orange (proxied), visitors don't go straight to Google's servers. They go to Cloudflare first, and Cloudflare passes them along. That's great for many websites.

But the Cloudflare proxy for Blogger causes trouble. Blogger needs to see your domain pointing directly at Google, so it can verify you and create your free SSL certificate. With the orange cloud on, Google sees Cloudflare instead, and things break. Verification fails, HTTPS gets stuck, or the site just won't load.

Cloudflare's own proxy status docs even say records that prove domain ownership shouldn't be proxied.

So we clicked Edit on each record, switched the cloud to grey, and saved.

Then we waited.

If anyone tells you the Cloudflare proxy for Blogger makes your blog faster, smile and leave it off. Blogger already runs on Google's own servers. Your blog is fast enough without it.

Question	Orange cloud (Proxied)	Grey cloud (DNS only)
Where do visitors go first?	Cloudflare	Straight to Google (Blogger)
Can Blogger verify your domain?	Often fails	Yes
Free Blogger HTTPS certificate	Can get stuck	Works
That yellow Cloudflare banner	Goes away	Stays (ignore it)
Best for a Blogger blog?	No	Yes

How do you redirect non-www to www in Blogger?

So far, www.clarkopal.org works. But what happens when someone types just clarkopal.org, without the www?

Without this step, they get an error. My cousin Aman ran his travel blog like that for two months. Half his friends told him "your site is down." It wasn't. They were just typing it without www.

To fix it, you add four A records in Cloudflare. These point the bare domain (people call it the "naked" or "root" domain) to Google:

• Type A, Name @, IPv4 address 216.239.32.21
• Type A, Name @, IPv4 address 216.239.34.21
• Type A, Name @, IPv4 address 216.239.36.21
• Type A, Name @, IPv4 address 216.239.38.21

All four with the grey cloud. Yes, again.

Then go back to Blogger, Settings, Publishing, and turn on Redirect domain. It'll say something like "Redirect clarkopal.org to www.clarkopal.org."

That's how you redirect non-www to www in Blogger. Now both addresses open the same blog, and Google sees only one version, which is cleaner for SEO.

Here's what my final Cloudflare DNS looks like. Six records, all grey:

Type	Name	Points to	Proxy
CNAME	www	ghs.google.com	DNS only
CNAME	your unique code	your code.dv.googlehosted.com	DNS only
A	@	216.239.32.21	DNS only
A	@	216.239.34.21	DNS only
A	@	216.239.36.21	DNS only
A	@	216.239.38.21	DNS only

Why is Blogger HTTPS not working on my custom domain?

This is the second most common panic, right after the orange cloud.

You open your site and Chrome says Not secure. Or the padlock is missing. Or Blogger shows "HTTPS availability is being processed."

I've read so many forum posts titled "Blogger HTTPS not working" that ended with one person saying, "Oh. The cloud was orange." Check that first, always.

Most of the time, nothing is wrong. Blogger is just making your free SSL certificate in the background. It uses Let's Encrypt for this, and it can take a little while.

Once it's ready, go to Settings, Publishing and turn on both:

• HTTPS availability
• HTTPS redirect (this sends everyone to the secure https version)

If Blogger HTTPS is still not working on your custom domain after a day, check these, in this order:

1. Orange cloud anywhere? Turn it grey. This fixes most cases.
2. Extra old records? If your domain came with parking records or old A records, delete only those. Keep your six.
3. CAA records? If you added CAA records, one must allow letsencrypt.org, or Blogger can't create the certificate.
4. Toggle trick: turn off HTTPS redirect, wait a few minutes, turn it on again.

When Blogger HTTPS is not working on a custom domain for more than two days, that's when I'd remove the domain in Blogger and add it again.

Riya's padlock showed up the next morning. Before that, she messaged me three times asking if it was "hacked." It wasn't. It was just Blogger doing its job slowly.

Want a second pair of eyes? I sometimes paste my records into an AI tool and ask it to check them. Just don't paste passwords or login details, and remember that AI can be wrong too. Here's the prompt I use:

I am connecting my Blogger blog to a domain I bought on Cloudflare. Here are my DNS records: [paste Type, Name, Content and Proxy status of each record]. Blogger asked me to add a CNAME for www pointing to ghs.google.com and a second verification CNAME. Please check: 1) Is any record missing or typed wrong? 2) Is any record proxied (orange cloud) when it should be DNS only? 3) Are there extra old records I should delete? Explain in simple steps for a beginner.

Do you need to change any Cloudflare SSL/TLS settings?

No. Leave them exactly as they are.

This surprised Riya too. She'd read somewhere that you must set SSL to "Full" or "Flexible" in Cloudflare, and she spent twenty minutes clicking around that menu.

Here's the simple truth. Cloudflare's SSL/TLS settings only work on proxied records, the orange ones. Since every Blogger record stays grey, Cloudflare isn't touching your visitors at all. Blogger makes the certificate, Blogger serves the padlock.

Same with buttons like "Always Use HTTPS" in Cloudflare. They don't do anything for a grey-cloud Blogger blog. Use Blogger's own HTTPS redirect switch instead.

Less clicking. Fewer chances to break something.

Can you use a subdomain like blog.yourdomain.com on Blogger?

Yes, and it's even easier.

Maybe your main domain already runs a shop or a portfolio somewhere else, and you only want the blog on Blogger. Then use a subdomain, like blog.yourdomain.com.

The steps change only a little:

• In Blogger, type blog.yourdomain.com as your custom domain.
• In Cloudflare, the first CNAME's Name becomes blog instead of www. It still points to ghs.google.com.
• Add the second, unique verification CNAME exactly as Blogger shows it.
• Skip the four A records. Those are only for the naked domain.
• Grey cloud on both. You knew I'd say that.

A friend of mine who sells handmade candles did exactly this. Her shop sits on the main domain, and her candle-care tips live on a Blogger subdomain. Both work fine side by side.

How long does a Blogger custom domain take to work?

So, how long does a Blogger custom domain take? For me, about an hour for everything except HTTPS. Riya's took until the next morning, mostly because of the orange cloud detour.

A rough idea of how long a Blogger custom domain takes:

• A few minutes to an hour: Cloudflare records go live. Cloudflare is fast.
• Up to a few hours: Blogger accepts your domain after you click Save again.
• Up to 24 hours: your old blogspot address starts redirecting to your new domain.
• A few hours to a day or two: HTTPS certificate is ready.

Want to see whether your records are live without refreshing your blog fifty times? Use Google Public DNS. Type your domain, pick the record type (A or CNAME), and it shows what the world sees.

What should you do right after your custom domain works?

Your blog opens on its new address with a padlock. Nice. Now do these three things.

Once you connect Cloudflare domain to Blogger and the padlock shows, the technical part is over. What's left is telling Google your blog exists, and keeping things tidy.

1. Add it to Google Search Console. Go to Google Search Console and add a Domain property for your domain.

Here's something I didn't expect. When I added clarkopal.org, Search Console verified it instantly. No code, no TXT record. Its settings said "Domain name provider, successfully verified."

How? Remember that second CNAME, the long dv.googlehosted.com one? Google had already seen it. It counted as proof that I own the domain. Google's page on verifying site ownership explains the different methods if yours asks for one.

So here's my rule now: never delete that verification CNAME, even after everything works. It quietly keeps your Search Console access alive.

2. Submit your sitemap. In Search Console, open Sitemaps and add https://www.yourdomain.com/sitemap.xml. If your blog has no posts yet, it may show an error like "Missing XML tag." That's normal. It fixes itself after your first post.

3. Ignore the scary banners. Cloudflare will keep nudging you to turn on the proxy. It may also say email can't reach your domain. If you don't use email on that domain, nothing is broken.

And one more from my own blog journey. My finance blog Arocol started on a blogspot address. Google was slow to show it. Things moved much better after I switched it to its own domain. I can't promise the same for every blog, but a custom domain does look more trustworthy, to readers and to ad networks.

Which mistakes stop you from being able to connect Cloudflare domain to Blogger?

I've now helped four people with this, including Riya. The same few mistakes show up again and again.

1. The orange cloud. Number one, by far. Grey cloud for every Blogger record.
2. Typing the full domain in the Name box. In Cloudflare, the Name is just www. If you type www.yourdomain.com, some screens turn it into www.yourdomain.com.yourdomain.com. Cloudflare usually cleans this up, but check the saved record anyway.
3. A tiny typo in the verification CNAME. Remember Sana and her extra space? Copy and paste, never type it by hand.
4. Old parking records. Some domains come with leftover A records or a "parked" page. If they clash with Google's four IPs, delete only the old ones.
5. Skipping the A records. Your www works, so you think you're done. Then the naked domain fails, like Aman's travel blog.
6. Giving up too soon. DNS is not instant everywhere. Wait an hour before you decide something is broken.

If your domain was bought somewhere else (GoDaddy, Hostinger, Namecheap) and you only use Cloudflare for DNS, there's one more check. The nameservers at your old company must point to Cloudflare. Otherwise, the records you add in Cloudflare simply don't count.

Can you mess up your blog while doing this?

Honestly? Not really, if you're careful.

I was nervous too, the first time. I kept a screenshot of my Blogger settings and Cloudflare records before changing anything, just in case. You can do the same. It takes ten seconds and calms your mind.

Your posts stay safe inside Blogger. DNS only decides which address points to them. The worst case is your site not opening for a few hours while you fix a record.

Still, a few don'ts:

• Don't delete records you don't understand without checking first.
• Don't turn the orange cloud on, even when the banner tempts you.
• Don't change your custom domain again and again in Blogger. Each change can reset the HTTPS process.
• Don't share your Cloudflare or Blogger login with anyone who offers to "fix" it for money.

So, did Riya's blog come back?

It did.

At 9:40 the next morning she sent me a screenshot. Her baking blog, her own domain, a little padlock in the address bar.

Then a second message: "Didi, I'm making you a chocolate walnut cake this Sunday. Don't say no."

I didn't say no.

If you're about to connect Cloudflare domain to Blogger yourself, remember the three things that saved her: copy Blogger's two CNAMEs exactly, add the four A records for the naked domain, and keep every cloud grey.

That's it. You've got this.

Stuck somewhere? Tell me in the comments which step and what error you see, and I'll try to help.

Disclaimer: Steps and screens are from my own setup in October 2026. Blogger and Cloudflare change their menus from time to time, so if something looks different, check their official help pages. Clark Opal is not affiliated with Google, Blogger or Cloudflare.