Skip to main content

Custom Domain Publishing And The Broken BlogSpot Redirect

This weekend, as the broken BlogSpot to custom domain redirect problem stretches into its 4th through 5th days, we see a diverse crowd of bloggers complaining about the problem. Some bloggers have been following this problem since Wednesday, others just discovered it today. One group of complainants which always intrigues me is the ones with the biggest and most popular blogs.
What? Blogger can't do this to me, and get away with it! I'll move my 10,000 visitor / day blog to WordPress!!
as if the daily visitor count makes them more important.

Everybody who is hurting, because of this snafu, is hurting because of links that continue to refer to the BlogSpot URL. The BlogSpot URL is the primary blog address until you publish the blog to a custom domain, and only until then. When you publish the blog to a custom domain, it becomes a secondary blog address. It's a secondary blog address which should diminish in importance, steadily, as your the custom domain address becomes more mature.
  • As soon as you publish your blog to the custom domain, you cease issuing the BlogSpot URL.
  • As the domain becomes more mature, you have more new inlinks pointing directly to the domain.
  • As the search engine databases are updated, both old and new links to the blog will point directly to the domain.
  • As you publicise the blog, and encourage new inlinks, you should also encourage the conversion of existing inlinks to point directly to the domain.

If you buy a new car, you don't leave it in the garage and keep driving the old car. Most people make up places to drive, just to show the new car off. Similarly, with a new non BlogSpot URL, you want people to know about it - both for direct browsing and for newsfeed access (Following / subscription).
Hey, check out my blog with it's new URL!

As the custom domain URL becomes used, the BlogSpot URL should diminish in importance, both absolutely and relatively. Your ultimate goal should be that it would have zero importance.

>> Top


I'm keeping my fingers crossed & hope this gets sorted out really soon. Reading about it on your post makes me feel better that the issue is being addressed! have a good day!
rajesh said…
I think google should be given some time to rectify the issues. They just cant do a magic trick. People should have some patience.
Rick said…
The problem for custom-domain bloggers of any size is that people don't update 'legacy' links unless they have to. I only realized that a big blog I visit was on a custom domain when the link that I use to get there from another big blog started sending me to the redirect page.

Ironically, the longer the redirect stays broken, the more people will update links. But once Google fixes the redirect, people will forget about it and leave their links as they were.
Alanna said…
Wasn't it just last week that Rick Klau (Blogger product manager, former EVP at FeedBurner) was going on and on about how superior Custom Domain is, how Google has so much control over it, how it's Google's preferred platform?
enfield.23 said…
Nice write-up. This one is the blog which I like most,I would like to thanks that master brain who make all this for the readers like me.keep up writing good job.

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: