What is a canonical URL?
A canonical URL is the primary address representing identical or very similar content. A website can suggest its preferred version, but Google makes its own selection using multiple signals.
Also known as: canonical URL · canonical tag · rel="canonical"
At a glance
- The website’s declared canonical and Google’s selected canonical can differ.
- A canonical annotation does not redirect the visitor.
- Distinct pages should not be labeled as duplicates merely because they share a broad topic.
On this page

Why can one piece of content have several URLs?
A guide might be available at a clean URL, a campaign-parameter version and a print-friendly address. The visitor receives similar content while the search engine encounters several URLs. Canonicalization addresses that situation by selecting a representative.
Several URLs do not automatically mean spam. However, similar presentation does not make distinct explanations duplicates. “Adjusting a bicycle brake” and “Cleaning a bicycle chain” answer different questions even when they share a website template.
What does rel="canonical" mean?
The canonical link relation identifies a preferred address for duplicate content. A simple illustrative HTML annotation is:
<link rel="canonical" href="https://example.com/guides/window-measurement">
Google recommends a complete, absolute URL. The preferred page can identify its own address; this is commonly called a self-referencing canonical.
Do not copy the same example address into every page. Each independent piece of content needs its appropriate representative. A hard-coded canonical left in a shared template can send incorrect signals across many otherwise distinct pages.
Why might Google choose another URL?
The declared annotation is one signal among those Google considers. The search engine distinguishes the user-declared canonical from the Google-selected canonical and can choose differently.
A canonical also does not make substantially different pages identical. Pointing one distinct service page at another is not a sound way to “transfer its strength.” First establish whether the content really belongs to one duplicate group.
Canonical, redirect or noindex?
| Mechanism | Purpose | What happens to the visitor |
|---|---|---|
| Canonical | Suggest a primary content version. | The opened page stays in the browser. |
| Redirect | Send the request to another URL. | The destination loads. |
| Noindex | Exclude a page from the search index. | The page can remain accessible. |
A permanent redirect suits an actual permanent move. A canonical does not perform that navigation. Noindex asks for exclusion rather than naming a preferred duplicate.
An example: a campaign link
Imagine a blinds company emailing its window-measurement guide. The email link includes tracking parameters, but the content matches the ordinary address.
Choosing the parameter-free URL as the representative is understandable. Visitors can still read the campaign version while the site consistently identifies one lasting address for the guide.
A separate page explaining the different measurement problems of roof windows should not automatically be forced into the same group. Similar vocabulary is not the same as duplicate main content.
What should you verify?
Inspect the canonical actually served, then open its destination. Does it contain the appropriate content? Is it working and indexable? Do internal links consistently use the intended address?
Check several page types and parameter variants, not just the home page. A correct annotation demonstrates the signal your site sends; it does not prove Google’s selection. Verify the actual indexing result separately. For genuine language or regional equivalents, hreflang describes an additional relationship with a different purpose.