Skip to main content

Blogger Gives You A Second Chance - If You Act

As Blogger fine tunes their abuse and spam classifiers, we're seeing chronic abusers admitting their mistakes, in Blogger Help Forum: Learn More About Blogger.
My Blogger account was just deleted! Recently, we received a message from Blogger, advising that one of our articles has been deleted because of copyright issues. We were further advised that if we re published, Blogger would have consider it as an act of rebellion against Blogger's policy.
In most cases, this would represent a non repentant abuser, righteously deleted.

Blogger allows second chances, for abuse and copyright violations - if you act promptly.

The Blogger violation warning policy is not perfect.

Blogger Policy Enforcement sends out notices, with the hopes that the people abusing TOS will act, and avoid additional violations. With some people, who blatantly and multiply violate, avoiding additional notices is not easily done.

The more offenses, the greater chance extreme and prompt action will be taken.

People with multiple violations, in their blogs when an initial violation notice is sent, are more likely to be detected again, generating more notices. The more violations discovered, the greater chance the blog owner will be classified as a non repentant, repeat offender - and the blog will be deleted.

If multiple blogs are published and are offensive, chances are greater that the blog owner will be classified as a defiant, non repentant offender - and the Blogger account too will be terminated.
We'd like to inform you that we've received another complaint regarding a blog that you administer. Upon review of your account, we've noted that you've repeatedly violated the Terms of Service: Given that we've provided you with several warnings of these violations and advised you of our policy towards repeat infringers, we've been forced to disable your Blogger service.
This may involve another team blog issue, in some cases.

The more offending blogs, and the more offending blog content, the greater the chance that a defiant, non repentant offense will be determined, by Blogger Policy Enforcement. Blog owners who intentionally and repeatedly test the limits, of Blogger patience, will eventually regret their attempts.

Blogger sends out the notices, for good reasons.

Blogger sends out each notice, for a reason - to have abusive activity stopped.
  • Stop doing, what you're doing.
  • Remove what you have already done, that may violate TOS - even if not cited, specifically.
The best policy is to not offend, period. The next best policy is to act immediately, when receiving a notice.
  • If you're not violating, appeal the notice.
  • If you are violating, see the list, above.
If you're truly innocent, use ChillingEffects, and appeal. If you're even slightly guilty, clean up your act. The more guilty you are, the quicker you need to act - and the more cleanup you need to do.

For best results, act before you get a notice.

If you received the first notice, one day - a second notice, the following day - and your account was terminated, on the third day, this is the result of blatant policy violation. Don't wait until you get two notices, in two days, then mull it over.
Gee, maybe I should stop doing that?
Act now, and clean up your blogs - before it's too late. Blogger sends out notices, using best effort possible - and everybody may not get every notice, when sent. Don't take lack of notices received, as permission to continue dodgy practice.

You may get one final chance.

In some cases, an "account suspension" notice may come with a final chance for redemption.
Next steps for suspended accounts: If you believe your access to this product was suspended in error, contact us.
That advice will provide a link, to a final appeal form. Click on the link, and follow instructions. This is not offered, in all cases. If it is offered, take it - and follow instructions, to the letter.

You may get one last chance. If so, use it wisely.

Or the account may be terminated, with no redemption offered.

In some cases, with the Blogger account terminated, you will simply have to start over - and clean up your act, with your new account and new blogs. Even if this does not happen, you'll have to deal with the consequences.


Linda Simpson said…
I have lost over 20 followers on my googles friend connect on my blog in less than an hour. What is going on? Some help needed.
Chuck Croll said…

Thanks for the observation, you are not alone.

Some problems, only Google can explain. Maybe if enough people report the problems, some Blogger Engineer will break himself from a weekend doze, and investigate.

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: