Microsoft Bing Still Spamming Fake Referrers In Webmaster Log Files

August 25, 2009 by: admin

I normally don’t get upset when I report about bugs with search engines, it is what I do. But I am really getting upset with Microsoft and their webmaster support with Bing, really. For the umpteenth time, Microsoft said they fixed the fake referrer issue that has been plaguing webmasters since 2007 and they have lied again. Well, maybe the word lied is a strong word, maybe Microsoft simply has no idea how to manage a search spider or crawl the web?

The day after Microsoft said they fixed the issue with fake referral data showing up in log files, webmasters said the issue is still there. We have updated threads at Bing Forums and WebmasterWorld, the issue is still going on.

I am sorry for being so upset about this, but this is seriously a bit out of hand. Why? Well, we reported this issue so many times, here is an archive:

Now these are only issues specific to fake referrers clogging up our log files. This doesn’t mention the issues with Cashback rewards, or Bing clicking on their own search ads, or NOODP tag, the geotargeting issues, crawling too fast, adding pound signs to URLs and much more.

So I am a bit upset with Bing Webmaster support.

Forum discussion at Bing Forums and WebmasterWorld.



Related posts:

  1. Bing’s MSNBot Crawling Fake File Names?
  2. Fake Google Matt Cutts Ban List Referrers?
  3. Bing Webmaster Tools Unexpected Errors
  4. Fake Yahoo Employee, Not Fake: Side Money?
  5. Bing Webmaster Tools Bug Won’t Allow Adding Sites
  6. Bing’s Fake Referrer Spam Back, Now Hiding Referrer Now?
  7. Did Microsoft Finally Fix The Fake Referrer Spam Issue?
  8. Microsoft Claims To Fix Fake Referrals or “Single Word Query” Complaint
  9. What is “Page Score” in Bing Webmaster Tools?
  10. Bing Classifies Cloaking Detection as “Single Word Query” Issue
  11. More Cloaking Tests In Form Of Fake Referrers From Microsoft Bing?
  12. Microsoft To Fix Fake Referrer Data From Live Search

This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.

Trackbacks

Leave a Reply