Home > Contemplations > WordPress Deactivates Blogs En Masse, This Blog Was A Casualty, & The QUICK Resolution By WP Support

WordPress Deactivates Blogs En Masse, This Blog Was A Casualty, & The QUICK Resolution By WP Support

A little after noon today my friend Alexander called me to tell me he couldn’t access my blog. At first I didn’t understand what he meant because (a) I didn’t believe it and (b) I really needed that coffee I was in the midst of making for a early afternoon boost so I had to have him repeat himself. Once I fully grasped his meaning my blood ran cold. I ran to my computer and opened up my blog. I was greeted with a page very similar to the one you see below:

LNN Suspended by WordPress Screen Shot 2011-12-14 via @CasieStewart

That image is actually via my friend Casie Stewart‘s Posterous here I don’t know why I didn’t screen shot it but there you go. I next opened up my blog’s dashboard and saw this (keep going below for full text):

LNN violated WordPress TOS cropped

This blog has been deactivated because we believe it does not comply with the WordPress.com Terms of Service or advertising policy.

If your blog is designed to promote affiliate links, get rich quick programs, banner ads, consists solely or mostly of duplicate or automatically generated material, or is part of a search engine marketing campaign, WordPress.com is not the place for you. Please use the Export feature to move your content to a more appropriate hosting service.

Occasionally we make mistakes. If you believe we have misclassified your blog, please click here to contact us as soon as possible so we can fix the problem.

Immediately I click the “click here to contact us as soon as possible” link and it took me to the Error Reporting Page you see below.

WordPress Error Report page

I quickly filled in the light blue-green box and explained that my blog was:

  • NOT designed to promote affiliate links
  • NOT designed to promote get rich quick programs
  • NOT designed to promote banner ads
  • DOES NOT consist solely or mostly of duplicate or automatically generated material
  • IS NOT part of a search engine marketing campaign
I didn’t know what else to say other than asking them to review my case. I didn’t know what I had done wrong but began to question every post as of late on my blog to think what had triggered this. I took to Twitter glumly and the outpouring of love and support was HUMONGOUS! I don’t know what I would have done without all my Twitter peeps supporting me when I told of what had happened so special thank you shout out to @AdrianGabeChen@beachrockinc@bnbutterscotch@casiestewart@Digiteyes@eLKDee@FunkyBarrister@GHBurgerBar@layvee@markhoffberg@PocketJLo@Shananigans5@stilez@wedding_crasher@_fishbar. These folks’ supportive words made all the difference as this situation wore on. Thank you for being there for me! I have already mentioned I Get By With A Little Help From My Friends, and you guys today were just a perfect case in point for that post. (Those names are all alphabetical and copied directly from their Twitter URLs. No favoritism, and I did not change capitalization just copy/pasted their URL, added the @, and removed the “http://twitter.com/#!/” part.)

One of my theories for what had happened included my Season 4 Being Erica quotes post from yesterday because as I already had 3 other ones it might seem “duplicat-ey.” (Yes, I made up a word, I was stressed out at the time and only had 140 characters to work with!)

Another theory I had, although I didn’t mention this to anyone at the time, was that maybe it was because I was helping sell tickets for #ATorontoXmas which is happening on Friday at the Steam Whistle Brewery. I dismissed that one because it was for charity and WordPress.com wouldn’t ban me for helping charity…would they?

I first noticed the issue at 12:29 PM when according to my phone logs, Alexander called me. My first tweet about it, was at 12:36 PM once I had confirmed the issue and then I reported back to people that I had emailed WordPress about the issue with the Error Report page seen above at 12:39 PM.

Amazingly, within an hour at 1:34 PM I got the email you see below from Anthony at WordPress.com. As you can see below, it was a misunderstanding and the system should not have done that.

WordPress apology email for mistakenly taking my blog down

I did a happy dance. I did another happy dance. I tweeted (more than once) that all was well and normal.

I then began to wonder what had caused WordPress.com to think I had violated the Terms of Service and/or advertising policy anyway? I wrote Anthony at WordPress.com a reply email and asked him. He again replied within record time getting back to me at 2:04 PM with this message (I highlighted exactly what he thinks caused it).

Wordpress explains why my blog was suspended

Seems the article I had written about the Textuality movie premiere in mid-April had triggered something. There was no way  in a million years I would have ever guessed that it was the cause when everything was going down (especially this blog). I also wonder why spam sites would be driving traffic to that site. My only guess would be it’s part of a DDoS attack (DDoS = distributed denial-of-service attack) to bring down the server for that movie for some reason but I have no idea why anyone would try to do that.

All I can say is thank you to my friend Alexander, to everyone on Twitter for the massive amounts of support, and to the folks at WordPress for the amazingly quick response time to this. Truly amazing customer service especially for a free service! My only suggestion to them would be to send out an email alert that, blogs had been taken down so people like me who were just caught in the crossfire of spam filters know to respond and get this kind of thing dealt with. Who knows when I would have looked at my blog if not for Alexander’s call.

This episode also brought to the forefront the fact that I am forever under WordPress.com’s mercy while I leave this blog hosted on WordPress.com. I am almost at the end of the 2011 Post-A-Day Challenge (although mine is going until January 4, 2012 to make it the full year) and I think it is high time I got more functionality out of this blog and maybe moved on from WordPress.com so this kind of thing won’t happen to me again. Some people on Twitter gave me some advice for hosting options and domain name registration options but I would also love to hear from you, my readers, any suggestions you may have in this regard. Let me know in the usual spaces but as usual, I prefer in the comments below.

Thanks and have a great rest of the evening!

Screen shot at the top of LNN unavailable via @CasieStewart‘s Posterous here. Her personal blog is here.

  1. December 15, 2011 at 10:54 am

    Instead of hosting on WordPress, I’d recommend exporting ALL of your posts from WordPress.com. Purchase a domain name (levynewsnetwork.com, if its available), and signing up for some hosting (I currently use midphase.com) to use wordpress.org to self-host your blog. That’s what I do for my own. Makes me more comfortable, because not only can I remove the “.wordpress.com” from my blog’s URL, but it gives me complete control over the blog.

    Once you have everything set up, you should be able to import all of the posts back into the new self-hosted blog.

  2. November 20, 2012 at 3:18 am


    I am getting message “ccieexpert.wordpress.com is no longer available”. WordPress has deactivated my blog. How can I get it back?

    Please reply and help me out.

    Best Regards,

    • November 20, 2012 at 6:19 am

      If you read the full post I go into a great amount of detail on what I did. Beyond that, I don’t know what to tell you because this was my one experience with this sort if thing happening.
      Best of luck!

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: