🎯
Every Page Needs a Canonical
Even if a page has no duplicate, a self-referencing canonical is best practice. It explicitly signals to Google which URL is the preferred version, preventing confusion from URL parameters or tracking links.
⚠️
Canonicals Don't Block Crawling
A canonical tag is a hint, not a directive. Google may still crawl non-canonical versions. To fully prevent crawling, combine canonicals with robots.txt disallow or noindex meta tags.
🔗
Use Absolute URLs in Canonicals
Always use fully qualified absolute URLs in canonical tags (https://example.com/page), never relative paths (/page). Relative canonicals can be misinterpreted differently across crawlers.
🌐
Canonical vs. Hreflang
For multilingual sites, use hreflang tags alongside canonicals — not instead of them. Each language version should self-reference its own canonical while hreflang signals the relationship between versions.
🔄
HTTP Header Canonicals Too
Canonical signals can also be sent via Link HTTP response headers (Link: <url>; rel="canonical"). This works for PDFs and non-HTML files that can't contain a <head> tag.
📊
Canonicals Consolidate Link Equity
When multiple URLs have similar content, a canonical points all the link equity to the preferred URL. This strengthens that page's authority rather than diluting it across duplicates.