Archive for the 'SMM' Category

Grey Bar to PR6 in Under 60 Days

Wednesday, April 30th, 2008

We pushed the “” piece on wintrest.com on March 10. It went ridonculous viral. The April 29th PR update shows this page at a PR6. Wintrest.com itself is under 6 months old, and the index now shows a PR4.

Good SMM pushes is powerful stuff, meng!

SMM Comparison – Reddit, Mixx, & Propeller

Saturday, March 22nd, 2008

When I’m chumming for links w/ SMM, I typically like to say “shoot for digg, settle for stumble, pick up the scraps w/ mixx.” Well…I’m spending a LOT of time this week working on my propeller account. I’ve never picked up any significant traffic from mixx, but I still think it’s solid tool to use to cross promote.

So…I’ve been trying to figure out other sites to use to promote material. emailed me yesterday to let me know that a particular piece would do well on reddit & propeller. From my experience, reddit can definitely drive traffic -a couple of pieces got 30k+ visitors when they went hot naturally.

However, I don’t like reddit. IMO, the branding is too poor to ever gain a wide audience, and it lacks the tools necessary to promote a piece – namely, sharing with friends. So, reddit traffic = good. Reddit functionality = bad.

I do like propeller, but I haven’t promoted there much. The audience seems to be more mature than digg, and there are proper categories for a lot of pieces that I wouldn’t be able to submit on digg. The functionality is good – you can add friends & shout to them. Unfortunately, it doesn’t look like you can “select all” so shouting will become a chore with a massive friends list (edit – you can shout to 5 friends at a time…huge pain in the ass – will probably code a solution.) Also, I couldn’t find a way to integrate the vote count with your site (someone please correct me if I’m wrong.) But it looks like the biggest plus will be the traffic. I checked out the alexa results for reddit, mixx, & propeller, and it looks like prop comes in a close second to reddit (which I know can drive 30k+ visitors.)

So…I’m signing off to start working on my prop account. I’ll push a couple of stories, and report back w/ some traffic counts!

Ajaxonomy Bury Recorder is a Great Idea in Theory

Thursday, March 20th, 2008

We’ve been running a ton of digg campaigns, and using the on all of them. In theory, it’s great. Using the feed, it watches for buries, and tells you how many buries a particular post has. Great in theory. We’ve been using it to watch different submissions and were shocked to find that many of our submissions were yanked from upcoming w/ zero buries according to ajaxonomy.

So…Ken Smith & I have been pretty pissed about the whole “” deal. Then Ken decided we needed to run a test on the credibility of ajaxonomy. Bottom line – it doesn’t work.

We picked 5 random stories that had gone hot (not popular) so that we knew they had some exposure. We put them all on the bury recorder, and then we both buried them for specific reasons (spam, duplicate, general.) Between the 2 of us, we had 10 total buries to watch for. One was recorded by ajaxonomy – one. So, according to this test, ajaxonomy is sitting at ~10% accuracy.

Super Cache + Strong Hosting = Digg Proof

Monday, February 4th, 2008

I crashed another server on my digg. Needless to say, I was pretty pissed at Inmotion. The sales team was very knowledgeable about the digg effect, and they assured me that my new plan would be able to handle it with no problem – no matter if I had a WP blog querying DB’s or not. And….it crashed.

To their credit, Inmotion’s support team was awesome. I had been meaning to install for a while, but didn’t think to do it before the last campaign. They shut down the server, installed super cache on the blog, and fired it back up. By this time, the post had made it down towards the bottom of the page, so I wasn’t actually sure if it was the plug-in, or the decreased traffic.

But then, yesterday I pushed another piece. I did it kind of spur of the moment, and put it on a blog that I put up specifically for diggbait. It’s at 1000+ diggs right now, and the server stayed strong throughout the whole ordeal. So…I think we finally have the final piece to the digg proof puzzle –

Puurple.com Launches – Social Bookmarking for the Real Estate Industry

Friday, February 1st, 2008

Check it out!  We just skinned and launched .  This site is intended to be a real estate industry niche social bookmarking site.

Do the diggers hate your stuff?  Don’t feel bad – They hate everything!  Come on over, where it feels so gooooood.  If you have real estate related content, this is your place.

Reputation Management Case Study: Baptism by Fire

Wednesday, January 30th, 2008

Pubcon 2007 was my first SEO convention, and I absolutely loved it. I went looking for new link building ideas, and was floored by one – social media marketing. I listened to Cameron Olthius, Neil Patel, Michael Gray, & Rand talk about methodology & case studies, and I soaked it up.

