You know that sinking feeling? You finally buy a custom domain for your Blogger site, you set up the DNS records perfectly, and then... Google Search Console hits you with a big red error: "URL is not on Google: Redirect Error."
I just went through this exact panic with my new site, Paper is Blue.
I spent 48 hours refreshing pages, tweaking settings, and worrying I had broken my site forever. But here is the good news: Your site is probably fine.
If you recently connected a custom domain (like GoDaddy or Namecheap) to Blogger and you are seeing "Redirect Errors," it’s likely a "ghost error" a reporting delay in Google's system, not a real technical failure.
Here is exactly how I diagnosed the problem, confirmed my site was live, and the simple settings I used to fix it.
The "Ghost" Error: Why Search Console is Lying to You
The first thing you need to know is that the main dashboard in Google Search Console (GSC) is not real-time.
When I saw the "Redirect Error," I thought my DNS was broken. But when I checked the specific date of the error, it was from two days ago back when I was still messing with my domain settings.
Don't trust the Dashboard. Trust the Live Test.
Here is the first step you must take before changing anything:
- Go to URL Inspection in Search Console.
- Paste your full URL (e.g.,
https://www.yourdomain.com). - Click the "TEST LIVE URL" button in the top right corner.
If that result comes back Green with "URL is available to Google," STOP. You have won. The red error on the dashboard is just old history that hasn't updated yet.
Step 1: The "Perfect" DNS Setup for 2026
If your Live Test failed, then you might actually have a DNS issue. For your custom domain to work with Blogger in 2026, you strictly need these records. I verified these myself, and they are what finally worked for me:
A Records (The Google IPs): You need four separate "A" records pointing to these exact IPs:
- 216.239.32.21
- 216.239.34.21
- 216.239.36.21
- 216.239.38.21
CNAME Records:
- Host:
www-> Points to:ghs.google.com - Host:
[Your unique verification code]-> Points to:[Google's long verification string]
Note: Make sure you don't have any "Forwarding" rules set up in your domain registrar (like GoDaddy). Let Blogger handle the redirects.
Step 2: The "HTTPS Toggle" Trick
Sometimes, even with perfect DNS, Blogger's internal SSL certificate gets "stuck" especially if you deleted and re-added your domain like I did.
Here is the "Toggle Trick" that forces a refresh:
- Go to Blogger Dashboard > Settings.
- Scroll down to HTTPS.
- Turn "HTTPS Redirect" to OFF.
- Wait 5 minutes (go make a coffee).
- Turn it back ON.
This simple reboot forces Blogger to re-issue the security certificate and clear out any old redirect loops.
Step 3: The Mobile Indexing Confusion (?m=1)
Once your site starts indexing, you might notice something weird. Google might index the mobile version of your URL (the one ending in ?m=1) instead of your clean desktop URL.
Don't panic. This is normal.
Blogger is a mobile-friendly platform, and Google uses a "Mobile-First" crawler. So, it sees the mobile version first.
I checked my own "Page Indexing" report, and under "User-declared canonical", it correctly showed my clean desktop URL (.html).
As long as that "User-declared" line is correct, Google knows the desktop version is the "real" one. It will eventually swap them in the search results. Do not block the ?m=1 parameter in your robots.txt, or you will crash your SEO.
Conclusion
If your Live Test is Green and your Incognito Mode check works (typing your domain opens your site), then your job is done.
The "Redirect Error" in Search Console will stay red for a few days maybe even a week. It’s annoying, but it’s just a reporting lag. I simply clicked "Request Indexing" once on the Live Test screen and then closed the tab.
Focus on writing your next post. The tech is working, even if the dashboard hasn't caught up yet.