How I Fixed the URL Indexing Redirection Error in Google Search Console After Connecting a Custom Domain to Blogger
Connecting a custom domain to Google Blogger sometimes causes unexpected redirection errors during URL indexing. Even when the domain and DNS settings are correct, Search Console may still report:
“URL is available, but indexing failed due to a redirection error.”
In this guide, I’m sharing the exact steps I followed, what Gemini suggested during debugging, and how the issue was ultimately resolved.
If you recently connected a custom domain to Blogger and are seeing redirection-related indexing errors, this walk through may help.
1. Background: Custom Domain Connected to Blogger
After purchasing a personal domain and completing all DNS settings through my hosting provider, I connected the domain to my Google Blogger site.
Then, I added my site to Google Search Console as a new property (example.pe.kr).
Everything looked normal at this stage—no DNS or server issues.
2. Index Request: Redirection Error Appears
When I submitted a URL for indexing in Search Console (simply pasting it as https://www.example.pe.kr/xxx), Search Console recognized the page but returned a redirection error.
To troubleshoot, I tested the indexing request again using a slightly different form:
- First attempt:
https://www.example.pe.kr/xxx - Second attempt:
https://example.pe.kr/xxx
Surprisingly, both attempts resulted in the same redirection error, even though the URLs resolved correctly in the browser.
3. Debugging With Gemini: What We Checked
Using Gemini’s suggestions, I reviewed several possible issues :
✔ Blogger settings — OK
Canonical redirects and HTTPS availability were correctly enabled.
✔ Domain DNS configuration — OK
The hosting provider’s DNS panel matched Blogger’s recommended records.
✔ Blogger’s original base URL
By inspecting the HTML source, I confirmed that the canonical domain was:
https://www.example.pe.kr/xxx
✔ Manual URL access test (4 variations)
I checked all four versions:
All of them correctly redirected to https://www.example.pe.kr, with no obvious redirect loops.
According to Gemini, sometimes multiple redirect hops (3–4 chain steps) may trigger Search Console warnings—even if the browser loads normally.
If https://www.example.pe.kr is the canonical address, why did Search Console show a redirection error even when using the correct URL?
This raised a question:
4. Solution: Add the WWW Version as a Separate Domain Property
Gemini recommended one more step:
š Add a second property in Search Console using the WWW version
https://www.example.pe.kr
When I added the property, Search Console immediately confirmed ownership without additional verification (because DNS was already configured).
But interestingly:
- Even after adding the new property,
- The Search Console sidebar still displayed only one visible domain property (example.pe.kr).
This appears to be a Search Console UI behavior, not an error.
š How to Add Your Custom Domain to Google Search Console
5. Re-Running the URL Inspection Tool
After adding the WWW version as a property, I tested URL inspection again.
This time:
- The URL was successfully indexed
- No redirection errors appeared
- Search Console confirmed the page had been crawled
Although the page was still not visible in actual Google search results, the indexing report itself showed “Indexed” when entering the URL manually.
This indicates indexing is functioning correctly, and visibility will update once Google processes the page fully.
6. Notes and Limitations
This solution may not be the official fix, but it worked in my case, and it appears to help when:
- Blogger’s canonical URL uses the WWW version
- Search Console property was originally added without it
- DNS redirects are correct, yet Search Console still detects multiple hops
After adding the WWW property, I noticed a significant improvement in indexing behavior.
Some URLs are still not indexed yet, so I will need to continue monitoring overall performance.
However, before adding the WWW property, almost none of my URLs were indexed.
Now, when checking individual URL inspection, approximately 80% are marked as indexed, which is a major improvement.
Although not a guaranteed solution for all cases, this step clearly helped stabilize indexing for my Blogger site.
Related Posts
Soft Closing
This was my experience resolving the redirection indexing issue. If you’re facing similar behavior after connecting a custom domain to Blogger, this approach may be worth trying.
