The page with the redirect error

 Page with redirect error on your Blogger website

Learn how to fix the “Page with redirect error” in Blogger. Step-by-step DNS, HTTPS, and SEO  solutions  for custom domains

Page with Redirect Error on Your Blogger Website Running into a “Page with redirect error” inside Google Search Console can be unsettling, especially if your Blogger site uses a custom domain. This message means Google’s crawlers are being trapped in a redirect loop or an invalid redirection chain, making it difficult for them to access or index your pages.

The encouraging news is that this issue is almost always fixable. By carefully reviewing your domain and Blogger settings, you can restore proper indexing and maintain your site’s visibility in search results.

Fix the redirect loop Blogger custom domain

1. What a Redirect Error Really Means:

When a web browser or Googlebot requests a page, the server might respond with an instruction to visit another address—a process known as a redirect. Redirects are normal when moving from HTTP to HTTPS or from non-www to www, but problems arise when the chain loops endlessly. Common causes include:

Infinite loops—URLs keep sending requests back and forth (e.g., Page A → Page B → Page A).

Excessive redirects—The browser is asked to follow too many steps before reaching the final destination.

Invalid targets – The redirect points to an incorrect or non-existent location.

For Blogger sites connected to custom domains, these errors most often come from DNS configuration mistakes or conflicting HTTPS settings.

2. Checking Your DNS Records

Your Domain Name System (DNS) translates your web address (like digivaultsbd.com) into IP addresses so visitors can find your site. If your DNS entries are incomplete or incorrect, they can easily trigger redirect loops.

Blogger redirect error in Google Search Engine

The page with the redirect error

Steps to verify and correct your DNS setup: 

    Sign in to your domain registrar (GoDaddy, Namecheap, Hostinger, etc.).

    Locate DNS Management or Zone Editor options.

    Review the A-records for your root domain (the “@” host).

 

        Blogger requires four A-record entries pointing to Google’s servers.

        Confirm that these IPs match the ones listed in the official Blogger documentation.

        Delete any extra A-records that don’t correspond to these

Next, verify your CNAME records carefully:

        The www record should point to ghs.google.com.

A second, unique CNAME (given during your Blogger setup) should point to something like gv-xxxx.dv.googlehosted.com.

3. Resolving HTTPS and SSL Conflicts

Blogger includes free SSL certificates so your site can load securely over HTTPS. However, when HTTPS is partially enabled or conflicts with settings at your registrar, visitors may encounter endless redirects between HTTP and HTTPS versions.

How to refresh HTTPS safely:

Log in to Blogger Dashboard → Settings.

Scroll to the HTTPS section.

Temporarily set “HTTPS availability” to No.

Wait about 5–10 minutes to let changes propagate.

Switch “HTTPS availability” back to Yes, and ensure “HTTPS redirect” is also turned On.

4. Reviewing Custom Redirects in Blogger

Occasionally, redirect errors appear because of incorrect entries in the Blogger “Custom Redirects” section—especially if code was accidentally pasted instead of simple paths.

To fix these:

In your Blogger dashboard, go to Settings → Errors and redirects → Custom redirects.
Delete any that include JavaScript, HTML tags, or anything other than straightforward URL paths (for example, /old-page.html → /new-page.html).

Review each redirect listed.

Save your changes.

✅ Tip: Use custom redirects only for legitimate 301 or 302 redirects between valid pages. This preserves SEO value and ensures a smooth user experience.

The page with the redirect error

Read More

5. Clear Your Browser Cache and Test the Results

After updating your DNS or HTTPS settings, cached data might cause you to see old redirect behavior.

To test accurately:

Clear browser cache and cookies, or use an Incognito/Private window.

Use an HTTP status checker (such as httpstatus.io) to confirm your redirect flow.

A healthy redirect pattern should resemble:

http://yourdomain.com → https://www.yourdomain.com → (200 OK).

If you see long or repetitive chains, recheck your settings.

6. Let Google Know the Issue Is Fixed

