The Real Blogger Status

Not all Blogger blog owners know that the ability to comment is a privilege which they control. Like the ability to publish and read posts , it is also a responsibility which they need to control, carefully. Any blog owner who wishes to publish a blog, and not be subject to frequent deletion of the blog, as a suspected malware or spam host, needs to understand the responsibilities, and the risks.

We've been seeing a few problem reports, in Blogger Help Forum: Something Is Broken , from blog owners who are not aware of the risks from installing third party code, on their blog. Some blog owners are not even aware that the code being installed is not supplied by Blogger - and is not subject to the same coding standards as code supplied by Blogger. Third party accessories and code - from simple JavaScript that installs in the blog template, to attractive XML gadgets installed using the "Add a Gadget" wizard - has always been a challenge, to Blogger blogs. Knowing when you are installing code provided by someone other than Blogger / Google, and taking appropriate precautions, is your responsibility. What you install can affect your reader activity - and even your reader's computers.

We've explored the issues of Blogger account and blog recovery policy, repeatedly. We've mentioned the business concerns , the personal support issues , the strategic hacking possibilities , and even the personal implications of prevention . With all of the warnings, we continue to see evidence of blog owners who just don't understand the message, posting in Blogger Help Forum: Something Is Broken . I started a blog under an alias, to be able to post anonymously, and can't remember the login details or the e-mail recovery. How can I regain access to my blog?

Occasionally we see the innocent query in Blogger Help Forum: Something Is Broken , about the recently introduced Blogger feature - country code aliasing . Is there any way I can opt out from this constantly changing of the .com termination, into .be, .bg, or .ro, depending on where I travel? Not many Blogger blog owners realise the benefits of country code aliasing , which is, like auto pagination , a feature which is not optional. There are publicly available workarounds, which may bypass the effects of country code aliasing - and which may cause more trouble than simple URL confusion.

Sometimes, when you have a Blogger blog, published to a non BlogSpot URL, you may need to repeat the publishing process. Maybe, you want to change the BlogSpot or domain URL, or change the blog - or maybe the previous publishing did not complete, properly. If the blog is currently published to a non BlogSpot URL, you can't just publish it, again. You have to start by publishing the blog back to a BlogSpot URL, before you can again publish the blog to a non BlogSpot URL. Given the right planning, and understanding of the tasks involved, you can do all of this in 5 minutes - less time than it will probably take you to read these instructions.

We see the naive question sometimes, in Blogger Help Forum: How Do I? , about avoiding spam classification by publishing to a non BlogSpot URL. Can I keep my blog from being deleted, by publishing to a non BlogSpot URL? This is a complex question, because custom domain publishing provides several possibilities. But will the possibilities provide an opportunity for avoiding spam classification?

In 2012, Blogger gave us a suite of useful utilities to control how the search engines see our blogs . This feature suite includes the ability to redirect one URL in our blog to another URL in our blog . The "Custom Redirects" feature is easy to use - but like many Blogger features, not immediately so. Neither its possibilities, nor its limitations, are obvious to everybody.