Little Background: Bing was down for over 36 hours which is why Google sort of indexed their “Error” page for one of their domains – Bing Travel. Many days has passed, but it seems like Google hasn’t updated the search snippet. Matt Cutts replied in Techcruch with a screen shot saying the problem has been fixed — But apparently the issue is something else. Read on…
This morning when I was reading this story on Techcrunch, I initially thought of blogging about it, but as i scrolled down I saw Matt Cutts’s responses in the story where he pretty much cleared the air stating that this was just a fluke and certainly not intentional (well these were not his exact words, but I think I sort of made it up). But anyway that’s not the point. The point is he actually showed everyone a screen shot (http://www.mattcutts.com/images/bing-travel-snippet.png) where the problem seemed fixed:
Based on Matt’s screen shot I did a search for “bing travel” in Google and found the snippet to be back to normal. I noticed that the last date of cache was indeed 9th July, just like what Matt said. But many people were still complaining that they can’t see the ‘updated snippet’ and at that time I thought that this may be a DC issue (Google has many data centers and they take time to propagate).
However after 6 hours or so, I noticed that Andy Beal is covering the story in Marketing Pilgrim. So I became a bit curious and tried the search again this time only with the key phrase “bing and to my surprise I got the same old snippet –
Then I looked up the cache of both pages and it seems like Google has two version of Bing Travel page indexed -
Version 1: http://www.bing.com/travel
Last Cache Date: 4th July
Version 2: http://www.bing.com/travel/ [This one basically has a forwarding slash at the end of the URL]
Last Cache Date: 9th July
Hopefully this is temporary and both Google and Bing looks into it rather than playing the blame game.