Once your site loads properly, update Google Search Console to prompt a re-crawl.

Open Google Search Console → Indexing → Pages.

Find the “Redirect error” report and select Validate Fix.

Optionally, test a few individual URLs using the URL Inspection tool to confirm they now return “URL is available to Google.”

More for you 

7. Wrapping It All Up

Redirect errors may momentarily disrupt traffic and indexing, but they are easily manageable. By verifying your DNS records, refreshing HTTPS, and keeping custom redirects clean, you’ll maintain a fast, accessible, and search-friendly Blogger site.

A properly configured setup ensures Googlebot can crawl your pages smoothly, users enjoy a secure experience, and your SEO performance remains strong and stable.

Conclusion: A Seamless Online Presence

A "Page with redirect error" can temporarily hinder your Blogger site's performance, but it's a solvable problem. By diligently checking your DNS settings, reconfiguring HTTPS, and ensuring your custom redirects are clean, you can quickly restore your site's health. A well-configured, redirect-free site not only improves your SEO performance by ensuring Googlebot can crawl and index your content efficiently but also enhances the user experience with faster, more reliable access to your blog. Follow these steps, and your Blogger site will soon be navigating the web without a hitch. 

SHORT QUESTIONS  AND ANSWERS

1. Why does my custom domain on Blogger show a "Page with redirect error," and what is the primary cause?

Answer (SEO Focus: DNS Configuration):

The primary cause for the "Page with redirect error" on a Blogger custom domain is often incorrect or missing A-records in your domain's DNS settings. This happens when the four specific Google IP addresses required for your root domain (@ host) are not correctly pointing to the Blogger servers, creating a loop or failure when the domain tries to resolve to your blog's content. Fixing these A-records is the crucial first step for restoring site accessibility.

2. How does the Blogger HTTPS setting relate to redirect loops, and how do I fix a conflict?

Answer (SEO Focus: HTTPS/SSL Conflict):

Redirect loops frequently occur due to HTTPS/SSL conflicts, where your domain repeatedly redirects between http:// and https://. To fix this, you must reset the settings in Blogger: navigate to Settings > HTTPS, temporarily toggle "HTTPS availability" to "No", wait 5-10 minutes for the cache to clear, and then switch it back to "Yes", ensuring "HTTPS redirect" is also "On." This forces a proper, single-step secure connection.

3. What is the correct way to use the "Custom Redirects" feature in Blogger to preserve SEO value?

Answer (SEO Focus: 301 Redirects & Link Equity):

The correct use of the "Custom Redirects" feature is to create clean, text-based 301 (Permanent) redirects from old, outdated URLs to new ones (e.g., /old-page.html to /new-page.html). This is vital for preserving link equity and preventing users and search engines from hitting a 404 error. The feature should never contain JavaScript or HTML code, as that immediately causes structural redirect errors.

4. After fixing my DNS and HTTPS, how do I ensure Google knows the redirect error is gone?

Answer (SEO Focus: Google Search Console Validation):

After implementing the fix, you must communicate the change to Google via the Google Search Console (GSC). Go to the "Redirect error" report under Indexing > Pages and click "Validate Fix." Google will then put all affected URLs into a re-crawl queue. To confirm the fix worked instantly, run a "Test Live URL" on a sample page; the expected result is "URL is available to Google."

5. What immediate steps should I take if my browser is stuck in an endless redirect loop?

Answer (SEO Focus: User Experience & Cache):If your browser is stuck in an endless redirect loop (ERR_TOO_MANY_REDIRECTS), the immediate step is to clear your local cache. Clear all browser cookies and cache for your specific domain, or use an Incognito/Private Browsing window. This removes any outdated, cached redirect instructions, allowing you to test the site accurately against the newly corrected DNS and HTTPS settings.

                                   The page with the redirect error

If this guide helped you resolve your Blogger redirect issue, share your result in the comments—or check out our guide on optimizing robots.txt for Blogger.

Read More