HTTP status codes reference

The requested URL corresponds to more than one resource, and the robot failed to determine which page it refers to (code 300 Multiple Choices).

Fix the headers and specify the resource correctly, and then the robot will be able to index the page.

The document isn't used by the server anymore and the link redirects to another page (code 301 Moved Permanently).

Displaying such pages serves no purpose as users can't view these pages, so the robot doesn't index them. However, the robot will index the redirect target page, if it's available.

The requested resource is temporarily located under another address (code 302 Found).

Displaying such pages serves no purpose as users can't view these pages, so the robot doesn't index them. However, the robot will index the redirect target page, if it's available.

The requested resource resides under a different URL and should be requested with the GET method (code 303 See Other). For the page to appear in the search, it must respond with the 200 code.

Code 304 Not Modified. Respond with this code if the page hasn't changed since the last visit by the robot. This will speed up indexing and reduce the traffic.

The requested resource can be accessed only through the proxy server specified in the Location header (code 305 Use Proxy).

The requested resource has been temporarily relocated to another address. Specify this address in Location (code 307 Temporary Redirect).

The server can't understand the request due to incorrect syntax.

A password is required to access the document or the user must be registered.

Internal error or a configuration error on the server.

Access to the document is forbidden. To have the page indexed, allow access to it.

The document doesn't exist. If you deleted a section of the website, you can use robots.txt to prevent the robot from accessing it. If such a page on the website never existed, ignore this error. Somebody could put an incorrect link to your website.

The method defined in the request (Request-Line) can't be applied for the specified resource, so the robot couldn't index it.

The document exists, but the format is incorrect (the robot doesn't support the language or encoding).

Registration on the proxy server is required.

The website failed to complete the request within the specified time and the robot disconnected.

The request conflicts with another request or with the server configuration.

The requested resource was permanently deleted from the website.

The server refuses to accept the request without a certain Content-Length header. Correct the headers on your server so that the robot will be able to index the page next time.

The server found a mismatch in one or more request header fields (a failure or an error in the precondition processing).

The server refuses to process the request because it is larger than the server can handle.

The server refuses to process the request, because the URI (Request-URI) requested by the robot is longer than the server can render.

The server refuses to process the request, because the request body has an unsupported format.

The server refuses to process the request, because the Range field in the request header contains an invalid byte range.

The server refuses to process the request, because the value of the Expect field in the request header is unexpected.

The server can't process one or more request elements.

The server refuses to process the request, because one of the required resources is blocked.

The server refuses to process the request, because one of the dependent resources is blocked.

The server requested connection upgrade to SSL, but the client doesn't support SSL.

Too many requests sent in a short time. This may indicate, for example, a DDoS-attack attempt. The response can be accompanied by a Retry-After header that indicates after what time the request can be repeated. Yandex doesn't take this header into account.

The server encountered an unexpected condition that doesn't allow it to complete the request.

The server doesn't support the functionality required to execute the request. This response means the server doesn't recognize the request method and can't provide it for any resource.

The server acting as a gateway or proxy server received an invalid response from an inbound server it accessed while attempting to fulfill the request.

An error occurred due to temporary overload or disconnection for server maintenance.

The server, while acting as a gateway or proxy, didn't receive a timely response from an upstream server it needed to access in order to complete the request.

The server doesn't support or refuses to support the version of the HTTP protocol used in the robot request message.

The server can't process the request due to the lack of the disk space.

The server can't process the request because the requested extension isn't supported.