Skip to main content

Blogs Published To A Custom Domain Are Showing A Redirect Alert, To Readers Using The BlogSpot URL

When you setup a Custom Domain, the setup wizard provides encouraging advice
We won't leave your readers behind! will redirect to your custom domain.

Blogger accomplishes this bit of trickery, using standard Internet protocol - a 301 Redirect, which equates "" to "". The redirect is setup only after you setup a "CNAME" referral, pointing "" to "". This means that anybody viewing "" gets "", published to a Google server and indexed through "". And anyone viewing "", intentionally, gets it directly from the Google server, as indexed through "".

Recently, however, hackers and spammers have started to setup their blog "", publish that to a custom domain, then redirect the custom domain not to "", but to "". The reader viewing "", now gets "", indexed by "".

Blogger is looking for cases of this deviousness. Unfortunately, right now, they are looking too casually, and are seeing false positives. Legitimate blogs, that are genuinely published to a Google Custom Domain, are showing an alarming notice.

This isn't good for your readers.

This isn't good for your readers either.

Who wants to be warned that they will shortly be viewing an untrusted blog?
This blog is not hosted by Blogger and has not been checked for spam, viruses and other forms of malware.
Visions of hacking abound in the minds of the readers seeing this.

If you have an established custom domain, it's likely that everybody looking at your blog is using the custom domain URL, in my above example "", and nobody sees this alert in any great number. If you just setup your custom domain, though, and are now seeing this, you're probably suffering two problems.
  1. Your readers are a bit confused, if they use "".
  2. The search engine spiders aren't going to index your blog, as either "", or as "".
In other words, you're out of luck.

>> Top


Kathy said…
This is unfortunate. I'm one of the legitimate redirects. I don't suppose there's a way to contact Google to have them re-examine my blog and see that I'm not a hacker/spammer?
Writerly Whimsy said…
That's really a shame. My redirect is legit through google too, but the same thing is happening to me.
Chuck said…
Be patient, guys. I just got a status of "escalated", this afternoon.

I'd like to think that they were aware of the problem earlier, but maybe not...
Amit said…
i have the above problem with my blog to

what do i do?
i had started a thread

after that it was okey. but from few days it stated again to rediret problem.
Chuck said…

We'll only be able to fix your problem once the overall problem is fixed.

If your problem continues, after Blogger fixes the problem described here, then we'll work on your problem. Be patient, you'll gain nothing from restating the issue.
Toby Rogers said…
I've got the same problem. Thanks for shinning a light on it. Blogger really needs to fix this ASAP or I'm gonna have to move to a different platform. I see your message of "escalated status" from 11/3/08 -- but it just started showing up on my system about a week ago.
Fur Diva Mommas said…
Why are they out of luck? Can't they at least drop using the custom name and go back to the blogspot until there is a fix? We saw that page and have not yet changed to our custom name. We did not like it so we quickly switched back to the
Fur Diva Mommas said…
Amit....we went to both of your urls and didn't see the redirect. Does that mean you don't have the problem anymore?
Chuck said…

People are out of luck because most bloggers, when they sign on to the idea of having a shiny feature like a non-BlogSpot URL for their blog, really don't want to go back to BlogSpot, even temporarily. Some bloggers have even given out the custom URL to friends, before experiencing the problem.

Playing ping pong with the URL won't help with search engine relationships, either. You need a consistent presence, to build up a reputation on the Internet.
John Rodriguez said…
Hi Chuck,

Thanks for your help, both here and in the Blogger Help Group.

I moved a client's blog to a sub-folder on their site last week (FTP publishing), and their blog visitors immediately dropped 95%. I'm sure a big part of it is the IE "The page cannot be displayed" error.

Obviously, with spammers and hackers abusing the redirects, this will be a difficult problem for Google to tackle.

Do you know if they are doing any kind of manual verification on these redirects?

(Not that that may be worth anything, because people can just do another redirect once verified.)

I'd reported the issue to Google last week, but no response -- I didn't even get a "We've received your msg" auto-reply. Do you think it would be worth it to submit another report?

Bombchell said…
This is very annoying, I regret starting my blog with blogger, because they constantly have such issues

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: