(Reading time: 4 – 7 minutes)

Got lemons? Make lemonade. Such a hideous old cliche, all the worse for it’s truth. Having your website squeezed will leave a sour taste, but the resulting traffic data turns out to be sweet.

Now that there’s a year’s worth of data for Website In A Weekend, let’s use the stupid service attack as an excuse to take a few notes. No fancy writing today. Just the facts, with four graphs showing traffic.

Daily stats for February 2010

WordPress daily stats for February 2010

Examining the graph above:

• The red bar shows a local plateau in traffic, which is good, exactly what I was aiming at (10k hits/month).
• February 11, 2010 disaster strikes early Thursday morning. Hosting company informs of distributed denial of service “This one is as bad as we’ve ever seen.”
• Traffic stays cratered for a few days. Literally, cratered. Kind of cool when when think about it. I continue to post, but comments are turned off.
• When the server was offline completely on Feb 18, I gave it up. No articles for 3 days in a row. That’s the longest posting break since May 2009.
• Traffic starts to return to normal on February 21 when I run Julie Angelos article on being successful.

Weekly stats for last 6 months

WordPress Weekly traffic numbers week ending February 27, 2010

The weeklies show a similar story.

• There’s a definite crater through the holiday season. Note that my Alexa ranking, which is a relative index, remained steady or declined (good) during the holiday season. While total traffic was decreasing, I was gaining traffic share. Nice!
• Since the attack started half way through the week, the first week of the attack doesn’t show much decrease. The second week is pretty awful. The screenshot was taken 5 days into the 3rd week since the attack began, so there is still room for growth on that number. The rate of traffic loss clearly declined in any case.
• The traffic plateau shown for the first four weeks (i.e., January) was my target: about 10k hits/month, then twiddle the knobs to balance ROI for time invested.

Monthly stats for first year of Website In A Weekend

WordPress Weekly traffic numbers week ending February 27, 2010

The monthly is where it’s getting really interesting. I’m giving you the whole year too, no secrets here.

• April is an outlier, one day of bogus traffic from StumbleUpon. Take that one day away, you would see smooth growth all the way to September.
• Starting in September (after Burning Man), I started commenting on other blogs more often. You can see the result in my traffic.
• No surprise that December is cratered. Take the Christmas Crater out, growth would have been pretty smooth.
• And here’s where it’s really interesting: despite being throttled and without even commenting for 9 days, February 2010 is already my second best month, and that’s with 2+ days left in the month when the screenshot was taken. As of February 27, 17:54 Pacific time, the February count is 8433, and it should hit about 8700 by midnight February 28, 2010.

Relative ranking from Alexa

Let’s see what Alexa has to say. Here’s the trailing month:

Alexa trailing 1 month traffic rank

• A one week decline from mid-35k to around 100k, then bouncing around at 100k. Ouch.
• On the other hand, I do nothing and I still rank right around 100k on Alexa. That’s pretty close to money for the right readership. This is good to know.
• Getting traffic back the second time turns out to be much easier. It took months to get from 100k to 40k. I’ll do that again in a week to 10 days.

Note: Alexa is very useful for relative ranking. It doesn’t correlate well with raw traffic, but that’s ok. The relative traffic is still useful.

Supposed you’re attacked, what then?

First: don’t sweat it. Seriously. If you’re running a solid operation, it’s not a big deal.

Here’s a few suggestions:

• Do something else. Literally. Step away from the computer. Go outside. Find something else to do.
• Write small articles which will load quickly. Tell your readers what’s going on, but don’t get all weepy about it. I have no way of knowing for sure, but I suspect had the server not gone down completely on February 18, the whole 9 days would just look like a more or less ordinary “slow traffic week.”
• Have a plan you can execute very rapidly to keep your readership engaged. I have a couple of ideas I’m toying with. If it happens again, perhaps I’ll implement those.
• Don’t sweat it. These things happen to everyone. Even Google gets hacked.

What about you?

Do you have a plan in case of attack?

What about other internet emergencies, are you prepared?

Let’s talk it over!