A canonical URL is the representative address for a group of duplicate or substantially similar pages. A website can express its preference through a canonical link, while a search engine makes its own selection using the signals available.
This distinction explains a common source of confusion. Declaring a preferred URL does not force Google to select it. The declaration needs to be consistent with the page, its content and the wider website structure.
Why can several URLs show similar content?
A website may present the same information through tracking parameters, alternative paths or other technical arrangements. Content can also be reproduced across different pages or sites.
For example, a campaign link might add tracking information to an otherwise unchanged article URL. A website migration may leave an older version available alongside its replacement.
Not every variation creates a serious problem. The useful question is which addresses need to remain accessible and how their relationship should be communicated.
What does a canonical link do?
A canonical link identifies a preferred representative URL. It can appear in the page's HTML head or, in supported circumstances, an HTTP header.
It does not move the visitor to another address. Someone can remain on the alternative URL while the canonical declaration points elsewhere.
That makes it different from a redirect. A 301 redirect sends the request to another destination and is more appropriate when an address has permanently moved.
Canonical URL versus Google's selected canonical
The declared canonical is the website's preference. Google's selected canonical is the version its systems choose to represent the group.
If those differ, investigate the context rather than assuming the tag has simply been ignored at random. The preferred page may be inaccessible, materially different or contradicted by other signals.
Check the intended destination, internal links, redirects and sitemap entries. A coherent structure gives a clearer explanation than several conflicting choices.
What is a self-referencing canonical?
A self-referencing canonical points a page to its own preferred address. It can help make the intended URL explicit when other variations are available.
For a business website, the important part is that the address is correct and stable. A template should not accidentally point every article to the same generic page.
A self-reference does not create a ranking entitlement. It is part of communicating the URL relationship, alongside the content and other technical signals.
When might canonicalisation be useful?
It is worth investigating when several accessible URLs represent the same underlying material and those alternatives need to remain available.
A campaign tracking variation is one example. Another is a technical arrangement that exposes a page through more than one route. The right solution depends on why the alternatives exist.
Avoid applying canonical links indiscriminately to distinct pages. If a comparison page and a product page answer different questions, treating one as a duplicate of the other may misrepresent their purpose.
Canonicals during a website rebuild
A rebuild can change domains, folders and page slugs. Review canonical behaviour as part of the migration plan, including both the main website and any staging environment.
Shared templates deserve particular attention. A single incorrect configuration can affect every page generated from a collection.
Test several representative pages after implementation. Check that each article points to its own intended address, rather than a preview URL, an old domain or the collection's generic path.
How do internal links and sitemaps fit in?
Links within the website should normally use the preferred destination directly. A sitemap should reflect the URLs the business wants search engines to consider.
These elements should tell a consistent story. If navigation uses one address, the sitemap lists another and the canonical link points to a third, diagnosis becomes more difficult.
Cleaning up those inconsistencies can also make the site easier to maintain. Editors and developers work more confidently when the intended destination is clear.
Common canonical mistakes
A copied template can retain a fixed canonical URL from the original page. Another error is pointing to a page that redirects again or no longer works.
A broader mistake is using canonicalisation as a substitute for deciding what the content should be. If several articles repeat the same answer, editorial consolidation may be more useful than keeping them all and adding tags.
Likewise, a canonical link should not be used as an access control. It does not make a page private or prevent people from visiting it.
How should you investigate a canonical issue?
Identify the affected URLs and compare their content. Confirm the intended representative page and why the alternatives exist. Then inspect the declarations and the supporting site structure.
Use search inspection evidence where available to compare the declared and selected versions. Record the change and allow for search engines to revisit the pages before assessing its effect.
For primary guidance, see Google's explanation of canonicalisation and how to specify a canonical URL. See technical SEO for the wider foundation.
The practical objective is a coherent relationship between accessible URLs. That supports a website whose pages have clear purposes and whose preferred addresses can be understood.
A practical example
Illustrative example: an article can be reached at its normal URL and through an email link with tracking parameters. The website identifies the normal article address as preferred and uses it in internal links. Visitors can still follow the campaign link without treating the tracking variation as a separate editorial page.
Why it matters
Canonical handling helps clarify the relationship between similar pages. It is particularly useful during template changes and migrations, where one incorrect setting can affect many URLs.
