2 min read

Technorati, boooooo [Part 3]

Paul Kinlan

Paul Kinlan

Lead of Chrome DevRel

After a comment from Zoli Erdos on my blog entry about Technorati, I don't completly agree with the article, but then again the only problem I have seen is that my posts don't get indexed correctly [although, each time that I mention they don't about a day later they appear in the listing]

I do however agree with the following statement:

Now, let’s talk about communication: emailing techorati support is acomplete dead end. Bloggers quickly learned the trick: emailing Dave Sifry(CEO), or perhaps Kevin Marks, or tagging blog entries with their names used toresult in a response, and sometimes even corrective action. That’s nolonger the case. I understand. The CEO personally emailing back isnot exactly scalable communication. But why doesn’t Technorati have asearchable Knowledge Base, or at least a FAQ of known issues andsolutions? This is really Customer Service 101.

We need a FAQ, we need a knowledge base, we need better community support from your support. You can't continue with the "support service" as is, because, it doesn't support any service. [ps I don't think a Wiki is the answer either, the developer Wiki is rather rubbish, the pages should just be static support pages]

I really don't know if we should be complaining about this, after all Technorati is still a free service, it has a free access API and it has provided me with a lot of hits on my blog.

Stay in the loop.

I'm trialing a newsletter. Join for monthly insights into web dev, Chrome, and the open web.

alternate_email

Get in touch

Open to chat about Chrome or Web development.

Book a consultation