This Is Odd

I very much doubt this was intentional…at least, I hope it was not, but it seems Feedster and Blinx have been taken out of Google's results in one way or another. Read up on it here and here…….

I very much doubt this was intentional…at least, I hope it was not, but it seems Feedster and Blinx have been taken out of Google’s results in one way or another. Read up on it here and here….

Author: John Battelle

A founder of NewCo (current CEO), sovrn (Chair), Federated Media, Web 2 Summit, The Industry Standard, Wired. Author, investor, board member (Acxiom, Sovrn, NewCo), bike rider, yoga practitioner.

7 thoughts on “This Is Odd”

  1. The only page a can get to come up in the SERPS is a Feedster tutorial on BLOGGER, I’m not actually sure if this does / doesn’t fuel any potential conspiracy theories?

    http://www.google.com/search?sourceid=navclient&ie=UTF-8&q=%22A+Tutorial+from+the+Folks+at+Feedster%22

    Here is the page from Google’s cache, this was my first port of call to attempt to find feedster.com

    http://66.102.11.104/search?q=cache:Xw_rAMqAXAEJ:feedster.com/tutorials/bloggerbasics/+%22A+Tutorial+from+the+Folks+at+Feedster%22&hl=en

    I can’t believe it

  2. here’s a theory: the search-engine spammers that have been trying to game some of the blogging-related directories and sites may have gotten sites like feedster caught up in google’s anti-link-farm machinery.

  3. Hey, I happened to be at working late tonight, so let me see if I can take a stab at it. The query [blinkx] returns Blinkx at #1, and [site:blinkx.com] returns 250+ results, so that’s good. I’m guessing that John is wondering why the url query [www.blinkx.com] doesn’t return their root page. At first glance I’d guess it’s because Blinkx has a zero second meta refresh. If you wget http://www.blinkx.com/ you get basically an empty page with this redirect:
    meta http-equiv=”refresh” content=”0;URL=http://www.blinkx.com/overview_us.php”
    I’ll ask a crawl person to check on it, though.

    The Feedster case is a little easier: it appears that Feedster is serving different content depending on the user agent. A normal user gets normal content, but when the user-agent contains “Googlebot/2.1,” Feedster serves up a 404. I verified this from the Googleplex and from my school account, but you can try it for yourself as well:

    # Fetch as a normal user
    % wget http://www.feedster.com/
    –21:39:51– http://www.feedster.com/
    => `index.html.8′
    Resolving http://www.feedster.com... done.
    Connecting to http://www.feedster.com[66.151.189.204]:80... connected.
    HTTP request sent, awaiting response… 200 OK
    Length: unspecified [text/html]

    [ ] 6,266 75.54K/s

    21:39:51 (75.54 KB/s) – `index.html.8′ saved [6266]

    # Now fetch with a Googlebot-like user agent
    % wget -U Googlebot/2.1 http://www.feedster.com/
    –21:40:02– http://www.feedster.com/
    => `index.html.9′
    Resolving http://www.feedster.com... done.
    Connecting to http://www.feedster.com[66.151.189.204]:80... connected.
    HTTP request sent, awaiting response… 404 Not Found
    21:40:02 ERROR 404: Not Found.

    Given that the issues appears to be on Feedster’s side in this case, if they’ll start serving Google a normal page again instead of a 404, I would expect their root page to be back right as rain in a few days. Okay, back to work for me..

Leave a Reply