Skip to main content

Confusion From The Blogger Blind Login Policy

We've known, for a while, the dangers of logging in with the wrong Blogger account.
My dashboard has no blogs!!
My Reading List is empty!
Blog owners and readers, alike, have been reporting this problem, for years.

With the new Google multi account login, this problem has become more noticeable, for some blog owners and readers.
My Blogger account was merged, to an an account with an empty dashboard.

Sometimes, the dashboard lacks blogs - at other times, it lacks menu items, or reading list entries. In either case, the account owner needs to login to a different Blogger account.

With Blogger blogs, wrong account login frequently starts with the "Sign In" - or maybe "Sign Out" - link in the navbar.

Clicking on "Login", the blog owner (or reader) is presented with the Google login screen. If this is the first login since the browser was restarted or cookies were cleared, the login display will resemble the login wizard, before the latest change. The Blogger has to simply enter the right account name and password.

If this browser has been used previously, the Google account(s) previously used will be offered, in a menu list, for login. Blog owners and readers, not realising the effects of Blogger blind login, or of inadvertently created Blogger accounts will occasionally use the wrong account - and will find the wrong dashboard.

This story becomes more confusing, with either a locked account / blog - or with a team blog. Ownership diagnostics, for deleted / locked accounts and blogs are very limited. With the blog in question offline
Blog has been removed.
It's simply not possible to identify the Blogger profile used by the owning Blogger account.

When we advise about blog deletions, it's always useful to know whether the blog was deleted because the owning account was deleted or locked - or because the blog itself was deleted for a TOS violation. Without the ability to identify the blog owner, we can only suspect that the blogger might be logged in to the wrong account.

We also see confusion when Google Apps based email domains are involved.

Until all Blogger account owners learn to add accounts to the Google login wizard, using "Add additional account", "Manage accounts", or "Sign in with a different account", the Blogger blind login policy will continue to cause confusion.


Chuck Croll said…

The "bx-w7tr63" error code, like the "bX-rjv21c" and "bX-sf96g4", appears to involve people using Internet Explorer V11, which is not compatible with the Blogger dashboard.

Since you chose to disclose your email address, openly, in your comment, I deleted your comment.

You should consider using Google 2-Step Verification, if disclosing your email address is a common practice.
Pat said…
Thanks!! I'll see! 😟

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: