Need yahoo slurp administrator - problems with yahoo slurp on my site - hitting the site over million times...

Question

I need email of administrators or developers of Yahoo! slurp engine. This crawler is hitting my site very strangely - and it's making a lot of mess in logs and databases. Yahoo! Slurp is logged in my database that entered a site over 1,4 million times in 1 month (i am logging entries through global.asax) - this is becoming a huge problem...And all the time it is from Yahoo! Slurp range - 68.142...

Answer 1

Maybe this will help you. http://help.yahoo.com/help/us/ysearch/slurp/

Answer 2

(1) I suppose we will get used to this, though it does make the line length rather long. (2) This one gets my vote as best innovation. I have always felt cheated when I take the time to read all the answers, narrow it down to two or three, and re-read those to ensure that I vote for the answer that really is the best .............. and after all that I find I need not have bothered because the first poor answer has six votes already and the real best answer doesn't stand a chance because it is on the second page! (3) Haven't seen this yet. (4) Ok .... well, I will just have to remember to save it to my watchlist before reporting. (5) Good idea. I was sceptical about the incorrect reporting until I nearly did it myself the other day. I had sort of registered at the back of my mind that the answer box seemed smaller than usual, but didn't twig until I went to press Submit and saw the button said Report instead! I still think they should move the Report button - stick it over on the right, out of the way. (6) Oh I love this one! I've made good use of it already to give people an extra point for a really good answer. Edit:- Thanks for reminding me, H-man, I too have always thought it should be obligatory to give a reason for reporting. I have seen too many people complain of receiving a VN with no reason given. It seems most unfair to punish people without even telling them which rule they have broken.

Answer 3

Why don't you use a "robots exclude" file to stop the hits? Second thing is to limit the access on your server. We had to do this with a library that was inundated with page requests. Basically it just puts them in "time out" abd slows down the demand.



http://www.myklin.com