Background: I've got a popular site that's over 350 pages and is crawled regularly and aggressively, with visitors about 100,000 per month. It is a directory with categories and individual pages in each category. The site is ASP and is mostly driven via MS SQL. I've got an access database that only keeps track and reports page views for my news pages. The pages in the directory are of the format: category.asp?c=[x] where x = category number, and pageItem.asp?i=[y] where y = the item number I recently implemented Error 500 trap logging (an error 500 is a server error). To my knowledge the site had no problems but I wanted to trap errors because the site was so popular. The error generates an email which contains all the details of the error. It also sends a text message to my cell phone. I discovered that I had an illegal link on the site, of the format pageItem.asp?c=123 (note that "c" is an illegal query parameter, it should be "i". according to my error logging, the Error 500 was generated when search bots followed the link. Now, there are any number of ways of fixing this, but instead of fixing it I decided to do a little experiment. I removed the link to that illegal page, and I set it so that for that illegal page, instead of an Error 500 it would return to the agent an Error 410, which means the page is permanently gone and the bot should stop looking for it. The code is <% Response.Status = "410 Gone" %> What happened? Well, Google crawled the orphan illegal page twice in 12 hours and then never crawled it again. Nice, Googlebot, good Googlebot. MSN and inktomisearch/YahooSlurp continued to crawl the orphan page for a week. They would crawl the page in quick succession, so that I'd get three errors all within a 15 second span. I also discovered a bot called cyberalert that would crawl category.asp and pageItem.asp (with no query string). These are/were illegal pages that generated Error 500 results. I also found a number of minor errors in the website, including errors from Google search referrers that are too esoteric to bother explaining. One interesting thing I experienced is the reputed unruliness of Access databases - when too many people accessed the same page that had the pagecount kept in an Access database, there would be an error. Importing that Access database into MS SQL is number 35 on my list of simple things to do, so I just wrapped the Access page count routine in Application.Lock and Application.Unlock and in 30 seconds the problem is solved. Yes, of course I know that Access can't handle too many users, but it's educational to discover that for myself. (Yes, I know it's called a JET database, but people also call it an Access database so leave me alone). The Moral Of This Story: I highly recommend detailed error trapping on big busy sites - you'll be amazed what you'll find! I fixed all the problems discovered and I am at harmony with the Universe. OOOOOMMMMMMMMMM......