Stationmaster needs to develop a good habit: see IIS Log

Did you notice the IIS log?

Baidu Crawler Normal Crawl page, the return of the HTTP status is 200 0 0, now crawl to his web page is always 200 0 64, he asked what this 64 mean, is not Baidu clear page, what solution. I have also written an article about Baidu, Google,yahoo search engine Spider crawler articles, talked about the three search engines crawl Site page characteristics.　　However, there is no analysis for the returned HTTP status, such as 200 0 64. This is a related explanation in IIS: NET HELPMSG 64--the specified receptacle name is no longer available. This means that the specified network name is not available, may be a path error, or the file may no longer exist, but this is only the HTTP status description of IIS itself.　　And in the Baidu Reptile log returned 200 0 64, and it is well known that Baidu has human intervention, which 64 explains what?　　Baidu Institute in the forum to see a moderator has such an explanation: Spiders in the IIS behavior 200 0 64 explanation according to my previous time to the present observation, although there is not enough evidence, but basically can certainly in IIS, if the spider behind the number appears 200 0 64 Then this single page in the site will disappear in the search engine. I was written on the page after K 200 0 64, do not know whether you agree, there are other views, of course, I said this is not absolute enough, because I also have a page behind the show 200 0 64 But it can still be found in search engines. This also explains the problem, but most of the 200 0 64 Web pages are gone.

So I think Spider's 200 0 64 behavior can be interpreted as clearing data.

This explanation, at present, seems to have credibility. Flymorn that the crawl state of 200 0 64 is not normal crawl, the normal crawl is the success of the logo 200 0 0, when the status of the 200 0 to show that the search engine in the crawl this page when the error occurred, not normal to the conventional crawl; for Baidu,　　Baidu is probably no longer grabbing these pages into the main index library, but put into the "Baidu Sandbox" in the investigation, how long to see how you improve, perhaps, you do not see Baidu to these sites are released by K, people are not regular. Exactly, Flymorn also has been Baidu K website, open this site's IIS log (. Log suffix, such as ex080222.log), sure enough, also found Baidu returned 200 0 64 status: 2008-02-22 07:14:37 w3svc78302822 58.17.36.91 get/article/1/79.html-80-61.135.163.102 baiduspider+ (+[url]http://www.baidu.com/search/spider.htm[/ URL] 0 2008-02-22 07:18:07 w3svc78302822 58.17.36.91 get/article/1/11.html-80-61.135.163.102 baiduspider+ (+[url ]http://www.baidu.com/search/spider.htm[/url] 200 0 64 for the site has been Baidu hair, if you still care about Baidu, then quickly correct all the sites on the cheating place, eliminate excessive optimization, eliminate malicious links, Waiting for Baidu to come again, generally speaking, this takes 2-3 months time, or seriously do stand, first think of users as well.

For the new station, because Baidu included to release this process is very long, due attention to IIS log can let you know in advance whether you are included, not very good? For the old station, is not careful Baidu K, then look at the log can know in advance whether it will k you, not suddenly be killed by seconds. Therefore, it is necessary to look at the IIS log.

My new station today on-line C3C3C novel net www.c3c3c.com welcome everybody to contact me to make a friendship connection, the common progress.