--- metadata: - name: generator content: Diplodoc Platform v5.64.0 alternate: - https://mobi.yandex.com/support/webmaster/en/indexing-options/server-response.md - https://mobi.yandex.com/support/webmaster/tr/indexing-options/server-response.md - href: https://mobi.yandex.com/support/webmaster/en/indexing-options/server-response.md type: text/markdown title: Markdown version - href: https://mobi.yandex.com/support/webmaster/en/llms.txt?revision=r21857035 rel: describedby --- > **Documentation Index:** Fetch the complete configuration index at https://mobi.yandex.com/support/webmaster/en/llms.txt?revision=r21857035 # Server response check You can use the [Server response check](https://webmaster.yandex.com/tools/server-response/) tool to find out whether the site pages are accessible to the Yandex robots, as well as other information about the site, such as the status of the SSL certificate. {% note alert %} If the server response differs from the HTTP status code 200 OK or it returns a message from the list below, the page is excluded from the search results. {% endnote %} The server response can be displayed as: **HTTP code**.   : For more information, see [HTTP status codes reference](https://mobi.yandex.com/support/webmaster/en/error-dictionary/http-codes.md). **The SSL certificate status for the HTTPS sites**   : #| || **The SSL certificate status message for the site** || || The certificate issuing authority wasn't found. || || The certificate signature couldn't be decrypted. The RSA key value doesn't match the expected value. || || The public key can't be read. || || The certificate signature is invalid. || || The certificate isn't active yet. || || Certificate expired. || || Error in the certificate effective date. || || Error in the certificate expiry date. || || The certificate is self-signed and isn't found in the list of trusted certificates. || || The certificate chain may contain untrusted certificates, but the root certificate wasn't found. || || The CA certificate wasn't found. || || Signatures can't be verified because the certificate chain contains only one certificate and it isn't self-signed. || || The certificate is revoked. || || The certificate authority is invalid. || || Certificate chain length exceeded. || || Invalid [certificate type](https://mobi.yandex.com/support/webmaster/en/yandex-indexing/https-migration.md#sert). || || The root certificate authority is not trusted. || || The root certificate authority rejected the certificate. || || Unknown certificate error. || || The root certificate is blacklisted. || || The certificate has already been issued to another site. || || Node certificate is missing. || |# To resolve problems with the SSL certificate, contact your certification center or your hosting provider. **Other message**   : #| || **Message** | **Note** || || Document failed to load | It appears for the following reasons: - The robot's request is blocked on the server side or a connection fault occurs when trying to get a response. In this case, check whether the robot is blocked by IP. - DNS error. Make sure that the site is accessible and the DNS is configured properly. If the settings have been changed recently, the data is updated within 24 hours. - Response timeout expired. A response should be received within 3 seconds. || || Failed to connect to the server | ^ || || A connection failure occurred | ^ || || The `noindex` tag disables URL indexing | The page has the `robots` meta tag with the [noindex directive](https://mobi.yandex.com/support/webmaster/en/controlling-robot/metatags.md#sup). || || URL indexing is disallowed in the robots.txt file | The `robots.txt` file contains the [Disallow directive](https://mobi.yandex.com/support/webmaster/en/robot-workings/allow-disallow.md) that prohibits indexing the page or directory where it's located. || || The document size is too large | The maximum page size is 10 MB. || || Document format not supported | HTML documents and files of the following types are supported: PDF, DOC/DOCX, XLS/XLSX, PPT/PPTX (MS Office); ODS, ODP, ODT, ODG (Open Office); RTF, TXT, and SWF. || || Invalid response code | [Standard HTTP status codes are supported](https://mobi.yandex.com/support/webmaster/en/error-dictionary/http-codes.md). || || The document language isn't recognized. | [List of supported languages](https://mobi.yandex.com/support/webmaster/en/yandex-indexing/locale-pages.md#supported-language). || || The document doesn't contain text. | The page is empty or has no content that can be indexed by the robot. || || Page content is missing | Check the following in your server settings: - HTTP header For example, if it contains "Content-length: 0", the robot will fail to index the page. - The size of the page content. It must be greater than 0 and match the HTTP header. || |# {% note info %} A response received using the “Server response check” tool may differ from the actual response to the robot, since the tool has a different IP. You can check the response in your server logs. {% endnote %} ## How do I check the server response in Yandex Webmaster? {#how-to} 1. Go to the [Server response check](https://webmaster.yandex.com/tools/server-response/) page. 1. In the **Requested URL** field, enter the URL of the page you want to check. For example, `https://www.example.com`. 1. In the **Robot** field, select the robot to check if it can access the page. The dropdown list contains the main robots that crawl most sites. Once you select the robot, its User-agent is displayed under the field. For more information, see [Yandex robots in server logs](https://mobi.yandex.com/support/webmaster/en/robot-workings/check-yandex-robots.md#robot-in-logs). 1. Click the **Check** button. You can also check the response if your server responds to the If-Modified-Since header with the HTTP status code 304 (Not Modified). To do this, specify the date and time in the **If-Modified-Since** field: - When the page being checked was last updated. In this case, the received response must contain the HTTP status code 200 OK. - A different date: you'll get a response with code 304 (Not Modified). ## Questions and answers {#qanda} {% cut "The “Document contains no text” status is displayed when checking Sitemap" %} The status indicates that the robot can't index the file as a regular site page and include its contents in search results. This status doesn't affect the `Sitemap` processing. To check for `Sitemap` correctness, use the webmaster tool [Sitemap validator](https://mobi.yandex.com/support/webmaster/en/indexing-options/tool-sitemap.md) tool in Yandex Webmaster. {% endcut %} {% cut "The “URL has been excluded from indexing with the 'noindex' tag” status is displayed when checking Sitemap" %} This status indicates that the file is blocked from indexing. Typically, this restriction is set in the [X-Robots-Tag HTTP header](https://mobi.yandex.com/support/webmaster/en/controlling-robot/metatags.md#meta-robots). The directive prohibits a file from appearing in search results, but doesn't affect the processing of the `Sitemap` content. To check for `Sitemap` correctness, use the webmaster tool [Sitemap validator](https://mobi.yandex.com/support/webmaster/en/indexing-options/tool-sitemap.md) tool in Yandex Webmaster. {% endcut %} ### Learn more - [Tool usage limits in Yandex Webmaster](https://mobi.yandex.com/support/webmaster/en/indexing-options/quotas.md)
{% cut "Report an error in the tool" %} Specify the tool in which you found the error, describe the situation in as much detail as possible, and if necessary, attach a screenshot that illustrates it.
{% endcut %}



You can also go to

[![](../_assets/logo/logo-pic.svg)](https://webmaster.yandex.com/) [![](../_assets/logo/logo-en.svg)](https://webmaster.yandex.com/)