Forget Indexing Tweets: Google Is Pulling Them Directly from the API

When Google rolled out with Caffeine last year, the idea was to speed up the way that the search engine was able to index pages, particularly for use in real-time social media searches. Apparently, that wasn’t fast enough, so they’re going straight to the source.

Tim Cohn first noticed that Google was displaying the last Tweet from particular accounts in their search results. Search Engine Land then tested it and found that Google was popping up the last Tweet almost instantaneously and that the last Tweet would disappear after a certain period of time if the account wasn’t updated.

We just ran a test of our own (above). I tweeted, then immediately refreshed the Google search result as quickly as I could. As you can see, it registered the Tweet immediately, showing “2 seconds ago.” No standard indexing technology could work that quickly. Google has tied their search results directly into the Twitter API (something they’ve done for a while with their “Realtime” search feature).

Most tweets are eventually indexed – some within minutes, some within hours or even days. These Tweets are being presented in their raw form prior to being indexed. The Tweets themselves are not being used in search results through this new method. They will be indexed separately and can then appear in searches as their own listings, but this is different. Just as with Google’s “Realtime” search, this feature is a firehose.

When Tweets (or any other pages) are “indexed,” they have been read, understood, and classified based upon their content, the history of the domain, and links coming into the page (among other factors). Once they’re indexed, they can appear in search results as stand-alone listings. This is a direct feed regardless of content filtered by removing any that start with an @reply.

Groundbreaking? No.

What does this mean? Not much. It’s a cool feature, but it’s just an addition to what they’ve already been saying for a couple of years (and proclaiming more openly in December) about how social signals are playing a roll in their algorithm.

The other minor (but cool) change is that links within Tweets are maintained, including hashtags. Since @replies are not being included, apparently Google is looking for the latest news and statements on Twitter but they’re not interested in conversations between users.

About JD Rucker

+JD Rucker is Editor at Soshable, a Social Media Marketing Blog. He is a Christian, a husband, a father, and Director of Digital Marketing for KPA. He drinks a lot of coffee, usually in the form of a 5-shot espresso over ice. Find him on Twitter, Facebook, and Pinterest.

Comments

  1. great find.

  2. I think they should segregate this kind of feature and put it in similar categories to google images and google blog search. It’s kinda cool if google put an api to social media sites that’s accept content to be aggregated and let google pull the search results to a different page.

  3. Very interesting. I use Google almost exclusively and this is good info to know.

  4. great. more useless content we don’t need on the internets.

  5. I noticed that a while ago. Whats better is that some of my profile pages from Twitter appear on the first site of Google. I suppose that’s because I have around 10000 followers on some accounts.

  6. Its really useful, i am interested.

  7. I am a google worm, and this particular feature of google is really great. It will very useful for all google users if they put an API to social media sites.

Trackbacks

  1. [...] pm in Uncategorized by LiveWord? Forget Indexing Tweets: Google Is Pulling Them Directly from the API Source: soshable.com When Google rolled out with Caffeine last year, the idea was to speed up [...]

  2. [...] media searches. Apparently, that wasnt fast enough, so theyre going straight to the source.Source:http://soshable.com/forget-indexing-tweets-google-is-pulling-them-directly-from-the-api/ Posted by Makin at [...]

  3. [...] media searches. Apparently, that wasnt fast enough, so theyre going straight to the source.Source:http://soshable.com/forget-indexing-tweets-google-is-pulling-them-directly-from-the-api/ var stLink = jQuery('a:last')[0]; stLink.href = 'javascript:void(0)'; SHARETHIS_post = [...]

  4. [...] media searches. Apparently, that wasnt fast enough, so theyre going straight to the source.Source:http://soshable.com/forget-indexing-tweets-google-is-pulling-them-directly-from-the-api/ var stLink = jQuery('a:last')[0]; stLink.href = 'javascript:void(0)'; SHARETHIS_post = [...]

  5. [...] bueno es saberlo http://soshable.com/forget-indexing-tweets-google-is-pulling-them-directly-from-the-api/ [...]

  6. [...] Forget Indexing Tweets: Google Is Pulling Them Directly from the API (tags: twitter) [...]

  7. [...] media searches. Apparently, that wasnt fast enough, so theyre going straight to the source.Source:http://soshable.com/forget-indexing-tweets-google-is-pulling-them-directly-from-the-api/ [...]

  8. [...] Source:http://soshable.com/forget-indexing-tweets-google-is-pulling-them-directly-from-the-api/ from → Uncategorized ← New music industry plan: halt flow of money to pirate music sites LikeBe the first to like this post. No comments yet [...]

  9. [...] Soshable noticed that those account which have been upgraded to the new Twitter search results display the latest tweet immediately after it has been tweeted. This, they deduce, means that Google is pulling right from Twitter’s API rather than waiting for tweets to be indexed. [...]

  10. [...] you can say one thing about Google is that it likes to do things for itself.  Soshable reports “Forget Indexing Tweets: Google Is Pulling Them Directly from the API.”  Google launched Caffeine last year as a tool for real time web indexing with a heavy [...]

  11. [...] ??? ?????? ????? ????????? ????, ????? ???? ??????? ????? ?????? ????? ??????? ??????, ?????? ??? ?-API, ????? ????? ???????? ??????? ??? ????? ?? ??????? [...]

  12. [...] More often than not, a customer will refrain from slamming you on social media, filing a chargeback, reporting you to the BBB, and other revenge tactics if you simply give them the opportunity to vent to the owner. Deprive the customer of that simple bit of communication and you’ll likely regret it later as Google indexes your customer’s public rage. You don’t want your business name coming up in search engine result pages (SERP) as part of a customer rant – definitely bad for SEO. And yes – Google sees and indexes Tweets very, very quickly. [...]

  13. [...] between Google and Twitter seemed to start off pretty well, when it was first reported in March last year that Google was apparently pulling tweets directly from Twitter’s API, to [...]

Speak Your Mind

*