5 Ways to Increase Your Blog Traffic: Chris Brogan vs. The Watchmen

As I've mentioned before, I notice whenever Lijit reports a spike in my blog traffic. Normally, that spike is caused by someone with a wide online reach (like Chris Brogan) mentioning something I've written, which then drives that person's audience to me (for that day, at least).

But this week I learned a huge lesson: Chris Brogan is no Rorschach.

When Chris (and the rest of the standard social media Twitterverse) mentions something I've written, I may see a peak of 700 views on that particular post.

When I wrote my review of the Watchmen film last week ("10 Things People Don't Seem to Get About the Watchmen"), I had no idea what would happen next:



Somehow, that Watchmen review really touched an online nerve.

Admittedly, Chris Brogan's original retweet of my post (which referred to it as the "best Watchmen review. Ever.") had something to do with it first finding an audience. But that 17,000+ traffic spike is 25 times the normal "Brogan Effect" on one of my posts. This means my Watchmen post reached some kind of escape velocity and broke out of our social media fishbowl (where most of my and Chris's audience tends to live), and crossed over to an equally-passionate (and, presumably, much larger) niche: traditional comic book fans. (It also had legs: look at the numbers 5 days later, vs. the 8 readers from the previous Sunday.)

My attempts to figure out exactly where all this additional traffic came from have been patchy at best, but I suspect Reddit had something to do with it. It also appears to have been retweeted at least 50 times (with another 15 thanks to Copyblogger), and then it may have continued on being retweeted under other names / descriptions.

All of which leads me to...

5 Thoughts on Increasing Your Blog Traffic

1. Write Something That Appeals to the Hubs. I could write amazing blog posts all day, but if none of them were interesting to the folks that OTHER people listen to (like Chris Brogan or Copyblogger), no one would ever see them. I could spend months building an audience that's comparable in size to Brogan's, but that's also time I could spend making interesting media, which is what provides the hubs with interesting things to talk about. (It's a cycle, people; find your spoke.)

2. The Title Is the Hook. If someone likes what you wrote, they'll want to tell other people. In this age of Twitter, they need to be able to explain WHY your article is interesting in about 100 characters (not counting the characters they'll use for the link, plus any "retweet" attributions, etc.). What better shorthand than an interesting (or provocative) post title that does their work for them?

3. The Summary May Also Be the Hook. Sometimes a title doesn't sum it all up. In that case, provide a one-sentence summary of your article or a series of mini-theses within the post itself that readers can cut-and-paste as their "aha" quote to explain the post's relevance. (Things move quickly on the web; making the promotion of your work as easy as possible is imperative to getting it seen.)

4. Don't Confuse Your Traffic with Your Niche. I make a living doing social media, so that's where the bulk of my audience comes from. As a result, the majority of my blog posts are aimed squarely at the audience I expect to be serving. But that's also a closed loop; if all I ever wrote about was blogging, social networking and Twitter, I'd never attract an audience with other interests, and my total possible audience would have a limited cap.

On the other hand, I doubt most of the 17,000+ readers who saw my Watchmen post are interested in social media, which means 95% of them probably have no reason to return to my blog; they were simply passing visitors who were here for one specific post. (In fact, my subscribers have actually gone down since the Watchmen piece ran.) So as great as it is to see a massive bump in numbers, don't kid yourself into believing that the people who find you are necessarily interested in everything you have to say. (And don't get depressed when your subsequent posts fail to reach those eye-popping numbers.)

