Canonicalisation For SEO: What Is a Canonical URL and When Should You Use One?

Overview
Canonicalisation is the process of telling search engines which URL should be treated as the main version when the same or very similar content can be reached through more than one URL. A canonical tag helps consolidate those duplicate versions around one preferred URL, reducing confusion over which page should appear in search results.

 

Duplicate URLs are more common than they first appear. A product might be accessible through several filtered category URLs, a page might contain tracking parameters, or the same content may exist on both an original website and another authorised domain.

Canonicalisation helps search engines understand which version you would prefer them to use.

 

What is a canonical URL?

A canonical URL is the main URL chosen to represent a page or group of duplicate or near-duplicate pages.

For example, the same product could potentially be reached through:

https://example.com/products/blue-chair/

https://example.com/products/blue-chair/?utm_source=email

https://example.com/chairs/blue-chair/

If all three URLs contain essentially the same product information, you may want search engines to treat:

https://example.com/products/blue-chair/

as the canonical version.

The alternative URLs can then point towards it using a canonical tag.

Google also makes its own assessment of which URL is most representative. The canonical you specify is an important signal, but Google may choose another URL if other technical signals suggest a different version is more appropriate.

 

Why does canonicalisation matter for SEO?

Canonicalisation becomes useful when several URLs show the same or substantially similar content.

Without clear signals, search engines may have to decide which version to show themselves. That can create practical problems.

Links may point towards several versions of the same page. Internal links may also be divided between different URLs, while reporting becomes harder because impressions and clicks can appear against different versions.

Search engines also need to spend time discovering and revisiting those duplicate URLs.

A clear canonical setup helps indicate which URL should carry the main search signals and which version you would normally expect to see in organic results.

Duplicate content itself is not automatically a Google spam violation. The main issue is helping search engines understand how different URLs relate to one another.

 

When might you need a canonical tag?

Canonical tags are commonly useful when the same or almost identical content can be accessed using different URLs.

Typical examples include:

• tracking parameters added to URLs
• sorting and filtering options
• ecommerce product variations
• print-friendly versions of pages
• session IDs
• duplicate category routes
• syndicated content
• equivalent content published across separate domains.

A URL such as:

https://example.com/shoes/?sort=price

may show essentially the same products as:

https://example.com/shoes/

If the sorting URL does not need to rank separately, pointing it towards the main category page may help make your preferred version clearer.

Canonicals should not be used simply because two pages discuss a similar subject. If the pages serve different purposes and contain meaningfully different content, they may deserve to be indexed separately.

 

How do you add a canonical tag?

For an HTML page, a canonical tag normally sits inside the <head> section.

For example:

<link rel=”canonical” href=”https://www.example.com/products/blue-chair/” />

If this tag appears on:

https://www.example.com/products/blue-chair/?colour=navy

it indicates that:

https://www.example.com/products/blue-chair/

is your preferred canonical URL.

Use the full absolute URL, including https:// and the correct hostname.

The canonical should also point to a working, indexable page rather than a URL that redirects, returns an error or is blocked from search engines.

 

What is a self-referencing canonical?

A self-referencing canonical is a canonical tag on a page that points back to that page’s own URL.

For example, the canonical page:

https://www.example.com/services/seo/

could contain:

<link rel=”canonical” href=”https://www.example.com/services/seo/” />

This may look unnecessary because the page is already on the preferred URL, but it helps make your intention explicit.

It can also protect against unwanted URL variations being created through parameters or other site behaviour.

Google recommends including a canonical link on the canonical page itself.

For most indexable pages on a conventional website, self-referencing canonicals are a sensible default.

 

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

A canonical tag and a 301 redirect can both indicate a preferred URL, but they have very different effects on visitors.

A 301 redirect sends the user and search engine from the old URL to a new one.

A canonical tag leaves both URLs accessible, while telling search engines which version you prefer for indexing.

Imagine you have:

https://example.com/old-seo-guide/

and:

https://example.com/seo-guide/

If the old page has permanently moved and there is no reason for anyone to continue visiting the old URL, a 301 redirect is normally more appropriate.

Anyone visiting the old address is automatically sent to the new one.

Google describes redirects as a strong canonicalisation signal and recommends them when duplicate URLs are being retired permanently.

A canonical tag is more useful when both URLs genuinely need to remain accessible.

For example, an ecommerce site may need a filtered product URL for shoppers even though the main category page should remain the preferred version for search.

A good practical question is:

Should users still be able to visit both URLs?

If the answer is no, consider a permanent redirect.

If the answer is yes and the content is substantially duplicated, a canonical may be more suitable.

 

What is the difference between canonical and noindex?

Canonical and noindex solve different problems.

A canonical says:

“This page is similar to another page, and this is the version I would prefer you to treat as the main one.”

A noindex directive says:

“Do not include this page in search results.”

Those are different instructions.

If you have duplicate pages and want their signals consolidated around one preferred URL, a canonical is usually the more appropriate tool.

Google specifically advises against using noindex simply to influence which page becomes canonical within a site.

For example, if:

/seo-services/

and:

/seo-services/?source=menu

contain the same content, canonicalising the parameter URL to /seo-services/ makes sense.

Using noindex on the parameter version may remove it from search, but it does not communicate the same relationship between the two URLs.

