A canonical URL tells search engines which version of a page is the real one
When the same or near-identical content is reachable at more than one address, a canonical tag names the version search engines should treat as authoritative for indexing and ranking. It consolidates duplicate pages into one signal instead of several that compete with each other.
Definition
A canonical URL is the single version of a page that a site nominates as authoritative when the same content exists at more than one address, declared using a rel="canonical" link tag in the page's head, or an equivalent HTTP header. Search engines treat it as a strong signal, not a command: they weigh it alongside redirects, internal linking, and sitemap inclusion before deciding which URL to actually index and rank.
Why the same page ends up at more than one URL
Duplication is rarely deliberate. A trailing slash, a www versus non-www address, an http versus https version, a tracking parameter appended by an ad platform, or a sort and filter combination on a product listing can each generate a technically distinct URL serving identical or near-identical content.
Content management systems make this worse by default: many auto-generate print versions, paginated duplicates, and session-specific parameters without being asked to. None of this is a mistake on the page itself. It is a byproduct of how dynamic sites work, and canonical tags exist specifically to correct for it.
What the canonical tag actually does
Placed as <link rel="canonical" href="..."> in a page's head, the tag points at the preferred URL for that content. Every duplicate variant carries the same tag, pointing at the same preferred address, including the preferred page itself pointing at its own URL, a practice called self-canonicalisation.
The effect is consolidation. Instead of ranking signals, links, relevance, engagement, being split thin across several near-identical URLs, they collect on the one address the tag names, which is generally a stronger position than any of the duplicates could reach alone.
A canonical tag turns several competing versions of a page into one address worth ranking.
A signal, not a rule
Google's own documentation is direct about this: rel="canonical" is one input into a broader decision, alongside redirects and how a site links to itself internally, and the version it ultimately shows in search results can differ from the one a site's tags requested. A canonical tag that contradicts strong signals elsewhere on the site, a redirect pointing somewhere else, internal links overwhelmingly favouring a different URL, tends to lose.
The practical takeaway is consistency. A canonical tag works best when every other signal on the site agrees with it: internal links point at the same URL it names, the sitemap lists that URL, and nothing redirects away from it. See crawlability vs indexability for how this fits into indexing decisions more broadly.
What a canonical tag does not do
It is not an access control. A duplicate URL carrying a canonical tag pointing elsewhere is still fetched and read by crawlers individually; the tag only affects which version gets indexed and ranked, not whether the others get reached in the first place. Blocking a page from being crawled at all is a separate mechanism, robots.txt or a noindex tag, and confusing the two is a common setup mistake.
It is also not a redirect. Every duplicate URL a canonical tag points away from stays live and directly visitable; nothing forces a visitor or a crawler from one to the other. That is a deliberate difference: canonical tags exist for content that legitimately needs to exist at more than one address, not for pages that should simply stop existing.
Common questions
What is a canonical URL in plain terms?
It is the one version of a page a site nominates as the real one, when the same or near-identical content is reachable at more than one address. It's set with a rel="canonical" link tag pointing from every duplicate at the preferred URL.
Is a canonical tag the same as a redirect?
No. A redirect sends both users and crawlers from one URL to another; the old URL stops existing as a separate, visitable page. A canonical tag leaves every version live and visitable, and only tells search engines which one to treat as authoritative for indexing and ranking.
Do I need a canonical tag if a page only exists at one URL?
It's still good practice to add a self-referencing canonical, a tag on a page pointing at its own URL. It costs nothing and removes any ambiguity if a duplicate or parameterised version of that URL ever gets created later, by a CMS, a tracking script, or a sharing link.
Can a canonical tag point to a page on a different domain?
Yes. Cross-domain canonicals are a standard, supported use case, most often for syndicated content: a business republishing an article elsewhere can canonical it back to the original, so the original keeps the ranking credit rather than competing against its own syndication.
Does Google always follow the canonical tag a site sets?
No, and this is the detail most guides skip. Google treats rel="canonical" as a strong signal, not an instruction, and weighs it alongside redirects, internal linking patterns, and sitemap inclusion before deciding which URL to actually show. A canonical tag can be overridden when other signals disagree with it strongly enough.
AI-readable websites
The structural discipline canonical tags are one part of.
Crawlability vs indexability
The broader distinction canonical tags help resolve.
What is structured data
The markup format that sits alongside a page's canonical tag in its head.
What is semantic HTML
The underlying document a canonical tag is pointing search engines toward.
See whether your site's duplicate pages are competing with each other or consolidated.