Indexing errors reference - Webmaster. Help

References

Indexing errors reference

Loading errors

List of errors returned by the Yandex robot if it fails to download a document from your website.


Error	Description
Connection failure	Connection interrupted when trying to download a document. After several attempts the download was stopped.
Text size limit exceeded	The document is too long, try to break it into parts.
The document is blocked from indexing in robots.txt	The document is not indexed because you or another administrator blocked it from crawling in robots.txt.
Invalid document address	The document address doesn't conform to the HTTP standard.
Document format not supported	The server doesn't indicate the document format or indicates it incorrectly, or the indicated format isn't supported by Yandex.
DNS error	DNS error. IP address of the host couldn't be determined by its name.
The HTTP status code doesn't conform to the standard	The server returns a status code that doesn't conform to the HTTP standard.
Invalid HTTP header	HTTP header doesn't match the standard (including expansion from Yandex).
Failed to connect to the server	Failed to connect to the server.
Invalid message length	Message length is not indicated or is indicated incorrectly.
Wrong encoding	Transfer-Encoding header is set incorrectly or the encoding is unknown.
Invalid data amount transferred	The length of transferred data doesn't match the stated length. Data transfer is finished before or goes on after receiving the stated amount of data.
Maximum HTTP header length exceeded	The length of HTTP headers exceeded the limit. It may be caused by the attempt to pass too many cookies.
Maximum URL length exceeded	The length of URL address exceeds the limit.


Error	Description
Connection failure	Connection interrupted when trying to download a document. After several attempts the download was stopped.
Text size limit exceeded	The document is too long, try to break it into parts.
The document is blocked from indexing in robots.txt	The document is not indexed because you or another administrator blocked it from crawling in robots.txt.
Invalid document address	The document address doesn't conform to the HTTP standard.
Document format not supported	The server doesn't indicate the document format or indicates it incorrectly, or the indicated format isn't supported by Yandex.
DNS error	DNS error. IP address of the host couldn't be determined by its name.
The HTTP status code doesn't conform to the standard	The server returns a status code that doesn't conform to the HTTP standard.
Invalid HTTP header	HTTP header doesn't match the standard (including expansion from Yandex).
Failed to connect to the server	Failed to connect to the server.
Invalid message length	Message length is not indicated or is indicated incorrectly.
Wrong encoding	Transfer-Encoding header is set incorrectly or the encoding is unknown.
Invalid data amount transferred	The length of transferred data doesn't match the stated length. Data transfer is finished before or goes on after receiving the stated amount of data.
Maximum HTTP header length exceeded	The length of HTTP headers exceeded the limit. It may be caused by the attempt to pass too many cookies.
Maximum URL length exceeded	The length of URL address exceeds the limit.

Processing errors

The list of errors returned by the robots in case they downloaded the document successfully but further processing was impossible.


Error	Description
The document contains the `noindex` meta tag	The document isn't indexed because it contains the `noindex` meta tag.
Wrong encoding	The document contains characters that don't correspond to the declared encoding.
Document is a server log	The document was recognized as a server log. If it's a page created for website visitors, try to change it so that it won't look similar to a server log.
Invalid document format	The robot found that the document doesn't match the declared format (HTML, PDF, DOC, RTF, SWF, XLS, PPT).
Encoding not recognized	Document encoding wasn't recognized. Perhaps, the document doesn't contain text or contains text in different encodings.
Language not supported	The document language isn't recognized or isn't supported. For details about all supported languages go to the relevant help section.
Document does not contain text	The server returns an empty document.
Too many links	The number of links on the page exceeds the limit.
Extraction error	There was an error unpacking GZIP or DEFLATE data stream from the server.
Empty server response	The server returned a response of zero length. Contact the administrator of the hosting server.
Document is not canonical	The `link` element in the document code contains the `rel` attribute set to`canonical` and pointing to another (canonical) document. Canonical document was indexed instead of the current document.


Error	Description
The document contains the `noindex` meta tag	The document isn't indexed because it contains the `noindex` meta tag.
Wrong encoding	The document contains characters that don't correspond to the declared encoding.
Document is a server log	The document was recognized as a server log. If it's a page created for website visitors, try to change it so that it won't look similar to a server log.
Invalid document format	The robot found that the document doesn't match the declared format (HTML, PDF, DOC, RTF, SWF, XLS, PPT).
Encoding not recognized	Document encoding wasn't recognized. Perhaps, the document doesn't contain text or contains text in different encodings.
Language not supported	The document language isn't recognized or isn't supported. For details about all supported languages go to the relevant help section.
Document does not contain text	The server returns an empty document.
Too many links	The number of links on the page exceeds the limit.
Extraction error	There was an error unpacking GZIP or DEFLATE data stream from the server.
Empty server response	The server returned a response of zero length. Contact the administrator of the hosting server.
Document is not canonical	The `link` element in the document code contains the `rel` attribute set to`canonical` and pointing to another (canonical) document. Canonical document was indexed instead of the current document.