I believe many webmasters or SEOs know the existence of IIS log, but many people don't pay attention to it, because we can query some basic data of the website through webmaster tools. Why look at IIS log?
IIS log is mainly used to record the access behavior of users and search engine spiders to the website. In short, website IIS log refers to recording the behavior status code of various search engine spiders visiting and grabbing the website, and generating IIS log in the form of file.
We can let us know the records of spider visits through IIS logs, and let us know the dead links and return status codes of the website, so that we can timely analyze the collection and snapshot update of the website.
(1) Through the IIS log, you can understand the basic crawling situation of the spider to the website, and you can know the crawling track and amount of the spider. Through our IIS log, the amount of the external chain has a direct impact on the crawling amount of the website spider. The link bait we call is that if you make an external chain, when the spider crawls the external chain page and releases the page, The spider can crawl your website through the link you left, and the IIS log will record the spider's crawling action.
(2) The update frequency of the website is also related to the frequency of spider crawling in the IIS log. Generally speaking, the higher the update frequency, the higher the spider crawling frequency. The update of our website is not only the addition of new content, but also our fine-tuning operation.
(3) We can give early warning of some things and problems in our space according to the response of IIS logs, because if there is a problem with the server, it will be reflected in IIS logs for the first time. We should know that both the stable speed and opening speed of the server will directly affect our website.
(4) Through IIS logs, we can analyze which pages of the website are very popular with spiders, and which pages are not even touched by spiders. At the same time, we can also find that some spiders have a great loss of our server resources due to excessive crawling. We need to screen them.
(1) Whether the external chain we send has an effect?
(2) Is the space we buy stable?
(3) What pages do spiders like more than others?
(4) When do spiders grab our website frequently and when do we need to update the content?
(5) Which search engines like our website content (for details, see Ma Haixiang's blog "interpretation of search engine spider name code and crawling return code in IIS log")?
(6) Are there hidden dead links and wrong links in the website?
We can simply analyze these problems through our server IIS log, and these data can not be accurately tested by ordinary SEO tools.
4. How do I download IIS log files?
First of all, our space should support IIS log download, which is very important. Before we buy space, we must first say hello. Support does not support IIS log download, because some service providers do not provide this service.
In indows2003 environment, the default storage path of IIS logs is C: \ windows \ system32 \ logfiles \. Under the logfiles folder, there are multiple IIS log folders, and each IIS log folder corresponds to a site log.
If the IIS local folder is not configured, you can go to the space to download. Generally, the space is placed in the log folder of the root directory by default, and the IIS log is a text file with the suffix log.
Many webmasters using Windows IIS may encounter this problem, that is, the growth of IIS logs on the server will often lead to full disk space. If the server administrator does not store large files on Disk C and the site access in IIS is very large, 90% of the disk capacity of Disk C is occupied by IIS log files.
The default storage path for IIS log files is C: \ windows \ system32 \ logfiles. We open "my computer", drive C, windows folder, system32 folder and logfiles folder in turn. We find that there are multiple subfolders in it, and each folder corresponds to an IIS site.
(1) Enter the "Internet Information Service (IIS) manager" console interface, as shown in the following figure, right-click the "website" item on the left of the console to open the "website properties" setting window.
(2) In the "website" tab, select the check box before "enable logging", and then click the "apply" button to make the settings effective and enable the logging function of the website.
(3) Continue the configuration, set the "activity log format (V)" to "W3C extended log file format", and then click the "properties" button to configure the logging properties, so as to modify the path of IIS log file.
In addition, there is a very important problem. Ma Haixiang strongly recommends that IIS logs be generated every hour. Small enterprise stations and websites with less page content can be set to one day. It defaults to one day. If there are many contents or large stations are set to generate once a day, only one file will be generated a day, which will be quite large, Sometimes when the computer is turned on, it will cause crash. If you set it, you can find a space provider to coordinate the setting.