--- metadata: - name: generator content: Diplodoc Platform v5.54.2 alternate: - https://yandex.com/support/webmaster/en/robot-workings/managing-redirects.md - https://yandex.com/support/webmaster/tr/robot-workings/managing-redirects.md - href: en/robot-workings/managing-redirects.md type: text/markdown title: Markdown version - href: ../llms.txt type: text/markdown title: llms.txt --- > **Documentation Index:** Fetch the complete configuration index at https://yandex.com/support/webmaster/en/llms.txt # Processing redirects ## What redirects are recognized by the Yandex robot? {#recognized-redirects} The Yandex robot recognizes standard [HTTP 3xx](https://yandex.com/support/webmaster/en/error-dictionary/http-codes.md#redirect-3xx) status codes (redirection). The main types of redirects: - 301/308 — Permanent redirect. - 302/303/307 — Temporary redirect. - A redirection that uses the [refresh](https://yandex.com/support/webmaster/en/controlling-robot/metatags.md#refresh) meta tag with small delays is considered a temporary redirect. ## What's the difference between in-host redirection and host-to-host redirection? {#different-redirects} In-host redirection is a redirection within the same host ([FQDN](http://en.wikipedia.org/wiki/FQDN)). Host-to-host redirection is redirection to a page residing on a different host. Example of an in-host redirect: ``` a.ru/ → a.ru/index.html www.a.ru/index1.html → www.a.ru/index2.html ``` Example of an inter-host redirect: ``` a.ru/index1.html → www.a.ru/index2.html a.ru/index1.html → b.ru/index2.html ``` ## How does Yandex process in-house redirects? {#internal-redirects} If one page (source) has a redirect to another page (target) within the same host, the robot will index the content of the target, and the search results will display the link to the target. The main page of the host is always displayed in the search results. ``` a.ru/ → a.ru/innerpage a.ru/innerpage → a.ru/ ``` ## How does Yandex process redirects for regional and language versions of the site? {#region} If regional or language versions are implemented as subdomains and a redirect is configured for redirecting visitors, the subdomains are [combined into a group](https://yandex.com/support/webmaster/en/yandex-indexing/site-addresses.md). When the robot visits the site, like the visitor, it can be redirected to one of the subdomains. Then it indexes the target page of the redirect. Thus, the site can be displayed differently in the search: **Displaying the home and internal pages**   : If the redirect is configured for internal pages, the search results display the redirect target page with its content. If the redirect is configured for the site's home page, the search results show the home page with the content of the target page. For example, the search displays the home page `https://example.com`. If the robot is redirected to the page `https://example.com/en`, the home page is displayed with the English content. If to the page `https://example.com/ru`, the home page is displayed with the Russian content. **Selecting the page version to display**   : If the site uses a redirect based on the user's IP address, the robot's IP address may differ from the region's IP address. Therefore, any of the page versions can be displayed in the search results. As a result, the page content may not match what you'd like the user to see. To display the correct content in the search: 1. Identify a robot that crawls your site, for example, by its [User-agent](https://yandex.com/support/webmaster/en/robot-workings/check-yandex-robots.md) line. 1. Check what content the robot gets. 1. Choose one of the options: - Configure the redirect so that the Yandex robot retrieves the same content. - Instead of a redirect, use the language or region switch on the site. To do this, configure the server so that both versions respond with the HTTP code 200 OK. If the sites are already grouped together, configure the server in the same way — after a while, the sites will be ungrouped. To speed up this process, [submit an ungrouping request](https://yandex.com/support/webmaster/en/yandex-indexing/address-separation.md).
{% cut "Contact support" %} When you change a site's primary or alternate addresses, it usually takes about a month for the changes to appear in search results. If you followed the instructions for [moving](https://yandex.com/support/webmaster/en/yandex-indexing/moving-site.md) or [ungrouping site addresses](https://yandex.com/support/webmaster/en/yandex-indexing/address-separation.md) but the search results haven't changed, contact support. Tell us what your question is about so we can direct you to the right specialist: {% list tabs radio %} - The primary site address was changed by mistake The primary site address may change if a redirect or the [rel="canonical" attribute](https://yandex.com/support/webmaster/en/robot-workings/canonical.md#set-canonical) pointing to the site that became the primary site address is set on the old site pages. To avoid automatic selection of the primary address, make sure that the pages on all alternate addresses redirect users to the corresponding pages on the desired primary address. - The site is presented in the search results with the wrong URL This means that the indexing bot has selected the primary site address automatically. Specify the correct site URL for the robot, following the recommendations in the [Moving a site to a new domain name](https://yandex.com/support/webmaster/en/yandex-indexing/moving-site.md) section. - The domain name of a site changed
- HTTP / HTTPS changed
- The www prefix added or removed
- The moving request isn't accepted Main reasons why sites are not grouped: - In the source code of the site that should become the primary site address contains the [attribute rel="canonical"](https://yandex.com/support/webmaster/en/robot-workings/canonical.md#set-canonical). Delete it and submit the request for moving again. - The site is unavailable or responds with a long delay. - The sites' content doesn't match. Check if the internal page URLs and headers match. - The site moves to another domain zone without a redirect. - Site indexing is prohibited in the [robots.txt](https://yandex.com/support/webmaster/en/controlling-robot/robots-txt.md) file. - [Violations of the Search rules](https://yandex.com/support/webmaster/en/service/security-threats.md#threats-web.md) are detected on the site. View the details on the [Security and violations](https://webmaster.yandex.com/site/diagnosis/threats/) page in Yandex Webmaster and fix the errors. In two weeks, check that the message about the violation disappears from Yandex Webmaster, and re-send the request. - The request was sent from the site to move to. - Internal service error. Try sending the request later. {% cut "Recommendations didn't help" %}
{% endcut %} - Ungrouping sites takes a long time
{% endlist %} {% endcut %}



You can also go to

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