Canonical Tags vs Redirects: Which Fix Fits Each Duplicate URL Problem?

Duplicate URLs are common on real websites. A product may be available at several addresses because of filters, tracking parameters or old site structures. A page may also load with and without a trailing slash, or through both HTTP and HTTPS.

The practical question is not simply whether two pages look alike. It is whether both URLs should remain accessible to people, or whether one address should replace the other. That distinction is the starting point for choosing a canonical tag or a redirect.

For the query canonical tag vs redirect for duplicate URLs, the short answer is: use a redirect when visitors and crawlers should be sent to one URL; use a canonical when the alternate URL needs to remain accessible but you want to indicate which version should represent the content in search.

Neither method is a universal fix. The right choice depends on user experience, site function and how consistently your site signals its preferred URLs.

What a canonical tag does—and what it does not do

A canonical tag is an HTML element in a page’s head that identifies a preferred URL for substantially duplicate or very similar content. For example, a filtered product listing might include a canonical pointing to the unfiltered category page.

Unlike a redirect, a canonical does not send visitors elsewhere. The alternate page can still load, and users can continue to interact with it. Search engines treat the tag as a signal, not an instruction that guarantees the selected URL will be used.

Google’s guidance on consolidating duplicate URLs describes canonicalisation as a way to indicate a preferred version and recommends using consistent signals. That includes linking internally to the preferred URL and including it in the sitemap.

A canonical is useful when the alternate URL serves a purpose. But it should not be treated as a way to hide a page, block crawling or prevent a URL from being accessed.

What a redirect does—and when it is the stronger choice

A redirect sends a browser or crawler from one URL to another. For a permanent change, sites commonly use a 301 or 308 redirect. Temporary redirects, such as 302 or 307, are intended for changes that are not permanent. The HTTP standard defines these redirect responses and their behaviour in its section on 3xx redirection status codes.

Use a redirect when the old URL should no longer be a separate destination. Visitors reach the replacement page automatically, and links or bookmarks to the old address can continue to work.

For example, if a business changes its domain or replaces an outdated service page with a new one, a relevant permanent redirect is usually clearer than leaving the old page live with a canonical tag. The old address is no longer needed as a separate experience.

Canonical tag vs redirect for duplicate URLs: a decision framework

Choose a redirect if the old URL should disappear

Ask whether a visitor has a good reason to use both URLs. If not, and one URL genuinely replaces the other, redirect the old URL to the best equivalent destination.

• Domain or protocol changes: redirect HTTP pages to HTTPS, or old-domain URLs to their matching pages on the new domain.
• Site restructuring: redirect an old page path to its replacement when the content has moved.
• Duplicate URL variants: if both a trailing-slash and non-trailing-slash version resolve, select one and redirect the other.
• Retired products or services: redirect only when a close replacement exists. If there is no useful substitute, a genuine 404 or 410 may be more accurate than sending visitors to an unrelated page.

Redirects should be relevant. Sending every discontinued product to the homepage may frustrate users and make it difficult for search engines to understand what happened to each page.

Choose a canonical if the alternate URL still needs to work

Use a canonical when the alternate page has a practical purpose but should not normally be the version represented in search results.

• Tracking parameters: a URL with a campaign parameter can load the same page while reporting tools attribute a visit. The page can canonicalise to its clean URL.
• Sort and filter combinations: a retailer may let shoppers sort products by price or filter by colour. Some combinations have little search value but need to stay usable for shoppers.
• Printable or alternate layouts: if a separate page format must remain accessible, it may be appropriate to canonicalise it to the main page.
• Content syndicated elsewhere: a canonical can express a preference for the original article, although the receiving site’s implementation and search engine decisions still matter.

Be careful with filters. A filtered page that meets a distinct search need—such as a meaningful category with its own inventory—may deserve its own indexable URL rather than a canonical to a broader page. Make that decision based on the page’s purpose and usefulness, not just on the fact that its URL contains a parameter.

Common duplicate URL problems, with practical examples

Campaign and tracking URLs

A marketing team shares a landing page with tracking parameters. The page content is otherwise identical to the clean URL. Keep the parameter URL available for measurement if needed, but use a canonical to the clean version. Check that your analytics setup still records campaign data as intended; a canonical does not remove parameters from the visitor’s address or replace analytics configuration.

Faceted navigation on an online shop

