SMX Day 2 – Social Media Madness Part 1

Arrived bright and early today to catch the tailend of the intro SMX Advance panel. The panel gave a primer on many aspects of search engine marketing including optimization and social media. The panelists shared the opinion that social media is a major focus for businesses large and small, which made my ears perk.

Early turnout was quite high with many people arriving well before the booths and conferences started. The bell’s about to ring for first period: Real-time Search.

Real Time Search: Opportunity Or Hype

Moderator: Danny Sullivan, Editor-in-Chief, Search Engine Land

Gerry Campbell, CEO, Collecta
Jeremy Hylton, Software Engineer, Google Inc.
Ken Moss, CEO & Cofounder, CrowdEye
Kimbal Musk, CEO, OneRiot
Vipul Ved Prakash, Cofounded, Topsy

Admittedly I don’t know a lot about Real-time search but as it’s very much in the early conceptual stages, I’m interested to know how the panel plan to populate this presentation with data. The panel consists of Gerry Campbell, Jeremy Hylton, Ken Moss, Kimbal Musk and Vipul Ved Prakash.

Danny starts the conference descibing what real-time content is. Twitter, Facebook, flikr etc. are all tools that make real-time search and real-time data creation possible. Limitations of present real-time search is that the way your search results are displayed chronologically. Other limitations are that search results are actually displaying what’s being willfully shared and don’t include nearly as much content as it should. He mentions that while all tweets are public and made searchable they are still

Kimbul starts his reply by respectfully disagreeing with Danny about the quality of real-time search results. He shows how can provide meaningful real-time search results by aggrigating and filtering tweets and other returns. He warns that real-time search results are coming to the forefront and will have a big effect on SEO.

Jeremy, again, respectfully disagrees with Danny’s assesment of the state of real-time search. Jeremy questions the usefulness of making tweets searchable as they often link to other content. Jeremy argues that real-time search isn’t necessarily limited to content created within the last few seconds, but also delivering up the most recent content despite not always being strictly “real-time”.

Ken Moss takes the podium to give his take on real-time search. He stresses that consumers and businesses are keeping their finger on the pulse of information. He references the Iranian election situation where the US government told Twitter to delay their scheduled maintenance because Twitter had become an important information tool for the most up-to-date perspective. Ken goes on about his CrowdEye search which ranks tweets and twitters based on an influence score they’d created. The search also outlines the popularity of search term.

Gerry Campbell recounts a story of seeing videos and reading content about the Iran elections well before major news outlets and that the web is becoming the main source of information for people. Gerry believes real-time search is very much overhyped because as a concept, people haven’t yet agreed how important it is and how users are able to effectively use it. Gerry has broken down search queries in order to identify which areas of interest developers and entrepreneurs should focus their efforts. He believes there are certain categories benefit more and create more opportunity for real-time search than others.

Vipul Ved talks about the challanges of real-time search. As time goes on the more and more content is being created in a given minute. Much like CrowdEye, Vipul’s Topsy attributes a popularity rating to results based on participation and links.

The issue of ranking real-time content in traditional search becomes a point of discussion. Jeremy talks about the challanges at Google to be able to effectively display the most recent information about topics and issues.

By the sounds of it, real-time search will have a direct effect on the social media world.

Leave a Reply

Your email address will not be published. Required fields are marked *