What is the difference between a canonical tag and a redirect?

A redirect sends users and crawlers to another URL. A canonical tag leaves the current page accessible but signals that another URL is preferred for indexing and consolidation.

Technical SEO / Canonicalization / 2026

What is a canonical URL?

Q: What is a canonical URL?

A canonical URL is the representative URL selected for a set of duplicate or very similar pages. Site owners can signal a preferred version with redirects, a rel=canonical link element, consistent internal links and sitemap inclusion.

Q: Is rel=canonical a directive?

No. Google treats canonical signals as preferences and may select another URL when signals conflict or another page appears more representative.

Q: Should every indexable page have a self-referencing canonical?

A self-referencing canonical is a useful implementation pattern because it makes the preferred URL explicit, including when tracking parameters or alternate paths create copies.

One piece of content can exist at several URLs. Canonicalization helps search engines identify the version that should represent that content in the index.

Read the answer Technical SEO

Canonical URL: the short answer.

A canonical URL is the representative address selected from a group of duplicate or very similar pages. You can tell search engines which URL you prefer, but Google may select another version when technical and content signals disagree.

Article map

From concept to diagnosis.

Canonicalization becomes easier when you separate three questions: which pages are duplicates, which URL should represent them, and whether your signals consistently support that choice.

01Why canonicals exist 02How to implement 03Common mistakes 04Audit checklist

Why canonical URLs exist.

A page can become accessible through several addresses without anyone intentionally creating “duplicate content.” Tracking parameters, filters, print views, HTTP and HTTPS variants, trailing-slash differences, uppercase paths, syndication and CMS behaviour can all generate alternative URLs.

Search engines cluster pages whose primary content is duplicate or very similar, then select one representative URL. That selected page is the canonical. The process helps avoid showing multiple nearly identical results and consolidates signals around one address.

A canonical tag does not delete a duplicate page. It identifies the URL you prefer to represent a cluster.

Simple example

These addresses may show the same product:

https://example.com/shoes/black
https://example.com/shoes/black?utm_source=newsletter
https://example.com/shoes/black?sort=popular

If the clean URL is the preferred version, each duplicate can point to it.

<link rel="canonical" href="https://example.com/shoes/black">

ImportantGoogle describes canonical preferences as signals, not absolute rules. Conflicting redirects, internal links, sitemap entries, content and canonical tags can cause Google to select a different URL.

How to implement rel=canonical.

Place one canonical link element inside the document’s <head>. Use an absolute HTTPS URL and point to the page that should represent the content.

<head>
  <title>Example page</title>
  <link rel="canonical" href="https://example.com/preferred-page">
</head>

Self-referencing canonical

An indexable page can point to itself. This makes the preferred form explicit and helps when parameters or alternate paths reproduce the same content.

<link rel="canonical" href="https://www.totaldizajn.com/blog/what-is-canonical-url.html">

Canonical HTTP header

For non-HTML resources such as PDFs, a canonical can be sent through the HTTP Link header.

Link: <https://example.com/preferred-document>; rel="canonical"

Redirect, canonical tag or sitemap?

Choose the method that matches what users should experience. A permanent redirect is appropriate when the old URL should no longer remain available. A canonical tag is appropriate when alternate URLs must remain accessible. Sitemap inclusion reinforces which URLs you consider canonical, but it is a weaker signal.

Decision table

Canonical versus redirect.

Both can influence canonicalization, but they solve different product and technical problems.

Situation	Preferred approach	Why
Old URL permanently replaced	301 or 308 redirect	Users and crawlers should reach the new location.
Tracking parameter creates a duplicate	Canonical to clean URL	The parameter URL may remain accessible while the clean version represents it.
Filtered category has no independent value	Canonical or controlled crawling	Consolidate duplicate combinations while preserving useful navigation.
Two pages serve different search intent	Self-canonicalize both	Meaningfully different pages should not be collapsed.
A URL is listed only in the sitemap	Add consistent signals	Sitemap inclusion alone is weaker than redirects and canonical annotations.

International SEO

Canonical and hreflang are not rivals.

A localized page should normally canonicalize to the preferred URL in the same language. Then hreflang connects equivalent language or regional versions.

Keep local pages indexable

Do not canonicalize every translated page to the English version when each localization is intended to rank independently.

Use same-language canonicals

Each localized page should generally reference its own preferred URL in that language.

Connect equivalents

Use reciprocal hreflang annotations among pages that serve equivalent purposes in different locales.

Failure patterns

Canonical mistakes that create ambiguity.

Most canonicalization problems are signal-consistency problems. The tag says one thing while redirects, sitemaps, internal links or content say another.

Canonical points to a 404

The preferred URL should be live and accessible.

Canonical points to a redirect

Reference the final destination directly.

Canonical target is noindexed

Do not nominate a page that you simultaneously exclude from indexing.

Multiple canonical elements

Conflicting annotations can be ignored.

Relative or malformed URL

Use a complete absolute HTTPS address.

Every page points to the homepage

Unrelated content should not be collapsed into one URL.

Internal links use duplicates

Link consistently to the canonical version.

Sitemap lists non-canonicals

Keep the XML sitemap focused on preferred indexable URLs.

Localized pages canonicalize to English

Use same-language canonical URLs when local pages should rank.

Content is not actually equivalent

A canonical is not a substitute for proper redirects, pruning or information architecture.

Audit workflow

Seven checks for every important URL.

Inspect the live response, rendered HTML and Google-selected canonical—not only the source template.

Resolve the URL

Confirm status code, redirect chain and final destination.

Inspect the head

Find exactly one valid canonical annotation.

Test the target

Verify that it returns 200, is indexable and contains representative content.

Compare signals

Check redirects, internal links, sitemaps, hreflang and canonical agreement.

Crawl duplicates

Find parameters, alternate paths, protocols, hosts and trailing-slash variants.

Use URL Inspection

Compare the user-declared canonical with Google’s selected canonical.

Fix the system

Correct the template or architecture, not only one isolated page.