Canonical, sitemap, hreflang, and redirects solve different problems, but they all affect URL identity. When they point to different addresses, the search engine has to interpret the site’s intent on its own. The result may be a canonical version selected by the system, a language page dropping out of a group, or a URL being crawled even though it redirects.
Assign one primary entity
First, answer this question: which URL should users access and which should appear in search as the primary version of this content? Once you have made that decision, you can update the markup. The choice should be based on the current protocol and domain, a stable path, the language, the business entity, and whether the address can be maintained in the future.
Create a table for the affected group: requested URL, final address, status code, canonical, sitemap, hreflang, language, indexability, and incoming links. Don’t group pages just because their paths look similar. /ru/product and /en/product represent different language versions; a URL with sorting and a clean category page may be duplicates; an article’s old and new addresses may be stages in a migration.
Write down the decision in a plain sentence: “the primary Russian product page is A, the English page is B, and the old address C has permanently moved to A.” Technical signals follow from this statement, so teams can work from one consistent plan.
Understand the role of each signal
A permanent server-side redirect indicates that the source URL is no longer the final resource. rel="canonical" indicates the preferred version of an identical or very similar document. A sitemap lists URLs that the site owner wants to appear in search. Hreflang links independent localized versions of the same page.
Google considers redirects and canonical to be strong canonicalization signals, and inclusion in a sitemap to be a weaker one. The system still makes the final choice. In its official guide to canonical URLs Google specifically recommends not indicating different URLs through different methods and choosing a canonical in the same language for hreflang.
The practical rule follows: a sitemap should not contain a URL that permanently redirects or is canonicalized to another URL. Hreflang should not point to a non-canonical, blocked, or redirected page. Canonical does not replace language connections.
Find the source of the conflict
Start with the source HTML, then compare it with the DOM. Canonical can be added simultaneously by a template, an SEO plugin, and an HTTP header. Hreflang is often generated by a localization module, while a different plugin builds the sitemap from the database. Redirects may be configured in the CMS, server configuration, CDN, or middleware. Each layer may use its own normalization rules.
Group conflicts by template. If all URLs with a trailing slash are canonicalized without one, but the server redirects them back, the problem is in global normalization. If only translated product pages point their canonical to the Russian original, check the localization template. If the sitemap contains old addresses after a migration, the generator is using an outdated field.
Compare the public response with the origin, if available. A CDN may retain an old canonical or redirect after the application has been updated. Don’t clear the entire cache automatically: first identify the affected keys and scope.
Align canonical, redirects, and the sitemap
Page A should not redirect to B while also managing to declare C as its canonical: search engines generally don’t use the HTML of the source address as the final document. Check the destination B. If that is the chosen primary version, B returns 200 and has a self-canonical pointing to B; internal links and the sitemap also point to B.
Shorten the A → B → C chain to a direct A → C redirect when C is the final version. Make sure there is no loop between normalization rules: HTTPS to HTTP, www to non-www, trailing slash to no slash, and back again. Practical checking methods are covered in the article on redirects.
If A should remain an independent page, remove the redirect and return meaningful 200. A URL cannot be both an accessible page and an address that has been permanently moved.
Clean the sitemap down to canonical URLs
Include absolute final addresses in the sitemap that return 200, are allowed to be indexed, and are selected as primary. Google treats sitemap URLs as suggested canonical URLs and recommends listing only the versions the site owner wants to show in search; this is stated in the documentation on creating sitemaps.
After changing the domain, protocol, or path structure, update the generator and all XML files it creates. Check the sitemap index, child sitemaps, links in robots.txt, and submitted versions in search consoles. Remove redirects, 404, and parameter-based duplicates.
The date lastmod should reflect a significant change to the page. Substituting the time of every sitemap build creates meaningless constant updates and makes crawl activity harder to interpret. Other common issues are covered in the article on sitemap errors.
Build a valid hreflang cluster
Each language page should have its own canonical in that locale, if it is an independent version, and use hreflang to link to its available canonical equivalents. The links must be reciprocal: if the Russian page points to the English page, the English page confirms the Russian one. Target addresses return 200, are not blocked, and do not redirect.
A Russian page canonicalized to an English page usually removes the Russian page from the independent group: one signal says “this is a duplicate of the English page,” while another says “this is its language alternative.” If the localization is too limited and is genuinely considered a duplicate, first make a substantive decision about whether it should exist. Hreflang does not fix a missing translation.
Check the language and region codes, x-default, protocol, domain, and trailing slashes. Isolated errors and ways to check them at scale are described in the article on common hreflang errors.
Roll out the change using a mapping table
For a migration, prepare an explicit “old URL → new URL” table. Redirects, canonical, sitemap, hreflang, and internal links should be generated from or checked against it. When each layer is managed manually by different people, discrepancies are almost inevitable.
Before release, test representative groups: the primary page, old address, language versions, URLs with parameters, pagination, and HTTP/www/trailing-slash variants. After release, repeat the requests to the public domain, including with a mobile user agent. Compare the source HTML and headers, clearing only cache objects confirmed to be outdated.
The full reChecker site audit collects available URLs and shows canonical, hreflang, sitemap, and redirects in a technical report. Use it after approving the mapping table to find pages where one of the signals is still outdated.
Define the consistency criteria
For a regular indexable page, the final address returns 200, has a self-canonical, is included in the sitemap, and receives internal links without a redirect. For a language version, add reciprocal hreflang links to the canonical addresses in the corresponding locales. The old URL redirects directly to the selected new address and is absent from the sitemap.
Run the criteria against each group in the matrix and save the results alongside the mapping table. The canonical selected in the console may update later than the technical deployment: it takes time for the search engine to recrawl the site. At the next check, the matrix will show which conflict remains on the site and where the update has not yet reached the search index.