I’m not an SEO by trade – I’m a real estate broker who SEO’s his own sites (and works on side projects.) I knew going into SMM, that selling anything real estate related to the digg crowd would be difficult. But…..

I got the digg rush, and then the typical digg overdose. My server crashed, the digg guys talked smack about it, I stayed on the phone w/ my host for 2 hours, and then I went back live. I climbed to 1000+ digs, it was picked up & went popular on Reddit, and the Stumblers found & loved it. Over the next week the backlinks just kept rolling in.

Then…I was forwarded this: (click on images for full communication)

And…..my baptism by fire into the world of reputation management was rolling.

I was floored. I knew of Mert Sahinoglu, but had never really had any direct contact with him – he’d commented on my blog a couple of times, but that was it. I immediately called him to see if he’d actually sent the contact form. He answered the phone, I introduced myself, and he immediately hung up.

I shot him an email asking, “what’s up?” He responded by firing a mass email, blind copying the recipients.

The same day, I received two emails from other agents featured in the original digg post. They were pissed. They had not seen the digg post until Mert contacted them and informed them of the post. His email not only told them of the post, but advised them to sue.

And then….more attacks:

Reputation Management by Fire

Step #1 Assess & prioritize the damages

  1. Threats of Litigation
  2. Damage to reputation through email & forum attacks
  3. Potential damage through search rankings

Step #2 React to Each Attack

  1. The only winners in any lawsuit are the attorneys, so I immediately pulled the piece and apologized to the angry agents. No attorneys contacted me.
  2. I immediately sent a mass email to agents I speculated would be on Mert’s original mailing list, in order to explain what had occurred, and to clarify that I had done nothing to provoke the attack. I received many supportive emails & phone calls as a result.
  3. I then posted , and 301 redirected the original piece to the new blog, in the hopes that I would not lose any garnered backlinks. At last count, the original post has 1700+ links.
  4. I emailed friends & colleagues & asked that they comment on my response, in order to guide the conversation. This got the ball rolling in a positive direction, and there were 19 supportive comments at last count.

Important Points to Note

  1. I’ve always been active on many social networking sites, and I have more than a few blogs w/ decent PR. Because of this, Mert’s blog wasn’t able to climb any higher than the bottom of page 2 for my name.

  2. Silence speaks volumes. Mert’s forum & blog posts . Because of the lack of response, there was no need to lend it any credibility through a response.

  3. Unless you’re wrong, stick to your guns. My blog explanation clarified my position, but did not apologize.

  4. .

  5. 700+ diggs & another crashed server.


Promoting a Digg Piece? Mixx It Up, Meng

Monday, January 28th, 2008

Everyone’s up in arms over the new digg. The digg guys have tweaked the algo, and now it’s a different process to promote a piece to go popular. I say different, because in my opinion, it’s not harder or easier. that rings true.

Basically, the algo seems to track voting patterns, and devalues votes from the same group(s) of voters. So…if you have a small, but very consistent digg SOI, you’re going to have problems. Where as in the past, 50 voters that would always vote when you asked was a pretty good resource to get you dugg, now you need to have more sources, and they don’t need to be as consistent.

In the past, many diggers would keep a tight circle of ~100 mutual friends to shout to. Now, they need a bigger SOI to vary the vote sources, and go popular.

So…one technique is to mixx it up, meng! Mixx has turned into somewhat of a refuge for spited diggers. Social bookmarkers that are pissed b/c they’re having problems promoting on digg are turning to mixx, and other sites like it in order to get their fix.

I’ve briefly promoted on Mixx, and it doesn’t drive much traffic. However, it’s a good resource. Mixx allows you to easily directly email your followers – not simply a “shout” but a real, direct email to their inbox. Because the mixxers are pissed at digg, they’re receptive when you ask them to digg a story. Give it a “hey, let’s get this pushed popular on digg” spinn…fight the power – and the power, in this case, is digg.

The Digg Effect

Saturday, December 29th, 2007

Well…I talked to Godaddy a # of times about my (then) & was reassured twice that my shared hosting account would be able to handle the traffic. I specifically asked them, both times, if they were familiar with “the digg effect” and to please go google it. They said they weren’t familiar, but they had no doubts they could handle the traffic. If this is what they mean by “handle the traffic,” then I guess they were right.

After the server crashed, I immediately called them back & asked them to transfer me to the manager. Apparently, my hosting plan can only handle 150 inquiries/second, and we had 1.1m in 2 hours. Unless we had <1 second latency, this wasn’t going to cut it. The manager then transferred me to his manager, who then got on the phone with the server tech, who manually changed the permissions to allow the necessary amount of inquiries. With 2 hours of downtime, I logged 50k visitors that day. I’m not sure how many I missed out on.