-
Website
http://www.louisgray.com/live/ -
Original page
http://blog.louisgray.com/2009/06/google-gets-serious-about-blog-search.html -
Subscribe
All Comments -
Community
-
Top Commenters
-
charlieanzman
60 comments · 11 points
-
Jesse Stay
221 comments · 70 points
-
Ari Herzog
43 comments · 21 points
-
ChangeForge | Ken Stewart
133 comments · 18 points
-
drewolanoff
64 comments · 53 points
-
-
Popular Threads
-
FTC Disclosures Made Simple For Bloggers With Conflicts
6 days ago · 46 comments
-
Still Waiting for An Evil Google? It's Not Going to Happen.
6 days ago · 30 comments
-
Fighting Bots With Bots on Twitter, Leveraging SocialToo
1 day ago · 5 comments
-
Simler Adds Likes, Favorite Tags, Revamps Homepage
1 day ago · 4 comments
-
Gowalla Raises $8.4 Million for Location Check-in Service
1 day ago · 2 comments
-
FTC Disclosures Made Simple For Bloggers With Conflicts
Unfortunately, the comments you leave with your blogger profile aren't credited to louisgray.com but http://www.blogger.com/profile/0067564266533941... (good luck remembering to search for that) so that part is a bit of a bugaboo.
Still, I really like the display-in-div that the blogger team is doing. I think that was a bold move for them to integrate results inline, and that should be rewarded. And FWIW, blogger seems faster to me in the admin tasks than wordpress.com or hosted wordpress. But most of all, I'm glad to see that the blogger team is developing their app further.
And Lijit has to take credit for leading the right direction, too. It must be flattering to be followed. I'm eager to see their next version and where they take it. Bottom line is that when tools are improved, bloggers win!
I meant to say, yes, you did actually link to twitter.com/louisgray/status/ but that the gadget doesn't seem to be picking up text in the URLs.
Check it out:
This post, http://tins.rklau.com/2009/03/eight-lessons-lea...
has a 4 separate links to pages with louisgray in the URL
- http://twitter.com/louisgray/statuses/1330196523
- http://twitter.com/louisgray/statuses/1325740834
- http://twitter.com/louisgray/statuses/1330196523
- http://twitter.com/louisgray/statuses/1344547411
I would have thought the search gadget find those examples of "louisgray", but it only seems to find text when it's part of the domain (i.e. when you link to louisgray.com).
No biggie. I still like the display-in-div part very much :)
Thanks for the specifics - I'll check back with the search team and report back.
We are excited to see that other companies are understanding that bloggers are demanding more than just default search.
That bloggers live in a world that is populated by more than their blogs.
That bloggers are generating content beyond their blogs and are developing expertise and trust in a way (and speed) that is unprecedented.
Innovation begets innovation, and as we continue to lead the market in trusted blog search, I fully expect other companies (both new and old) to enter the space attempting to build on our success.
I think to some degree, you missed the point. People are now demanding more than a search box that returns keyword/pagerank based site-specific results. People want to know more about the bloggers they are searching; and bloggers want to showcase more of their expertise and content, which spread across the web.
Same goes for "real time" search. Google is late to the game with "real time" search. Will they develop a product that is as dominate as their standard search? Who knows.
Blog search is heating up because it has become more important to return a trusted result from a trusted source, than the single answer that one search engine's algorithm believes is the correct answer.
Every blogger is an expert about something, and when I do my searching, I would like to allow that blogger's expertise to apply the context to the search. That way the algorithm knows if I am search for seal (the animal), or seal (the singer), or seal (of Colorado)...
What you see from Google is their first step in that direction, and frankly that excites us at Lijit.
Sheesh, as I write this, I guess the answer is: YES there are use cases for using both, and YES, there are use cases for using one.
But isnt choice grand?