| 400 (Bad Request) |
The server does not understand the syntax of the request. |
| 401 (authentication error) |
This page requires authorization. You may not want to include this page in the index. If the page is listed in your Sitemap, you can delete it. However, if you keep it in your Sitemap, we will not crawl or index the page (although the page will continue to remain in an error state listed here). If we crawl it as part of a search crawl, you can check the reason for it in our webmaster information. |
| 403 (Forbidden) |
The server rejected the request. If you see this status code when Googlebot tries to crawl a valid webpage on your site (available in Google Webmaster Tools <strong> Diagnostics </strong> <strong> Network capture </ Strong> page), it is possible that your server or host denied Googlebot access. |
| 404 (Not Found) |
The server could not find the requested Web page. For example, this code is often returned for Web pages that do not exist on the server.
If you do not have a robots.txt file on your site and you see this status code on the robots.txt page of the Google Webmaster Tools Diagnostic tab, this is the correct status code. However, if you have a robots.txt file and you see this status code, your robots.txt file may be named incorrectly or in the wrong location (the file should be in the top-level domain named robots.txt).
If you see this status code for URLs Googlebot trying to crawl (on the HTTP error page of the Diagnostics tab), it means that Googlebot tracking may be an invalid link to another page (a link that is old or incorrectly entered). |
| 405 (method Disabled) |
Disables the method specified in the request. |
| 406 (not accepted) |
The requested content attribute could not be used to respond to the requested Web page. |
| 407 (requires proxy authorization) |
This status code is similar to 401, but specifies that the requestor must authorize the use of the proxy. If the server returns this response, it also indicates that the requestor should use the proxy. |
| 408 (Request timed out) |
A timeout occurred while the server was waiting for a request. |
| 409 (conflict) |
The server encountered a conflict while completing the request. The server must include information about the conflict in the response. This code may be returned by the server in response to a PUT request that conflicts with the previous request, as well as a list of differences of two requests. |
| 410 (Deleted) |
After the requested resource is permanently deleted, the server returns this response. This code is similar to the 404 (not Found) code, but is sometimes used to replace the 404 code in cases where the resource existed before and now does not exist. If the resource has been permanently deleted, you should use 301 to specify a new location for the resource. |
| 411 (valid length required) |
The server does not accept requests that do not contain a valid Content-Length header field. |
| 412 (precondition not met) |
The server did not meet one of the prerequisites set by the requestor in the request. |
| 413 (Request entity too Large) |
The server cannot process the request because the request entity is too large to exceed the processing power of the server. |
| 414 (The requested URI is too long) |
The requested URI (usually the URL) is too long and the server cannot process it. |
| 415 (Unsupported media type) |
The requested format is not supported by the requested page. |
| 416 (Request scope does not meet the requirements) |
If the page cannot provide the requested range, the server returns this status code. |
| 417 (expectations not met) |
The server does not meet the requirements for the expected Request header field. |