It might not be good, but developers are saying something about your product.

Unlike for restaurants, you can’t always read what reviewers think.

The stuff diners say on Yelp is more important to my decision to eat there than the overall star rating.

Say it’s a Friday evening, and I’m searching for a new teriyaki place…

I open Yelp, but I don’t simply sort by stars. I might look at:

• Proximity to me
• Pics of the seating
• Praise in five-star reviews
• Complaints in others

For example, sometimes a three-star review mentions something that wouldn’t bother me at all, like charging extra for sauce.

You probably have a similar list in your mind when you’re making dinner plans.

But how about content plans?

It’s not just volume of posts or even traffic that I think are interesting…

Here’s how I’d look at your dev blog:

• Recent publication dates and gaps
• Topic choices and consistent stories
• Relevance of the pages that rank well
• Credibility of the people behind the content
• Does it seem like you understand your audience?

Depending how much time I have, that list may go on. And each of these is its own little well that can go deep.

Want to learn more about ​how we can evaluate your technical content​? Reach out. Don’t worry, I won’t post about you on Yelp.