Blog
Canonical URL: meaning and when to use it
A canonical URL represents a group of duplicate or very similar pages. You can express a preference through rel="canonical", redirects and consistent signals such as sitemap entries. Google evaluates those signals and may select a different URL. A canonical tag expresses a preference; it leaves the visitor on the address they opened.
Example: one product, two addresses
Suppose a store uses the illustrative host https://www.example.com and sells a mug at /mugs/blue/. An Instagram campaign links to that path with the parameter utm_source=instagram after the ? separator. Both URLs display exactly the same product. The parameter identifies the visit’s source and does not, by itself, create a separate offer.
In this fictional example, both versions can identify the clean product URL as their representative:
<link rel="canonical"
href="https://www.example.com/mugs/blue/" />
Place the declaration in the HTML head. Internal links and sitemap entries should agree with the choice. This example describes a relationship between duplicates; it is not an instruction to strip every parameter from a site. A parameter that meaningfully changes content or functionality needs a separate assessment.
Google explains the methods for specifying a canonical URL. On a real store, inspect both the template’s declaration and the page the server actually delivers.
Canonical tag or redirect?
First decide whether visitors still need both addresses to work. When an old address has been replaced by an equivalent destination, a permanent redirect can take people to the current page. When both addresses need to remain accessible and contain the same material, a canonical declaration expresses the preference without moving visitors.
| Hypothetical situation | Decision to consider |
|---|---|
| Same product with a campaign parameter | Preserve the visit and identify the clean product URL as canonical |
| Article moved to a new path | Redirect the retired path to its replacement |
| Products with different useful characteristics | Keep separate pages when their differences warrant them |
| Full translation in another language | Connect language versions; avoid automatically consolidating into the original |
Pointing every canonical tag at the homepage does not solve duplication. A homepage that does not represent the product creates an inconsistent signal. Likewise, noindex is not a general substitute for canonicalization: excluding content from the index and choosing its representative are different decisions.
When Google selects another URL
Inspect the exact address in Search Console and compare the declared canonical with Google’s selected canonical. Open both pages. Does the selected one contain equivalent material? Does the preferred URL redirect, fail or carry noindex? Do internal links and sitemap entries consistently point to it?
A CMS template can emit the wrong declaration across many pages. Examine several affected pages before fixing the template, then inspect the published HTML. Index inspection reports reflect previous processing. A current test helps establish today’s state without proving that Google has already changed its selection.
Record the actual relationship: which variants represent which content, and which address you want to maintain. That decision also informs your sitemap and helps future internal links avoid unnecessary variants.
Plan your next post in HeyMark.
Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.