5. Pay Attention to What's Working (and What Isn't). Personally, I think every blog post I write is great. But not every post resonates with my audience. Some of my best articles (in my opinion) languish with nary a comment, while others (that I wouldn't necessarily expect to catch on) somehow find a life of their own.

Studying the habits of my readers helps me understand what topics most often generate comments AND which posts (or titles, or summaries) most often get redistributed. It also helps me understand when I might be wasting my time. For example, I have a tendency to share my convoluted theories on why and how certain aspects of social media work, but my audience doesn't seem to care. So no matter how interested *I* may be in my ideas, it's evident that my audience isn't (yet), which means I'm much better served by writing articles they ARE interested in (based upon past indicators), with the presumption that my aggregate audience will eventually grow to include new readers who WILL care about what the old readers didn't.

Oh, and a bonus tip:

Don't Feel Compelled to Write Something Every Day. Some people believe that daily content is the only way to maintain an audience. Wrong. People aren't reading you because you're around, they're reading you because you're good. Sure, it's great to be both, but when forced to decide, most thinking mammals prefer to read quality over quantity. And the better you are, the more your audience will forgive your infrequency between bolts of spine-tingling relevance.

The Comments Ate My Baby

Some blog posts elicit more comments than others, and when the occasional "hot button" post (or anything on Scobleizer) attracts massive amounts of comments, it gets me thinking...

How many comments is TOO many?

As a Blog Writer...

... I would say "there's no such thing as too many comments," because the more people take the time to respond to something I've made, the more I know I've connected with my audience. (Minus all those people who post comments that add zero value to the conversation and simply act as a free ad for their own URL).

I also enjoy hearing people's differing opinions, or seeing them make additional suggestions that are relevant to the topic at hand. One author can't nail a topic from every angle, so it's great when interested commenters can add depth and breadth to the conversation.

As a Blog Reader...

... I rarely read beyond the first 10 comments on a given post, because so much of it is either empty congratulations or a stock battalion of "yes, but" arguments.

That said, when a topic DOES spur a healthy (or heated) debate, I'll read much further down the comment stream, usually until the sentiments begin rapidly duplicating themselves.

And, as a Commenter...

... I'm more likely to leave a comment on a post if I'm either among the first responders to that post (and, thus, more likely to have my comment read by others) *OR* if I have something to add that I believe is both valid and as-yet unsaid by anyone who's commented before me.

In my opinion, there's no sense in adding yet another voice to a string of comments unless that voice extends the conversation beyond its existing borders. Which is ironic, because as a blog author, I don't mind redundancy in the comment stream; when I'm in that role, every comment carries with it the added value of validation.

So, how do YOU handle (or leave) comments?

Image by lammy.

10 Ways to Be a Social Media Asshole

You may have heard that social media is "all about the conversation." That may be true in some cases, but not all. In fact, for some people, social media is simply about finding new and interesting ways to be an asshole - it's Machiavelli's "The Prince," as applied to text boxes.

If you're finding it difficult to irritate people on a regular basis, here are ten tips you can follow to aggravate even more people - many of them strangers!

1. Insult people loudly and publicly. Bonus points if you don't know the person, but you do know enough to know that he / she / they must be horribly, horribly wrong. This will endear you to everyone else who shares your opinion, and will make you seem like a man / woman / composite persona that's not to be fucked with.

2. Leave scathing comments in public places. Nothing says "I've seriously considered your work / opinion and respectfully disagree" like personal attacks injected into one's thoughtstream.

3. Always be anonymous. Never say with public faces what's best typed hidden in private places.

4. Always ignore grammar / spelling / punctuation. Clear and legible disagreements are best left in the classroom. As a person with unbridled truth to share, you're free of the rules of class.

5. Steal other people's work. Creative Commons licenses never hold up in court, because Americans know that anything available to the public is fair game. If they didn't want you to take credit for their work, they wouldn't have made it public in the first place.

6. Talk endlessly about yourself. In a world of nearly 7 billion people, nothing is as interesting as you. Always find a way to turn topical conversations into conversations about you - especially when you don't know what people are talking about in the first place. (One great way to do this is to lead off with "Speaking of ___," and then immediately change the subject to that head cold you're not quite over.)

7. Namedrop like it's your job. Because it is. That's because people may not remember you, especially if what you're doing is redundant or unremarkable -- like, say, being a "social media expert" or "communications guru"-- but they'll damn sure remember who you had lunch with last week. (And by "had lunch," it's okay if you forget to add, "in the vicinity of," or "at the same conference as." Because even if you *didn't* technically "have lunch" with Seth Godin, he undoubtedly follows you on Twitter, so he might as well have been at your table when the server girl spilled all that water on Andrew Baron [at the next table].)

8. Pontificate loudly about why all new ideas will fail (or PHALE). And then, if they don't, take credit for their success by insisting that the creators of said idea must have taken your warnings seriously and changed their business plan.

9. Blame designers for your inability to understand their services. Because if it doesn't work exactly like Google, Flickr, MySpace or anything else you already know, it's new, and new design is bad and likely to fail (see above).

10. Make all private emails and messages public. Because if so-and-so had really meant it when they direct messaged you in confidence, or asked you to sign that non-disclosure agreement, they wouldn't have used the internet for such sensitive communications. As mentioned previously, if it's on the web -- even behind someone else's password-protected intranet firewall -- it's fair game. (The people have a right to know.)

Do you have a favorite approach that I've overlooked?

Fragmented Conversations

When someone blogs about someone ELSE'S blog post, where should YOU leave a comment?

For example, yesterday I blogged about Lan Bui's troubles with Podtech. As a result, some folks left comments on my blog, which I dig... but unless Lan himself stopped by, he'd never have seen them.

Conversely, had everyone only commented on his post, I'd have been under the impression that my two cents hadn't furthered the conversation.

Proposed Solution

What the blog world needs is a conversation tracker.

This way, after Lan made his initial blog post (for example), anyone else who'd blogged about the issue would have their post automatically included in that conversation stream. Then Lan (or whomever originates a blog post) would be able to see all other posts made regarding the original post / topic.

Plus, everyone else further down the conversation chain could see up and down the trail in both directions, AS WELL AS seeing any nodes that grow off their OWN posts about the subject.

In addition, any comments made on subsequent branches of the topic could also be cross-posted back to the preceding blog posts -- for example, Roxanne's comment on my post could also be CC'ed back to Lan's post, if so desired.

So, in the end, the structure looks more like a tree than a river.

Programmers of the world, you have been prompted.