Skip to main content

Observe The Spirit Of The Law, Not Just The Letter

We see too many problem reports, in Blogger Help Forum: Get Help with an Issue, about inconsistent content penalties.
My blog was deleted - then I got a letter of apology from Blogger. But my blog was deleted, again!
My blog does not contain copied content, why was it deleted?
These blog owners, and others, are complying with the letter of the law - as they see important.

Unfortunately, other blog and website owners have rights too - and Blogger will also enforce their rights - now, and in the future. To have a righteous blog, you have to remain innocent of all possible TOS violation categories.

The actual authoritative documents, to identify TOS Violations, are Blogger Content Policy, and Google Terms of Service.

If both you, and the owners of the blogs and websites that you offend, simply comply with the letter of the law, you, and your blogs, will still be vulnerable. If you repeatedly push the limits, your Blogger account and blogs will be vulnerable, as a repeat offender.

The DMCA Claim process includes a "false accusation" penalty.
Please note that you will be liable for damages (including costs and attorneys' fees) if you materially misrepresent that a product or activity is infringing your copyrights.
TOS Violation, in general, provides no similar protection - and if you offend somebody (even while staying within the letter of the law), the other party may report you.

The closer you approach the limits, the more carefully your blog must be judged - and the longer your blog will be down, while being judged. If "time" == "money" for you, the longer the blog remains offline, the more money you lose.

The FAQ, What Types Of Blog Content Are Considered Abusive, By Blogger Spam Mitigation Policy?, provides examples of known TOS Violation problems. It's not all inclusive - or final.

Very few blogs will be guilty of all of the examples, described in the FAQ - or even all possible complementary examples. If you have a large blog, with nothing but syndicated content, please don't claim innocence, of one unrelated category.
I never publish porn!
And if your blog contains monetised porn, don't claim
My content is all my own! I never steal content, from other blogs!!
Also, if your problem is with copied content, please don't just delete, when sent a DMCA notice - and please, don't repeat! Either mistake will, eventually, leave you with a deleted Blogger account.

And don't be offended if you don't get advance warning, properly delivered to your email Inbox, in time for you to conveniently remove your abusive content.

Remember, even if you are judged innocent, eventually, you may have to deal with the penalties. And similar blogs, confirmed as legitimately abusive, will subject your blog to confirmation.


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: