I know I said last word on Google, but guess what? I lied. This is too important not to share with you.
So to recap, you know the story of how I lost my google traffic, and then how I tried to figure out why I lost my google traffic.
A couple days later, on a whim, I decided to revisit google’s cached pages of PixelRN.com. I wanted to be sure I wasn’t missing anything. So I clicked on one of the cached pages, did a “view source” to see the HTML, and low and behold I scrolled all the way to the bottom and found this:

So now I realized that someone had hacked into my wordpress blog and flooded it with hidden spam. This completely freaked me out. I mean, who would want to hack into my lil’ old blog? But at last I had found out exactly why I lost my search engine traffic: Google thought I was a spammer.
After reading about similar situations, I realized that my site was hacked because of a vulnerability in earlier versions of Wordpress (2.1 - 2.3). Previously I hadn’t been in any hurry to upgrade to the latest version of Wordpress, because I was afraid I might screw something up. I eventually got over this fear, and upgraded, but by that time it was too late.
So meanwhile, I changed my wordpress password, and upgraded to Wordpress 2.6.2.
I then became completely unable to log onto my wordpress admin page, meaning, I couldn’t update Pixelrn at all.
I spent some time on the Wordpress forums. I fooled around with Google Webmaster Tools. I fooled around with phpMyAdmin. I learned how to add a new user, and change the password manually. I learned about MD5 hash. I also fooled around with the wp-config file. I even tried an emergency wordpress password reset script. Nothing worked, and no one could give me any answers on the Wordpress forums.
Finally, I resigned myself to the fact that I would have to export my database, delete all the files from PixelRN, reinstall wordpress, and import the parts of the database that I was pretty sure were okay.
Not looking forward to any of this, I procrastinated.
While I was procrastinating, Matt Cutts, the head of Google’s webspam team, was alerted to the problems I was having and wrote a blog post about it. While it thrilled me to no end that someone from Google was actually paying attention, I was still S.O.L. as far as getting onto my wordpress admin page. Maybe it would have been better if someone had alerted the other Matt, Matt Mullenweg (the creator of wordress.) As it turned out, I was supposed to attend WordCamp NYC on Sunday, where Matt was speaking. I opted to instead stay home. I was way too down on Wordpress to attend, and besides, I needed to actually spend time fixing the problem.
So that’s how I spent my Sunday afternoon: fixing PixelRN.com. As you can see, it worked, because here I am blogging again!
Tomorrow: I’ll blog about what I learned from this experience. I’m hoping I can save others from having the same experience.