A shopper selects “blue” and “size medium” from a clothing category. If that filtered URL is useful for shoppers but is not intended as a separate search landing page, a canonical to the parent category may make sense. If the combination has a stable URL, distinct products and clear organic demand, assess it as a potential landing page before consolidating it.

Do not canonical every filtered URL to the homepage. The canonical target should be a relevant page with content that meaningfully represents the alternate.

Old pages after a website migration

Suppose a consultancy changes its URL structure from /services/seo-audit to /seo-audits/. If the new page replaces the old one, use a permanent redirect from the old URL to the new URL. Update internal links, sitemap entries and any other references you control so they point directly to the new address.

A canonical on the old page would leave two accessible versions and ask search engines to choose between them. That is usually unnecessary when the business has deliberately retired the old address.

Similar regional or language pages

Pages for different countries or languages are not automatically duplicates just because their templates look alike. If the text, prices, availability or service details differ for each audience, keep those pages separate and use appropriate international targeting signals where relevant. A canonical from every regional page to one global page could undermine the purpose of the local versions.

Implementation checks that prevent avoidable problems

1. Choose the destination first. Confirm which URL best serves users and accurately represents the content. Do not select a canonical target just because it is shorter.
2. Use one clear signal where possible. Avoid redirecting an alternate URL while also asking it to canonicalise somewhere else. Make the intended relationship unambiguous.
3. Check the target is accessible. A canonical should point to a working, indexable page, not a broken URL, a blocked page or another URL that redirects again.
4. Keep signals consistent. Internal links, XML sitemaps and canonical tags should generally favour the same preferred URL. Inconsistent signals can make the intended choice less clear.
5. Test what the server actually returns. Check status codes, redirect destinations and the rendered page’s canonical tag. Some sites produce different results depending on cookies, device or rendering.
6. Review important URLs after release. Check whether search engines are indexing the intended version and whether organic landing traffic or conversions change. Give systems time to recrawl; a correct implementation does not guarantee an immediate change.

If the issue is a wider set of unwanted indexed pages, start with a URL inventory and diagnose the causes before applying one blanket rule. Ryse SEO’s checklist for investigating indexed but unwanted URLs can help structure that work.

Mistakes to avoid

• Using a canonical as a redirect substitute. If a page is obsolete and should not be visited, a canonical leaves it available rather than sending people to the replacement.
• Redirecting unrelated pages. A redirect should lead to a close replacement, not simply the nearest convenient URL.
• Pointing canonical tags to non-equivalent pages. A search engine may ignore a canonical if the target does not appear to represent the alternate content.
• Creating chains or loops. Redirect directly to the final destination. A chain adds unnecessary steps; a loop can make the page inaccessible.
• Canonicalising every page in a series to page one. Paginated pages often contain different items. Treat each page according to its content and function rather than assuming all are duplicates.

A quick decision rule

Use a redirect when one URL has replaced another and the old address should send visitors to the new one. Use a canonical when both URLs need to remain accessible, but one is the preferred search version of substantially the same content.

Before implementing either, check whether the pages are genuinely duplicates, whether users need both URLs, and whether the proposed destination is a useful match. Then make the rest of the site—links, sitemap and page signals—consistent with that choice.

Frequently asked questions

Can I use a canonical tag and a redirect on the same URL?

Usually, there is no reason to do both. A redirected URL does not serve its own page content to carry a useful canonical. Set the redirect to the final URL, and make sure the destination has the intended canonical.

Does a canonical tag guarantee that Google will index my preferred URL?

No. It is a signal, not a guarantee. Search engines may select another URL if other signals or the page content suggest a different choice. Keep internal links, sitemap entries and canonical tags aligned.

Should I redirect every URL with tracking parameters?

Not necessarily. If the parameters support campaign measurement or another function, the URL may need to remain accessible. A canonical to the clean URL is often more suitable, alongside analytics configuration that preserves attribution.

Should a discontinued product page redirect to its category?

Only if that category is a useful next step for visitors and a reasonable substitute. If a direct replacement exists, redirect there. If there is no relevant destination, returning a 404 or 410 can be more honest than redirecting to a broad or unrelated page.

How can I check whether a canonical or redirect is working?

Inspect the URL’s HTTP response and, for a page that loads, its canonical tag. Then check that internal links and sitemap entries use the preferred URL, and monitor indexing and organic landing pages over time.