Welcome to WebmasterWorld Guest from 184.108.40.206
Forum Moderators: mack
2007-12-05 00:02:54 W3SVC278140942 XX.XX.XX.XX GET /Index.aspx - 80 - 220.127.116.11 HTTP/1.0 msnbot/1.0+(+http://search.msn.com/msnbot.htm) - - www.mysite.com 301 0 0 320 260 109
This breaks reverse DNS lookup on my site (and many other sites) with all the nasty consequences.
What pisses me off most is that they themselves recommended to use reverse DNS to identify their bot!
Very sloppy MSN, very sloppy.
Based on this and what I've seen of their robots.txt and on-page robots meta-tag handling, I have to agree with your assessment.
[edited by: jdMorgan at 4:49 am (utc) on Dec. 5, 2007]
Cached reverse DNS lookups for a quick test for bot validity and if that fails I check to see if it at least belongs to a range owned by the company associated with the bot and do this for Google, Yahoo, Microsoft, Ask, Gigablast, etc.
[edited by: incrediBILL at 5:30 am (utc) on Dec. 6, 2007]
Shurik: Excuse my lack of knowledge in this area, but does this have something to do with Slow Crawling, No Indexing or NO RANKING and NOT SHOWING in serps?
My MSN traffic stopped cold Oct 1st at 10 am Pacific Time when they switched on the new Algo.
Will this "fix" that MSNDude speaks of, address the issue and return the many lost sites to the serps?
Many of us are at a loss as to why we are not in the serps with this new Algo.
Thanks in advance for a post.
18.104.22.168 = bl1sch2033920.phx.gbl
22.214.171.124 = bl1sch2042520.phx.gbl
126.96.36.199 = by1sch4030220.phx.gbl