Establish whether the pages are duplicates

A shared template does not make two different services duplicate pages. Compare the main content, language and purpose. A tracking-parameter URL may repeat the original page, while a useful category with a different product selection may deserve its own URL.

A canonical identifies the preferred address for identical or very similar versions. Google treats it as a signal and may choose differently. The tag does not redirect visitors or resolve conflicting signals automatically.

Consistent canonical signals: Choose the preferred URL; Point canonical to it; Use it in internal links; Include it in the sitemap; Redirect duplicates if suitable
Consistent canonical signals

Distinguish four mechanisms

Both similar versions remain useful: consider a canonical pointing to the preferred page.

The material has permanently moved: use an appropriate permanent redirect, commonly 301 or 308.

A public page should stay out of search: assess a crawlable noindex directive.

The material is gone without a suitable replacement: an accurate 404 or 410 may be more appropriate than an unrelated redirect.

The page’s purpose determines the choice. Identical design is not a reason to canonicalise every service to the homepage.

Align the supporting signals

The preferred address should load successfully and be eligible for indexing. Use it in internal links and the sitemap. Check HTTPS, www, trailing-slash and parameter behaviour against the agreed configuration.

For example, if /ru/ replaces an older /ru/glavnaya/, the old path can permanently redirect to /ru/, while navigation, sitemap and hreflang use that same destination. This is an illustrative configuration, not a diagnosis of a particular site’s current state.

Keep genuine translations distinct

Substantially translated Ukrainian, Russian and English pages generally have canonical URLs in their own languages and are connected through hreflang. Pointing a translation’s canonical to another language can conflict with the goal of having that translation represented independently.

Evaluate pagination separately too. A page containing a different product set does not become a duplicate of page one merely because its heading is similar. Do not automatically canonicalise all paginated pages to the first page.

Verify the published implementation

Inspect the page source for rel=”canonical”. Check the complete address, the final page’s response and any conflicting tags emitted by the theme and SEO plugin. Compare the declared and Google-selected canonical in Search Console.

If they differ, inspect both pages and the other signals. Check the crawl date: Google’s stored view may predate your fix. A successful live test and an older index report describe different points in time.

Record what was completed

Keep the URL pair, preferred version, link changes and response checks. Monitor Google’s choice after recrawling. Related procedures are covered in the redirect guide and multilingual website guide.

Need a plan for your website?
Explore our services: SEO Services, pricing or discuss your project.