Canonical tag mistakes happen when the tag points Google at the wrong URL, or when the tag fights with other signals on your site. The result can be that the page you want to rank is treated as a duplicate and left out of the results. The fix is to find where the declared canonical and Google's chosen canonical disagree, then correct the cause.
What a canonical tag does
A canonical tag is a line in the head of a page: a link element with rel set to canonical and an href holding the preferred URL. It tells Google which version to keep when the same content can be reached at more than one address. That is common with tracking parameters, sort and filter options, http and https versions, and www and non www versions.
Google treats the tag as a strong hint. It also looks at redirects, internal links, the sitemap and the content itself. When those signals disagree with your tag, Google picks its own canonical.
How to tell canonicals are hurting you
Start in Search Console. The Pages report lists reasons pages are not indexed, and several point at canonicals: Alternate page with proper canonical tag, Duplicate without user selected canonical, and Duplicate, Google chose different canonical than user. Then use URL Inspection on a sample page and compare the user declared canonical with the Google selected one.
Common mistakes
Canonical tag mistakes we see
Pointing at the wrong page
Every page canonicalised to the homepage, or to a category, so Google drops them as duplicates.
Staging URLs
Canonicals left pointing at a test domain after launch, telling Google your live site is the copy.
Relative or malformed URLs
Broken paths, wrong protocol or typos that point to pages that do not exist.
Canonical to a redirect or error
The target returns a redirect, a 404 or a noindex, so the signal is useless or harmful.
Multiple canonical tags
Plugins and themes each add one, and Google may ignore both.
Conflicts with other signals
Sitemap and internal links point to one URL while the canonical points to another.
Why the same mistake keeps coming back
Canonical tags are usually written by templates, plugins or a content management system, not by hand. One setting change can rewrite thousands of tags overnight. That is why canonical problems often start on the day of a redesign, a migration or a plugin update. Our guide on traffic drops after a redesign covers how those launches go wrong.
Step by step fix
1. Crawl the site and export the canonicals
Run a crawl and export, for every URL, the declared canonical, the status code of the target and whether the page is indexable. Look first for pages whose canonical points somewhere else.
2. Check the targets
Each canonical target should return a 200 status, be indexable and be the version you actually want to rank. Remove or repair any that redirect, return errors or carry a noindex tag.
3. Make the signals agree
The canonical, the internal links, the sitemap entry and any redirects should all name the same URL. If your sitemap lists one version and your tags another, fix the one that is wrong.
4. Fix the source, not the symptoms
Find the template, plugin or setting that writes the tag and correct it there. Editing pages one by one will not hold when the next update rewrites them.
5. Request a recrawl and check
Use URL Inspection to confirm Google now reads the right canonical on key pages, and keep your sitemap current. Changes Google has not recrawled cannot count. Watch the Pages report over the following weeks.
Three canonical mistakes in detail
Canonicalising pages to a different page
A canonical tag says this page is a copy of that one. Use it between true duplicates, such as a product reached through two category paths. Do not use it to point a weaker page at a stronger one when the content is different. Google may follow the tag, and the weaker page then disappears from the results along with the queries it used to answer.
Pagination and filtered pages
Paginated lists and filtered category pages are often all canonicalised to page one or to the unfiltered category. That can hide products and articles that sit deeper in the list, because Google may never reach them. If a filtered page targets a real search, such as a size or colour people look for, it may deserve its own self referencing canonical.
Canonical tags added by JavaScript
Some sites write or change the canonical in the browser after the page loads. Google can process it, but the raw HTML and the rendered page can then disagree, and that invites conflicts. Where possible, output the canonical in the server response. Use the live test in URL Inspection to compare what Google rendered with what your source code says.
What to expect after the fix
Canonical corrections are not instant. Google has to recrawl each page, read the new tag and reprocess the duplicates it grouped together. Large sites take longer because crawling is spread across thousands of URLs. Do not expect a chart to move the day you deploy. Check the Pages report for the canonical related reasons shrinking, and check that the pages you care about are indexed and showing impressions again in the Performance report.
Canonical tags versus other fixes
A canonical tag is not the right tool for everything. A redirect is stronger when a page is gone for good. A noindex tag keeps a page out of the results entirely, and mixing it with a canonical sends mixed messages. Our guide on noindex and robots mistakes explains how those tools differ. For duplicate pages more broadly, see duplicate content fixes.
If pages are missing from Google and you are not sure why, our answer on why pages are not indexed lists the other common causes.
When to call for help
Get help when canonicals are generated by a platform you cannot easily edit, when thousands of URLs disagree with Google's choice, or when you fixed the tags and traffic did not return. Those are signs the real cause may sit elsewhere.
We check the evidence first. Our technical SEO fixes work starts with a crawl and the index coverage data, and you can ask for a free SEO triage to find out whether canonicals are the problem.
FAQ
Questions owners ask us
Is a canonical tag a command?
No. Google treats it as a strong hint, not an order. If the tag conflicts with other signals, such as redirects, internal links and the sitemap, Google can choose a different canonical URL than the one you declared.
Should every page have a canonical tag?
It is good practice for each indexable page to carry a self referencing canonical pointing at its own preferred URL. It removes doubt when the same page can be reached with tracking parameters or other variations.
How do I see which canonical Google chose?
Open the URL Inspection tool in Search Console and look at the user declared canonical and the Google selected canonical. If they differ, Google disagrees with your tag, and you need to find out why.
Get started