Skip to main content

Externally Published Blogs, and the Redirect Interstitial Warning

A couple months ago, I noted that blogs published by FTP were showing, in some cases, a new (and not popular) accessory - the redirect warning.
You're about to be redirected

The blog that used to be here is now at
Do you wish to be redirected?

This month, we have numerous reports of blogs published using both custom domains and FTP are showing this warning, when you load them using the blogspot URL.

This is reasonable for FTP Publishing, not so for custom domain publishing.

Blogger needs to be more selective when showing this warning.
  • You expect to see this for blogs published by FTP. FTP Publishing is to an external server that could easily contain malicious content placed there directly, without being published through Blogger.
  • You do not expect to see this, nor do you want to see this, for blogs published to custom domains. Content published to custom domains is hosted on Google servers, published through Blogger, and only from Blogger blogs.

(Update 2009/04/04): This may not always be a bogus warning. Looking deeper, this may be a righteous display, in some cases.

>> Top


letdpplwatch said…
is their any way out to get this problem fixed as today i also set my blog on custom domain and seeing this warning and also my traffic has gone down to 5% dats so u knw any way out?
Chuck said…
Today? In your dreams, maybe.

Seriously, I'm compiling a list. I will need you to post in GBH: Something Is Broken, with BlogSpot and domain URLs, so I can point to your post there.
the Muse said…
hi chuck I'm completely clueless at the moment. Is this a new problem or it's always been like this? I just noticed tonight that if someone is visiting my blogspot address it's not directing to my custom URL...wasn't sure if that was new or it's always been like that.

And as of no, from reading your comments, there isn't a fix?!

Chuck said…

To understand the problem here, you have to understand the difference between custom domain and FTP publishing.

Both custom domain and FTP publishing let you publish to a non BlogSpot URL. With custom domain publishing, the non BlogSpot URL is hosted on a Google server, and is subject to scanning for undesirable content.

Custom domain published blogs, then should not be subject to the "Redirected URL" warning that says "This blog is not hosted by Blogger", because it is hosted by Blogger, just not BlogSpot.

FTP published blogs, however, are published to non Google servers, where you the blog owner could push any undesirable content at any time, and Google would never know. Blogs published to external servers, then, need the warning.

The fix would be to have the program that generates the "Redirected URL" interstitial be sensitive to blogs that are published to non-BlogSpot Google servers (custom domains), and to not label such blogs.
Chuck said…

Is your blog published to a custom domain, and showing the interstitial warning? If so, what's the URL?
Colleen said…
I am having this same issue as of today, February 10th, I was not having the issue yesterday. My domain is and the links on the left hand side of the page are getting this redirect warning. Can anyone help me fix this?
Colleen said…
Sorry -- I am publishing via blogger to a custom domain.

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: