What Is a Canonical Tag? How rel="canonical" Works
A canonical tag — written as <link rel="canonical" href="..."> in a page's <head> — tells search engines which URL should be treated as the authoritative, master version when the same or substantially similar content is reachable through multiple URLs. Google describes canonicalization as the process of selecting the URL that best represents a group of duplicate pages, and treats the canonical tag as a strong hint rather than an absolute directive it is guaranteed to follow.
Definition
A canonical tag is an HTML element placed in the <head> of a webpage that points to the URL Google should treat as the definitive version of that content. It's commonly needed because the same content is often reachable via multiple URLs — with and without www, with tracking parameters like ?ref=, with and without trailing slashes, or via both HTTP and HTTPS. Established
Why Canonicalization Is Needed
Without a signal indicating which URL is the master copy, a search engine may split ranking signals (like backlinks) across multiple duplicate URLs instead of consolidating them onto one, and may choose a version the site owner didn't intend to be the canonical, indexed one — such as a URL with tracking parameters appended. Established
A Hint, Not a Directive
Google's documentation is explicit that the canonical tag is treated as one of several signals, not an absolute rule the system is obligated to follow. Google states it may choose a different canonical URL than the one specified if other strong signals — such as redirects, internal linking patterns, or a sitemap — point elsewhere. This is different from a 301 redirect, which does enforce a single destination. Established
Implementation Methods
| Method | How it's declared |
|---|---|
| HTML link tag | <link rel="canonical" href="https://example.com/page/"> in the page's <head> |
| HTTP header | A Link response header — useful for non-HTML files like PDFs, where a <head> tag isn't possible |
| Sitemap | Listing only the preferred URL in the XML sitemap acts as an additional (weaker) signal |
Self-Referencing Canonicals
It's standard practice for a page to include a canonical tag pointing to itself, even when there's no known duplicate. Google's own guidance recommends this as a defensive best practice, since it's common for other URLs (with parameters, session IDs, or minor variations) to be created unintentionally over time, and a self-referencing canonical helps consolidate those into the intended page from the start. Established
Common Mistakes
- Pointing the canonical tag to a page that then redirects elsewhere (a "canonical chain"), which forces search engines to follow multiple hops to determine the true destination.
- Canonicalizing to a URL that returns a non-200 status, such as a redirect or a 404, which undermines the signal entirely.
- Using canonical tags across pages with meaningfully different content, expecting Google to treat them as duplicates when they aren't similar enough to be consolidated.
- Forgetting a canonical tag on paginated or parameterized versions of a page, allowing tracking-parameter URLs to get indexed and diluting signals away from the main page.
FAQ
Is a canonical tag the same as a redirect?
No. A 301 redirect forces visitors and search engines to a single destination URL. A canonical tag is a hint that search engines may or may not follow when selecting which URL to index and rank.
Does Google always respect the canonical tag I specify?
Not always. Google treats it as one signal among several and may select a different URL as canonical if other signals — like redirects or internal linking — point elsewhere.
Should every page have a canonical tag, even without duplicates?
Yes, as a best practice. Google recommends self-referencing canonical tags to guard against unintentional duplicate URLs (like parameter variants) created later.
Related Concepts
Sources
- Google Search Central. "Consolidate Duplicate URLs." developers.google.com
- Google Search Central. "Tell Google about Canonical URLs." developers.google.com