Redirect Errors in Google Search Console:
(What I Learned And What Didn't Work)
in Google Search Console on Blogger?
Here’s exactly what I learned
and what didn't work!”
 |
| A cute yellow kitten and a beautiful butterfly |
Today's Contents:
1. What Problem Did I Encounter?
2. Why Isn't My Blogger Homepage Showing Up on Search Engines Even After Registering It in Search Console?
3. Why Dose This Redirect Error Keep Happening on my Blogger Site Even After Changing my Blog Template to a Modern One?
4. How I Handled It: Step-by-Step
• Check Your Blogger Settings Again
• Test with an HTTP Redirect Checker
• Re-register Your Blog with URL Prefix Property (Most Critical Step)
• Resubmit a Clean Sitemap
• Manually Request Indexing in Search Console
• Time and Patience
• Check Indexing
5. What Happened After Handling It?
6. 5 Smart Ways to Handle Indexing Delays in Blogger
🚴"I am running a Blog on Blogger with the VTrick template."
Hello, Radiant Souls!✨
In 2024, I started my Google blog. At first, everything felt harder than I expected, so I began writing slowly while learning little by little along the way.
One day, I discovered that there's actually a way to make my blog searchable on search engines. That's when I first learned about a tool called Google Search Console.
Of course, simply posting as a hobby is fun. But the idea of reaching more people through my writing—and maybe even making a little money—made blogging even more exciting.
These motivations gradually led me to explore the wider online jungle of HTML, SEO, and Google tools. There's still so much to learn, but the energy I get every time I discover something new keeps me inspired and moving forward.
| What Problem Did I Encounter?
I used to use Google's free old theme called "Dynamic Views" for my blog. After publishing over 80 posts, I tried requesting indexing in Google Search Console. But I got the Redirect errors many times.
I was told that Google's old themes like Dynamic Views often use an internal anchor-based or JavaScript redirect structure, which often prevent Googlebot from properly understanding the page structure. This is a pretty difficult topics to me.
Anyway, after learning that, I doubted that this theme might be related to Redirect errors in Google Search Console, so I decided to switch to a new template called "Vtrick." This is a comparatively newer free template than Dynamic Views.
After setting up the new design and updating my existing posts, I submitted my blog's home URL for indexing in Google Search Console with big dreams in my heart. But unfortunately, I still got the same Redirect error.😭 What should I do?
| Why Isn't My Blogger Homepage Showing Up on Search Engines Even After Registering It in Search Console?
If your blog isn't appearing in Google search results even after submitting it to Google Search Console, you're not alone. Here're some common reasons this might happen, especially for Blogger users:
1. Too Few or No Blog Posts
- If your blog has little to no content, search engines may delay indexing it. So try publishing at least a few meaningful posts first.
2. Incorrect Blogger Settings
- Make sure your blog isn't blocking search engines:
- Turn on "Visible to search engines" so that Google can crawl your blog.
- Keep "Custom robots.txt" turned off to avoid accidental blocking.
- Check for "noindex tags" on individual posts—these can prevent indexing even if the blog itself allows it.
- Turn on "Redirect HTTP to HTTPS" to ensure secure and consistent access.
- Enable "Search Description" to allow custom meta description, which improves SEO.
- Set "Allow blog feed to FULL", as it helps search engines read your content like a sitemap.
3. Mistyped Incorrect Blog URL
- Be sure to register the correct blog address in Search Console. The proper format for a default Blog URL is:
The / at the very end may or may not be present.
4. Other Factors that Prevent Indexing
| Why Dose This Redirect Error Keep Happening on my Blogger Site Even After Changing my Blog Template to a Modern One?
If you're seeing a "Redirect error" message in Google Search Console, it means that Googlebot is not able to retrieve your blog's page correctly.
There's a redirection issue somewhere between your blog's URL and the actual page Google is trying to reach.
So, why does this happen—even after you've configured everything correctly? Let's go over the possible causes and what you can do to handle them.
Possible Causes and Recommended Actions
1. Test with a Redirect Checker Tool
Use an online tool like Redirect Checker (e.g., https://httpstatus.io) to analyze your blog URL.
- If the result shows "Too many redirects" or more than 3 redirect steps, your blog may be misconfigured.
- This could be due to incorrect HTTPS settings in Blogger, or external redirection code like:
- a <meta refresh> tag
- or JavaScript-based redirects in your blog's HTML <head> section.
Double-check your Blogger settings and remove any unnecessary redirect scripts from your template.
- If the result of the status code is "200 OK", it is considered normal.
2. Double-Check Blogger Settings
Go to Blogger >Settings and verify the following:
- Use HTTPS → On
- Redirect HTTP to HTTPS → On
- Custom Domain → Off (Stick to your default .blogspot.com domain)
If these settings are incorrect, when Googlebot accesses the sitemap or root page with http:// , it fails to properly switch to https://.
The correct settings ensure Googlebot is consistently directed to the secure version of your blog.
3. Check Your Property Registration Format
In Google Search Console, make sure your site is registered as a URL prefix property, not a domain property.
The correct format should look like this:
https://yourblogname.blogspot.com
Avoid registering with:
- http:// (non-secure)
- www. (Blogger doesn't use this by default)
It often happens to beginners. Registering with the wrong format can confuse Googlebot and trigger redirect errors.
4. Add a New Property in Search Console to Start Totally Fresh (Most Suspicious)
If your blog previously used an old Google template (like Dynamic Views) with anchor-based or JaveScript redirects, Googlebot may still remember your old indexing failure.
Even after switching to a newer, SEO-friendly template (like Vtrick), Search Console may continue showing redirect errors, because the previously failed index attempt was cached. In this case, simply resubmitting the sitemap won't be enough.
Therefore, go to Search Console, click [Add property], and re-register your blog using the correct URL prefix format. This helps Google treat your blog as a fresh, clean entity—and indexing errors often resolve shortly after.
5. Request Indexing
Request indexing directly for new posts or the blog's home URL using the URL inspection tool in Search Console. If an indexing error occurs, completely re-register the property and request indexing again. Once a day is sufficient.
6. Sitemap Address Stabilization
When submitting a sitemap, modified feed addresses such as "/feeds/posts/default?orderby=updated", "/atom.xml", and "sitemap.xml" can be unstable or cause redirection errors. These are common in Blogger.
The desiarable sitemap address to submit to Search Console is as follows, and this alone is sufficient and stable.
7. Use the Default or Trusted Template
"Redirect Errors" also occur when a particular theme includes automatic redirect code (meta refresh, JavaScript redirect). This is common in some older Blogger themes (e.g., Dynamic Views).
So, avoid older themes such as Google Dynamic Views. I would recommend modern themes such as Vtrick, Contempo, and Soho, if you are looking for a free theme.
| How I Handled It: Step-by-Step
🔑Key Strategy: Fresh Start with the Same Blog Address
If your blog is already registered in Google Search Console (GSC) and you're still seeing redirection errors or indexing problems, the key is not to fix the old property—but to register it again as a brand-new one.
Even if you're using the same blog address, you can "reset" the indexing process by using "Add Property" to create a completely fresh URL prefix property.
If you access GSC through Blogger Settings > Crawlers and Indexing > Google Search Console, you'll be directed to the existing property, where the redirect error may persist. Instead, go directly to the official GSC site:
https://search.google.com/search-console
Then:
- Click [Add Property]
- Select URL Prefix
- Enter your full blog address (e.g., https://yourblogname.blogspot.com)
- Complete verification
- Submit a sitemap and request indexing again
This step is often the real turning point when dealing with persistent redirect issues in Blogger.
🙏Step-By-Step Actions
1. Check the Blogger Settings Again
- Visible to search engines→ON
- Custom robots.txt→OFF
- Noindex tags→ NONE
- Redirect HTTP to HTTPS →ON
- Search Description→ ON
- Allow blog feed to FULL→Enable
2. Test with an HTTP Redirect Checker
3. Re-register Your Blog with URL Prefix Property (Most Critical Step)
- Go to the Search Console homepage:
https://search.google.com/search-console
Make sure you're logged in with the Google account connected to your Blogger blog.
- Click [Add property]
In the top-left corner, click the dropdown arrow next to your site name. Then click the [+Add property] button at the bottom. Even if your blog URL (e.g., https://bloggerx110.blogspot.com/) is already listed above, adding it again here will reset the redirect error cache.
- Choose the URL Prefix method
On the popup screen, select URL prefix (not Domain), and enter your blog address exactly (e.g., https://bloggerx110.blogspot.com/). Then click [Continue].
Search Console treats each property as a separate unit. So even if the address looks identical, this counts as a new, clean property.
- Automatic ownership verification
If your blog is connected to the same Google account, you'll see a message like "Ownership verified."
- Access your new property
Click the [GO TO PROPERTY] button to enter your new dashboard.
4. Resubmit a Clean Sitemap
- Click [Index] > [Sitemaps] in the left menu.
- In the "Add a new sitemap" field, enter:
feeds/posts/default
- Then click [Submit].
The newly registered property is literally recognized as “a new site.” to Search Console.
5. Manually Request Indexing in Search Console
Click the [REQUEST INDEXING] button on the top right. This is a request to Googlebot to "register this first." Once the request is complete, you will see the message "Indexing requested."
6. Time and Patience
It can take several days or weeks (3 to 14 days) for Googlebot to fully recognize a newly registered blog.
7. Check Indexing
After 1-3 days, type the following (your specific post URL) into the Google search box. If this page appears in the search, it is successfully indexed. e.g.:
| What Happened After Handling It?
Unfortunately, I still get the same "Redirect error" issues.
| 5 Smart Ways to Handle Indexing Delays or Errors in Blogger
1. Manually Request Indexing for Individual Blog Posts
Instead of focusing on your homepage or sitemap, submit specific post URLs in Search Console one by one.
- Go to URL Inspection
- Enter a full post URL, e.g.,:
- Click Request Indexing
This often works faster and can trigger Google to start exploring your blog more deeply.
2. Don't Repeat the Same Sitemap Submission
If your sitemap keeps showing "Couldn't fetch", avoid resubmitting the same one repeatedly. Google may temporarily block redundant requests. Instead, just submit once, and move on to other methods like manual indexing.
3. Keep Posting and Updating Content
Stay active. Publish new posts or slightly update existing ones to show Google that your blog is alive and valuable. Google favors fresh, connected content.
- Add internal links between posts.
- Update titles or add new images with ALT tags
4. Register Your Blog with Bing Webmaster Tools
Bing has own indexing system. If your blog gets indexed in Bing first, Google may pick up your pages through cross-linking and traffic signals.
5. Be Patient and Avoid Over-Submitting
Indexing takes time, especially for new or recently redesigned blogs. Avoid:
- Submitting the same URLs daily
- Making too many theme or setting changes at once
Instead, give Googlebot a few days to revisit after your indexing requests.
Congratulations
"Redirect error" is reported quite frequently among users of platforms such as Blogger, Wordpress, Shopify, and Wix. Redirect errors on Blogger can be frustrating, but they're fixable. By testing your redirects, checking your settings, and re-registering your blog properly, you can clear the way for better indexing and improved search visibility.
Even if it takes time, you're not doing anything wrong—Google Search Console often takes time to update and reflect new status changes. Stick with these smart, calm actions and you'll see results over time.