Noindex is more appropriate where a page itself should not appear in search results, such as certain utility or internal-use pages.

 

Can canonical tags work across different domains?

Yes. A canonical can point from a page on one domain to an equivalent page on another domain.

This is often described as a cross-domain canonical.

For example, a business might publish an original research article on its own website and then allow an industry publication to republish the same article.

The republished version could contain:

<link rel=”canonical” href=”https://www.originalsite.co.uk/research/report/” />

This indicates that the original URL is the preferred version.

Cross-domain canonicals can therefore be useful for syndicated or legitimately republished content.

They should be used carefully.

If you control both sites and have permanently moved all content from one domain to another, a 301 redirect is usually clearer because visitors should also be moved to the new location. Google recommends redirects when moving equivalent content between domains.

Cross-domain canonicals make more sense when both pages need to remain live.

 

What is the common WordPress pagination canonical mistake?

Pagination is an area where canonical tags are often implemented incorrectly.

Imagine a blog category has:

/blog/

/blog/page/2/

/blog/page/3/

A common mistake is making page 2 and page 3 canonicalise back to /blog/.

This can send the wrong message because those paginated pages do not contain exactly the same content.

Page 2 may contain older articles that do not appear on page 1 at all.

Each useful paginated page should generally have its own self-referencing canonical:

<link rel=”canonical” href=”https://www.example.com/blog/page/2/” />

for page 2, and:

<link rel=”canonical” href=”https://www.example.com/blog/page/3/” />

for page 3.

This helps search engines treat each pagination URL as a legitimate page in the sequence.

The mistake often appears after a WordPress theme change, SEO plugin adjustment or custom template implementation.

It is worth checking category, archive and ecommerce pagination during a technical SEO audit rather than assuming a plugin has handled it correctly.

 

Should product variations use canonical tags?

Sometimes. Suppose a retailer sells the same trainer in five colours.

If each colour URL contains almost identical content and there is little value in having each version rank independently, pointing the variants towards a main product URL may make sense.

However, if each variation has meaningful differences and customers actively search for those specific variations, separate indexable pages may be useful.

Google also supports distinct product variant URLs in ecommerce setups, so automatically canonicalising every variation to the parent product can remove useful search opportunities in some cases.

The decision should be based on what the URLs actually represent rather than applying one rule across every product.

 

Can Google ignore a canonical tag?

Yes. Google treats canonical declarations as signals rather than absolute instructions.

It may choose a different URL if your canonical conflicts with other evidence.

For example, imagine a page contains:

<link rel=”canonical” href=”https://example.com/page-a/” />

but:

• all internal links point to /page-b/
• the XML sitemap lists /page-b/
• /page-a/ redirects somewhere else
• backlinks primarily point at /page-b/.

Those signals are inconsistent.

Google may decide that /page-b/ is the more appropriate canonical.

Google Search Console’s URL Inspection tool can show both the user-declared canonical and Google-selected canonical, making it useful when diagnosing these problems.

 

How can you make canonical signals clearer?

Consistency matters. Where possible:

• link internally to the canonical URL
• include canonical URLs in the XML sitemap
• use HTTPS versions consistently
• avoid canonicalising to redirecting URLs
• avoid canonical chains
• use self-referencing canonicals
• make sure canonical pages return a normal 200 response
• avoid conflicting noindex, redirect and canonical instructions.

Google treats redirects and rel=”canonical” as strong signals, while inclusion in an XML sitemap is a weaker canonicalisation signal. Combining consistent signals can make your preferred URL clearer.

 

What is a canonical chain?

A canonical chain occurs when one URL points canonically to another URL, which then points to a third. For example:

Page A → canonical to Page B → canonical to Page C

If Page C is the genuine preferred version, Page A should ideally point directly to Page C.

Direct canonical references reduce ambiguity and make the setup easier to maintain.

The same principle applies if a canonical URL redirects. It is usually cleaner to point straight to the final live URL.

 

How can you check canonical tags?

Start by viewing the page source and looking for:

rel=”canonical”

You can then confirm that the URL is correct and matches the page you expect search engines to treat as canonical.

For individual pages, Google Search Console’s URL Inspection tool is particularly useful.

It can show:

• your declared canonical
• Google’s selected canonical
• whether the URL is indexed
• whether Google has discovered an alternative version.

For larger websites, a technical crawler can identify:

• missing canonicals
• multiple canonical tags
• canonicals pointing to redirects
• non-indexable canonical targets
• canonical chains
• paginated pages pointing to page one
• pages whose canonical does not match their preferred URL.

These checks are particularly valuable after a migration, redesign or CMS change.

 

When should canonicalisation be reviewed?

Canonicalisation should be checked whenever the way URLs are generated changes. That commonly includes:

• website migrations
• HTTP to HTTPS moves
• changes between www and non-www
• WordPress theme changes
• ecommerce filter changes
• category restructuring
• domain migrations
• new tracking parameters
• international site launches.

A canonical problem is often difficult to spot visually because the page can appear to work perfectly for users.

The issue becomes visible when Search Console reports unexpected Google-selected canonicals, pages disappear from search, or the wrong URL starts ranking.

Canonicalisation is therefore a small technical detail within SEO with a potentially wide effect. When each page sends clear and consistent signals about its preferred URL, search engines have a much easier job deciding which version should represent the content.