Quick answer

Inventory the URL variants, decide which page should represent the intent, then align canonical tags, redirects where appropriate, internal links and sitemap entries. Do not use a canonical tag as a substitute for fixing a broken navigation or redirect rule.

A canonical is a signal, not an absolute command. Search engines may choose another URL when other signals conflict or when the selected canonical does not appear to be the best representative page.

What I would check first

Look for query-string variants, duplicate paths, inconsistent protocol or hostname, pagination, filters and pages that differ only by tracking parameters. Compare the content and purpose before deciding that two URLs are duplicates.

Inspect the rendered canonical, response code, internal links and sitemap entry. If the page is redirected, blocked or points to a different destination, the signals may be inconsistent.

Decision framework

Use a redirect when the old URL should no longer be a separate destination and a relevant replacement exists. Use a canonical when multiple accessible variants need to remain available but one should represent the group in search.

Keep genuinely distinct pages separate when they satisfy different user needs. Similar keywords alone do not prove that pages should be merged; intent and the actual content matter.

Implementation steps

Create a URL rules document, test representative variants and crawl the site after changes. Update internal links to point directly to preferred URLs and keep the XML sitemap focused on canonical, indexable destinations.

Google's duplicate-URL guidance recommends consistent signals to help identify a preferred URL. Monitor Search Console and server behaviour after changes, especially where templates generate many URL variants.

Common mistakes

Do not canonicalize every page to the homepage, use canonicals to hide unrelated duplicate content or leave internal links pointing to a redirected variant.

Avoid making broad canonical changes without a URL inventory. A small template mistake can affect many pages and may be harder to diagnose after deployment.

Measurement and business implications

Track the number of unintended variants, canonical consistency, crawl errors and search performance for priority URLs. Verify that valuable pages remain discoverable and that the preferred destination answers the intended query.

Use the migration QA and Search Console diagnosis guides to separate duplicate-URL issues from content or demand changes.