How webmasters handle planned site shutdown events

Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall

For some time, users often ask us if a site in Google Robot search is closed, then the site in Google search results in the "visibility" will be adversely affected. Sometimes 11518.html "> site shutdown is an unavoidable event: Site owners may temporarily close the site due to routine maintenance of the site or legal or cultural considerations." If you do not explicitly declare to the user that the site is closed for the above reasons, the reputation of the site may be adversely affected. While we cannot guarantee the search, indexing, or ranking of a site, we can still handle the planned site shutdown events in some way to avoid a negative impact on the "visibility" of web sites in search results.

For example, when a web page is searched, the site should not return HTTP result code 404 (not Found) or display an error page with status code (OK), but should return the 503 HTTP result Code (Service unavailable) and show the search engine that the site is only temporarily closed. In addition, the webmaster can also provide users and search engines with a general timetable for reopening the site by returning information. If you have the appropriate information, webmaster can also use the Retry-after header option to list in seconds of shutdown time or planned re-opening time, Google robot can use this information to determine when to search the site again.

Returning the 503 HTTP result code also helps solve many other problems. Some sites return the result code for server errors, site shutdowns, and congestion temporary placeholder pages ("under construction"), and these sites often encounter many problems in search. 503 HTTP result code is the preferred solution for webmaster to solve the above problem. If a planned server outage occurs for reasons such as hardware maintenance, you can use another server to return the 503 HTTP result code. It is worth noting that we cannot see the return of 503 as a permanent solution-the constant return of 503 will result in the impression that the server has been permanently shut down, causing us to remove the URL from the Google index.

Header (' http/1.1 503 Service temporarily unavailable ');

Header (' Retry-after:sat, 8 Oct 18:27:00 GMT ');

If you set a 503 (Service unavailable) return information, using PHP header information will be similar to the above.

Like how to make full use of 404 pages, we can also provide custom 503 information to explain the situation to users and help them understand when the site will be reopened. For more information about HTTP result codes, see RFC 2616.

Published by: Tomer Honen,kaspar Szymanski, Dublin search quality team

Original: How to deal with planned site downtime