Skip to main content

Custom Domain Publishing - Moving Back To BlogSpot

When you setup a custom domain properly, and publish a blog to a non-BlogSpot URL, the BlogSpot URL remains active.

With the BlogSpot address active, you can move forward to the new address, without worrying about loss of readership, or search engines indexing problems. Both the old (BlogSpot) and new (custom domain) addresses will work, for eternity. This feature, in my opinion, is one of the ideas which exemplifies the reputation of Google, for innovative design.

If you decide to move back, and publish to BlogSpot, this may not be such an easy task.

Blogger provides the BlogSpot --> custom domain redirect, to reduce readership loss from the move to the custom domain.

You can't get automated redirection from the domain, back to BlogSpot.

If you move backwards, you won't, automatically, have a redirect from the custom domain to BlogSpot. If the search engines start to index your blog using the new URL, and you publish your blog back to BlogSpot, the indexed URL will be broken.

Upon clicking on a search engine hit entry, your potential readers will see, instead of your blog,

Server Not Found
Error 404

This won't encourage new readers.

You may be able to forward the domain to the BlogSpot URL.

If you truly need to move back to BlogSpot, if your DNS host will permit, and if changes in Blogger don't prevent this from working, you may be able to use a "301 Redirect" from the custom domain URL to the BlogSpot URL. This will, of course, work only as long as you continue to pay for DNS hosting of the domain.

You can't forward the domain, and save money by not having the domain.

If you decided to move back to BlogSpot for financial reasons (save $10 USD / year??), you won't be able to do this.

When you move to custom domain publishing, there is some risk - and you will have some lean hit rates, at least temporarily. But the lean hit rates, when publishing the blog to a domain URL, are nothing - compared to what you'll get when you publish the blog back to BlogSpot.

My advice? Move forward, not backwards. And plan the change, before you buy the new domain, not after you do so. And give your readers warning, before moving back.


Abdul Basith said…
In case, My domain is expired, after that can i remove custom domain from dashboard and continue using blogspot url?
Chuck Croll said…

As long as the blog is accessible on your dashboard, you simply follow the above procedure.

Or, is there a detail that you've left out? Domain expired or not, moving back to BlogSpot should be the same.
Look, I really do not understand this. I had purchased a domain which I used for my blog. Unfortunately I lost it,because the bill was sent to an e-mail-address I don´t use anymore. It seems like someone else bought it to earn money, but I am not interested to buy it. Now I just like to use the original blogspot-address. Is that not possible??!
Kind regards,

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: