Skip to main content

Nude Celebrity Blogs Are Not Allowed In Blogger

We've had some photo / video blogs under review recently, and confirmed as TOS Violations.

The citations were first seen late last year, and associated with the "Jennifer Lawrence" / "Anna Kendrick" celebrity leak photos scandal.

We're asking Blogger Support for details of the policy - but right now it appears that Google is now forbidding any "nude celebrity" photos or videos, after their public relations problems surrounding the Jennifer Lawrence photos.

Besides being considered pornography by some, "nude celebrity" photos constitute a DMCA violation (some celebrities may consider their photos to be commercially valuable), and invasion of privacy (photos were taken without consent).

Google was, as noted, unsuccessful in getting the Jennifer Lawrence photos completely removed from search engine cache - but that does not mean that they will allow similar content, or links to content, in their servers. And using the Jennifer Lawrence episode as a learning experience, they are being prudent in forbidding similar nude photo / video distribution.

The "nude celebrity" policy is part of the Blogger Content policy, under "Adult Content: Exceptions".
There are some exceptions to our adult content policy:
  • Do not use Blogger as a way to make money on adult content. For example, don't create blogs that contain ads for or links to commercial porn sites.
  • We do not allow illegal sexual content, including image, video or textual content that depicts or encourages rape, incest, bestiality, or necrophilia.
  • Do not post or distribute private nude or sexually explicit images or videos without the subject’s consent. If someone has posted a private nude or sexually explicit image or video of you, please report it to us here.
Apparently, the consent issue will protect both celebrities, and non celebrities, alike.

Google cannot control the Internet, in general - so it's unlikely that "nude celebrity" photos will eve be erased from the Internet, completely. People being what they are, there will always be demand for these photos - and where there's demand, there will always be supply. And Google accepts search content from other search engines.

Spammers being what they are, some "nude celebrity" content, and worse, will always be problematic, to Blogger and Google. However, the new policy, and improved TOS Violation detection, will enable Google to make such content short lived.

If you wish to provide or link to nude celebrity photos or videos, in online content, please don't use Blogger blogs to host your content.


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: