free html hit counter This Is Odd - John Battelle's Search Blog

This Is Odd

By - August 20, 2004

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….

Related Posts Plugin for WordPress, Blogger...

7 thoughts on “This Is Odd

  1. I got no problem with Blinkx and Feedster is first out here in canada for their subdomain but I post a similar story on Icerocket who was launch 18 days ago and when Google News got more than 50 link on it since 2 weeks ?
    Here the post :

  2. ID:entity says:

    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?

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

    I can’t believe it

  3. jim winstead says:

    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.

  4. Rob says:

    The links go some way to explore why Feedster is missing from the results, but what’s the story with blinkx?

  5. mos says:

    collateral damage? 🙂

  6. GoogleGuy says:

    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 [] returns 250+ results, so that’s good. I’m guessing that John is wondering why the url query [] 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 you get basically an empty page with this redirect:
    meta http-equiv=”refresh” content=”0;URL=”
    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
    => `index.html.8′
    Resolving done.
    Connecting to[]: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
    => `index.html.9′
    Resolving done.
    Connecting to[]: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..

  7. Scott Rafer says:

    Thank you! We’ll give your solution a shot and see if we get re-included.