I pinged the indexing team at Google, but this is almost certainly something weird going on with cakecentral.com's webhost: wget http://cakecentral.com/ http:/

I pinged the indexing team at Google, but this is almost certainly something weird going on with cakecentral.com's webhost: wget http://cakecentral.com/ http://cakecentral.com/ --2011-01-14 09:12:50-- http://cakecentral.com/ http://cakecentral.com/ Resolving cakecentral.com... 174.129.211.41 Connecting to cakecentral.com|174.129.211.41|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2011-01-14 09:13:01 ERROR 404: Not Found. Once the root page of a site starts returning 404s, we have to start taking guesses about the best way to handle it. Best advice for Cake Central: make sure your root page returns a valid HTML page with a 200 response code. P.S. If the webhost is trying to do something sneaky, e.g. things work for browsers, but wget or Googlebot is treated differently somehow, the owner of Cake Central can use our free "Fetch as Googlebot" feature in our webmaster console to help diagnose the problem. Summary: not the weirdest search result I've seen by far. Webhosts that serve up 404s, redirects, or duplicate error pages can cause arbitrary things to happen in search engines. Bing doesn't have the url cakecentral.com indexed at all, for example. Blekko has it, but their page is from Nov. 11, 2010, so they're probably missing the 404 issue by being a couple months older.