Eventually I’m going to talk more in-depth about gawk.it competition, but tonight I just wanted to dump some quick tidbits I’ve been discovering as I explore this general space a bit more.
I’ve been intentionally adding new blogs and forums to the gawk.it search system VERY slowly (I’ll try to explain the reasons behind my ‘slow to add’ approach in a future post)…anyway, to date I’ve only added about 35 different blogs (and their related comments) to the system.
The way I’m adding blogs at the moment is either by request (ie. someone creates a gawk.it account and uses the tool there to request that their blog is added to gawk.it) or by going out on my own and identifying a blog that I would like to be able to search myself (I add it, then I inform the blog owner, and if I’m lucky they like it and decide to have it power their search feature).
So anyway of the 35 in the system already, 6 have actually gone through the process of having the current version of gawk.it actually power their search (a handful of others have actually verbally agreed to let gawk.it power their search, but haven’t actually plugged it into their blog templates yet – I gotta get more aggressive/pestering about that I guess).
Forgetting for a moment that at least a handful will (likely) switch over to gawk.it before long, here’s how the 29 that are not powered by gawk.it yet are currently offering up search to their users:
So I know it’s an insanely small sample, but I still find this very interesting and exciting as it relates to the gawk.it opportunity.
First, the fact that almost 40% offer up no search feature at all is just baffling to me.
I wonder if it’s because they just didn’t like the search options/quality available, if it was just too hard to figure out how to include, or it there is some other reason for not offering up search?
In any case, I believe site search has shown to have many great benifits and adding the ability to search the entire conversation via gawk.it (along with the analytics stuff we already offer) is hopefully a no-brainer decision for most of these blogs to want to install gawk.it.
Second, the 24% that left the default tumblr search on are also baffling to me, but I love them because this is a case where I can simply have them do searches on gawk.it vs. searches on their tumblelog
Since Tumblr only searches against the tags they’ve tagged their posts with (and most people don’t do good tagging) I’m confident that 99% of the time gawk.it results in this comparison completely 'wow’ them.
Again, I hope that translates into a pretty easy decision for the blog owner.
So already, that’s over 60% that *should* be fairly easy conversions to using gawk.it
(assuming I can get the blog owners to notice gawk.it, want to have a quality search option for their readers, and make it EASY for them to get it running – BIG assumptions I know).
The remaining groups are a bit more interesting situations to try and work gawk.it into.
On first glance, the results they offer aren’t that different to what the blog search only feature of gawk.it offers up (they actually are slightly different, but probably not enough so to 'wow’ people with a comparison search like in the Tumblr situations).
So they require talking a bit more about the unique value that gawk.it brings to the table (ie. the concept of your whole conversation search vs. just website content search).
I still think I have a VERY compelling case to make against each of these (and this is part of what I mentioned I will try to lay out later in a post or two about gawk.it competition)…but it’s definitely a harder 'sale’ than the first two groups.
Luckily the 1st two groups are appearing to be a massive amount of the initial market, and I’m pretty excited to be getting gawk.it into position to start helping them provide quality search to their readers!
This post has received 36 loves.
Kevin has a day job as CTO of Veritonic and is spending nights & weekends hacking on Share Game Tape. You can also check out some of his open source code on GitHub or connect with him on Twitter @falicon or via email at kevin at falicon.com.
If you have comments, thoughts, or want to respond to something you see here I would encourage you to respond via a post on your own blog (and then let me know about the link via one of the routes mentioned above).