Skip to main content

Recreating Vs Restoring A Blogger / Google Account

People make mistakes - and that bare fact is the basis for so many interesting problem reports in Blogger Help Forum: Something Is Broken.

If you made a mistake and deleted your Blogger account, maybe you're just now noticing that the blogs owned by the account have disappeared, also.

Blog has been removed

Sorry, the blog at has been removed. This address is not available for new blogs.
Now, what to do?

If you want a deleted account or blog back, there is only one thing for you to do - get the Blogger account restored.

Get the deleted account restored - and it's best done within hours of deletion.

You have to get the restore done, promptly. Every hour spend wondering what to do reduces the chance of a successful recovery.

Don't recreate the deleted account - get the deleted account restored.

Some people make a second mistake here, and setup a new Blogger / Google account, using the same email address.

With a recreated account, you have a Blogger / Google account with the right email address - but without access to any of the blogs owned by the account just deleted. Access to any Blogger blog is only possible, using the right Blogger account.

When you re create a Blogger account using the email address of a Blogger account just deleted, you are creating a new Blogger account. You cannot control blogs, owned by an account just deleted, by recreating the account. You have to get the deleted Blogger account restored, so you can re establish access to the blogs.

If you recreated the account, you first have to delete the recreated account.

Having created a new Blogger account (with the same email address as the previously deleted account), you now have a new problem. Google can't restore your previously deleted account, when you have created a new account using that same email address. In order to have the previously deleted Blogger account restored, you have to delete the Google account just created.

That's your only choice, now. Do it, promptly. Every hour reduces chance of success.


Some Blogger blog owners accidentally delete their Blogger / Google accounts, then regret their action.

With an account deletion, every hour elapsed since deletion reduces the chance of ability to recover from the mistake. And the account needs to be restored - not recreated.


loveurbelly said…
thanks so much for this, very helpful. I restored the user but it hasn't automatically fixed my missing blog post images (that was the only thing that went missing) do you have any further links on what to do when the user is restored? thanks again

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: