What this guide will help you do
Choose a preferred URL for duplicate or near-duplicate pages without accidentally hiding useful content.
Key takeaways
- A canonical is a strong hint, not a guaranteed command.
- Keep canonicals consistent with redirects, internal links, and XML sitemaps.
- Use an absolute, indexable 200-status URL and place only one canonical in the HTML head.
What a canonical tag does
A canonical tag tells search engines which URL you prefer when several URLs contain the same or very similar content. Typical duplicates come from tracking parameters, print versions, product filters, HTTP and HTTPS variants, or the same item living in several categories.
The tag helps consolidate signals and reduces uncertainty, but search engines evaluate other evidence too. If your canonical points to one URL while the sitemap and internal links favour another, you are asking the crawler to solve a disagreement you created.
When to use self-referencing and cross-page canonicals
A self-referencing canonical is useful on an indexable page because it declares the clean version of its own URL. A cross-page canonical is appropriate when two URLs serve substantially equivalent content and only one should appear in search.
Do not canonicalise every weak page to the homepage or a vaguely related category. That is not consolidation; it is a mismatch. If an old page has permanently moved and users should never see the old URL, a 301 redirect is usually clearer.
Common canonical mistakes
Avoid canonicals that redirect, return an error, are blocked from crawling, or carry a noindex directive. Pagination and international pages also need care: each useful page generally needs its own canonical, while hreflang alternates should point to canonical URLs in their language set.
JavaScript can inject a canonical, but server-rendered markup is easier to inspect and less likely to conflict. View the rendered HTML and confirm there is exactly one tag. Then inspect a few important URLs in Search Console to see Google's selected canonical.
A clean consolidation workflow
List every accessible variant of a page and decide which URL is simplest, durable, and useful to visitors. Point internal links to it, include it in the XML sitemap, redirect obsolete variants where appropriate, and use a matching canonical on duplicates that must remain accessible.
Recheck after releases that touch routing, filters, templates, or trailing-slash rules. Canonical bugs are often sitewide, so one template error can affect thousands of pages. A small sample across every template is more valuable than checking many URLs from one section.
A practical next-step checklist
- Choose one preferred URL for each duplicate set.
- Make internal links and sitemap entries agree with it.
- Confirm the preferred page is indexable and returns 200.
- Inspect representative URLs after deployment.
When you make a technical change, test a small group of representative URLs first. Then run the free SEO audit to catch broken links, metadata gaps, crawl signals, and page-level regressions before applying the change across the whole site.
Frequently asked questions
Is a canonical tag the same as a redirect?
No. A redirect sends visitors and crawlers to another URL. A canonical lets the current URL remain accessible while identifying the preferred version for indexing.
Can every page have a self-referencing canonical?
Most indexable pages can, provided the canonical URL is the clean, final version and matches your indexing strategy.
Why did Google choose a different canonical?
Google may see stronger conflicting signals, content differences, redirects, internal links, sitemap entries, or technical problems on the declared canonical.
Primary references
Use these first-party references to confirm details that may change after this guide is published: