HTTP status code
1xx (provisional response)
A status code that represents a temporary response and requires the requester to continue the operation.
| 100 (continued) |
The requester should continue to make the request. The server returns this code to indicate that it has received the first part of the request and is waiting for the rest. |
| 101 (switching protocol) |
The requester has asked the server to switch the protocol, and the server has confirmed and is ready to switch. |
2xx (success)
indicates the status code of the request successfully processed.
| 200 (success) |
The server has successfully processed the request. Usually, this means that the server provided the requested page. If this status code is displayed for your robots.txt file, it means that Googlebot has successfully retrieved the file. |
| 201 (created) |
The request was successful and the server created a new resource. |
| 202 (accepted) |
The server has accepted the request, but has not yet processed it. |
| 203 (Non-authorized information) |
The server has successfully processed the request, but the information returned may come from another source. |
| 204 (no content) |
The server successfully processed the request, but did not return any content. |
| 205 (Reset content) |
The server successfully processed the request, but did not return any content. Unlike the 204 response, this response requires the requester to reset the document view (for example, clear the form content to enter new content). |
| 206 (partial content) |
The server successfully processed some GET requests. |
3xx (redirect)
To complete the request, further action is required. Usually, these status codes are used for redirection. Google recommends that you use no more than 5 redirects in each request. You can use Webmaster Tools to check if Googlebot is having problems crawling redirected pages. The web crawl page under Diagnosis lists URLs that Googlebot cannot crawl due to redirect errors.
| 300 (multiple choices) |
In response to the request, the server can perform various operations. The server can select an operation based on the requester (user agent), or provide a list of operations for the requester to choose. |
| 301 (moved permanently) |
The requested page has been permanently moved to a new location. When the server returns this response (response to a GET or HEAD request), it will automatically redirect the requester to the new location. You should use this code to tell Googlebot that a webpage or website has been permanently moved to a new location. |
| 302 (temporary move) |
The server currently responds to requests from web pages in different locations, but the requester should continue to use the original location to respond to future requests. This code is similar to the 301 code that responds to GET and HEAD requests . It will automatically send the requester to a different location, but you should not use this code to tell Googlebot that a certain webpage or website has moved because Googlebot will continue to crawl the original Location and indexing. |
| 303 (see other locations) |
The server returns this code when the requester should use separate GET requests for different locations to retrieve the response. For all requests except HEAD, the server will automatically go to another location. |
| 304 (unmodified) |
The requested page has not been modified since the last request. When the server returns this response, the content of the web page will not be returned. |
| 305 (Use a proxy) |
The requester can only use the proxy to access the requested page. If the server returns this response, it also indicates that the requester should use a proxy. |
| 307 (temporary redirect) |
The server currently responds to requests from web pages in different locations, but the requester should continue to use the original location to respond to future requests. This code is similar to the <a href=answer.py?answer=> 301 </a> code that responds to GET and HEAD requests . It will automatically redirect the requester to a different location, but you should not use this code to tell Googlebot something Pages or sites have moved because Googlebot will continue to crawl and index the original location. |
4xx (request error)
These status codes indicate that the request may have gone wrong, preventing the server from processing.
| 400 (Bad request) |
The server does not understand the syntax of the request. |
| 401 (Unauthorized) |
The request requires authentication. For the web page requested after login, the server may return this response. |
| 403 (forbidden) |
The server rejected the request. If you see this status code when Googlebot is trying to crawl a valid page on your website (you can see this information on the web crawl page under Google Webmaster Tools diagnosis), it may be rejected by your server or host Googlebot visits. |
| 404 (not found) |
The server cannot find the requested page. For example, this code is often returned for web pages that do not exist on the server. |
| 405 (Method disabled) |
Disable the method specified in the request. |
| 406 (not accepted) |
Unable to respond to the requested page with the requested content feature. |
| 407 (requires agency authorization) |
This status code is similar to <a href=answer.py?answer=35128> 401 (Unauthorized)</a>, but specifies that the requester should authorize the use of the proxy. If the server returns this response, it also indicates that the requester should use a proxy. |
| 408（请求超时） |
服务器等候请求时发生超时。 |
| 409（冲突） |
服务器在完成请求时发生冲突。服务器必须在响应中包含有关冲突的信息。服务器在响应与前一个请求相冲突的 PUT 请求时可能会返回此代码，以及两个请求的差异列表。 |
| 410（已删除） |
如果请求的资源已永久删除，服务器就会返回此响应。该代码与 404（未找到）代码类似，但在资源以前存在而现在不存在的情况下，有时会用来替代 404 代码。如果资源已永久移动，您应使用 301 指定资源的新位置。 |
| 411（需要有效长度） |
服务器不接受不含有效内容长度标头字段的请求。 |
| 412（未满足前提条件） |
服务器未满足请求者在请求中设置的其中一个前提条件。 |
| 413（请求实体过大） |
服务器无法处理请求，因为请求实体过大，超出服务器的处理能力。 |
| 414（请求的 URI 过长） |
请求的 URI（通常为网址）过长，服务器无法处理。 |
| 415（不支持的媒体类型） |
请求的格式不受请求页面的支持。 |
| 416（请求范围不符合要求） |
如果页面无法提供请求的范围，则服务器会返回此状态码。 |
| 417（未满足期望值） |
服务器未满足”期望”请求标头字段的要求。 |
5xx（服务器错误）
这些状态码表示服务器在处理请求时发生内部错误。这些错误可能是服务器本身的错误，而不是请求出错。
| 500（服务器内部错误） |
服务器遇到错误，无法完成请求。 |
| 501（尚未实施） |
服务器不具备完成请求的功能。例如，服务器无法识别请求方法时可能会返回此代码。 |
| 502（错误网关） |
服务器作为网关或代理，从上游服务器收到无效响应。 |
| 503（服务不可用） |
服务器目前无法使用（由于超载或停机维护）。通常，这只是暂时状态。 |
| 504（网关超时） |
服务器作为网关或代理，但是没有及时从上游服务器收到请求。 |
| 505（HTTP 版本不受支持） |
服务器不支持请求中所用的 HTTP 协议版本。 |