Skip to main content

Account / Blog Recovery, And Anonymous Ownership

We see occasional evidence still of confusion about blog ownership, and dashboard access, in Blogger Help Forum: Get Help with an Issue.
I can find my blogs on my profile page, and by Googling them - but I can't update them, post in them or access them in any way - even though the system says I'm logged in.
This blog owner is logged in to the wrong account - but has no way to recover, because the blog is offline.

If you had a blog, you don't have it now, and it's not online, then it was deleted - by Blogger, or by someone else.

Blogs are commonly deleted or locked, by Blogger, for three reasons.

There are three common causes, if deleted by Blogger. Each require owner action - not only a Blogger solution.
  1. The account was deleted because of repeated TOS violation.
  2. The account was locked because hacking activity was detected.
  3. The blog was deleted for spam / TOS violation.

In either case, if the blog is not visible on the dashboard, and no notice is seen, the owner is not using the account that owns / owned the blog. This is a result of anonymous or obscured blog ownership.

The blog owner must take the first step, in recovering a deleted blog.

It's up to the owner, to figure out what account that owns the blog, and to login to that account. The owner must either initiate account recovery (for hacking activity detected), or initiate blog recovery (for a deleted blog, whatever the cause).

Whether this involves an inadvertently created additional account, when accepting blog membership, or logging into Blogger - or an intentionally created additional account, for anonymity - only the owner can resolve this problem. This is the price of anonymous blog ownership - protection promised to us, by Blogger.

Blogger allows - and supports - anonymous ownership.

Blogger allows us to publish blogs anonymously, and under any account that we wish. They can't tell us what account we have forgotten - because successful anonymity protects us against identification.

If the blog was online, the "Forgot your username or password?" wizard would be a useful resource. Without use of "Forgot?" - which does not work with deleted or private blogs - the owner must login blindly, to recover the blog.

In this case, ones friends may be the best resource. Sometimes, an online cache may provide a clue - but online cache is not always available.

Only the blog owner can resolve an anonymity problem.

Some blog owners regard anonymity protection as a Blogger design problem - and wait for Blogger to fix their problem. This is not a design problem - and only the owner can resolve this problem. This is not a result of flakey account / blog recovery.


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: