Duplicate Google chose different canonical than user is the canonical status that annoys people most, because they did the work. The tag is there, it points where it should, and Google ignored it anyway. The natural response is to check the tag again, and then again. That is usually the wrong place to look. Google read the tag fine. It weighed it against everything else it knows about the pages and decided the evidence pointed elsewhere.
What duplicate Google chose different canonical than user means
Google’s Page indexing report describes the status this way: “Google has indexed the page that we consider canonical rather than this one.” In plain terms, you marked one URL as canonical, Google picked another, and the URL in the report is not indexed.
Conductor Academy’s guide to the index coverage report puts it more bluntly: “Google found these URLs on its own and considers them duplicates. Even though you canonicalized them to your preferred URL, Google chooses to ignore that and apply a different canonical.”
That is possible because rel="canonical" is a hint, not a directive. Google treats it as one strong signal among several. When the others disagree, the tag can lose.
How it differs from the other canonical statuses
The report has three canonical statuses, and they map to a simple question: did you declare a canonical, and did Google accept it?
| Status | Google’s description | Your canonical | Google’s response |
|---|---|---|---|
| Alternate page with proper canonical tag | “This page correctly points to the canonical page, which is indexed.” | Declared | Accepted |
| Duplicate without user-selected canonical | “Google has chosen the other page as the canonical for this page.” | None | Chose for you |
| Duplicate, Google chose different canonical than user | “Google has indexed the page that we consider canonical rather than this one.” | Declared | Overridden |
If you have not declared a canonical at all, you are in the territory of duplicate without user-selected canonical, and the fix there is simply to declare one. This status is harder because declaring one was not enough. It is also different from crawled, currently not indexed: Google is not rejecting the content, it is filing it under a different address.
Why Google overrides a canonical tag
Google does not explain individual decisions, so treat the following as the usual suspects rather than a diagnosis. They share one theme: your canonical says one thing and something else on the site says another.
- Internal links point at the other URL. If your navigation, breadcrumbs or body links consistently use the non-canonical version, you are voting against your own tag.
- The sitemap lists the wrong version. A sitemap containing the URL you canonicalised away sends a mixed message.
- Redirects disagree. A redirect from your chosen canonical to the duplicate, or a chain that ends somewhere else, outweighs a tag.
- The pages are not identical enough, or are too identical. Near-duplicate product or location pages with only a word changed get grouped, and Google picks whichever it prefers.
Notice what is missing from that list: the tag being broken. A malformed canonical is possible, and worth ruling out, but a tag Google cannot parse tends to be ignored rather than overridden. When Google actively chooses a different URL, it has usually found a reason to prefer that URL. Finding that reason is the job, and it nearly always sits outside the head of the page. Start by searching your own templates and menus for links to the URL Google chose; that check alone settles a surprising number of cases.
Conductor notes the status is common on multi-language sites with similar pages. Regional versions of an English page, for example for the UK, US and Australia, can be close to word-for-word identical, and Google may fold them together whatever the canonical says. If that is your situation, the right tool is usually hreflang rather than canonicals pointing across regions; our guide to hreflang covers the setup.
How to fix duplicate Google chose different canonical than user
Start with the evidence. Open URL Inspection for an affected URL and compare the user-declared canonical with the Google-selected canonical. Then decide which of two situations you are in.
Google picked the right page. This happens more than people admit. Sometimes the tag points at a URL that is worse: thinner, newer, less linked. If Google’s choice is the better page, change your canonical to match it and move on. Fighting Google to index a weaker URL is effort spent in the wrong direction.
Google picked the wrong page. Then you have two options, and the choice depends on whether the pages should exist separately.
Be honest about that question. Teams often canonicalise near-duplicates because they want the traffic of many pages without the effort of making them distinct. Google is telling you the pages look like one page. Either accept that and consolidate, or do the work that makes them two. A canonical cannot do both jobs, and trying to make it do so is how sites end up in this status in the first place.
- Make the pages genuinely different. If both deserve to be indexed, a canonical between them was a mistake. Remove it and give each page its own content, so Google has no reason to group them.
- Align every signal with your choice. If they really are duplicates, make internal links point only to the canonical, list only the canonical in the sitemap, and redirect the duplicate if it has no reason to stay reachable. Our guide to internal linking covers auditing links site-wide.
Check the tag itself once, not ten times. It should be an absolute URL, sit in the head, and point at a page that returns 200 and is not noindexed:
Our guide to the canonical tag lists the technical mistakes worth ruling out. Once the signals line up, use Validate fix in the report.
What you cannot prove
The limitation is built into the system. Google does not say which signal tipped the decision, so you can line up links, sitemap and redirects and still not know which one mattered. Change the strongest signals first, give Google time to recrawl, and judge the result by the Google-selected canonical in URL Inspection rather than by the headline count, which moves slowly.
One more thing worth resisting: removing the canonical altogether in frustration. That moves the URLs into the no-canonical status and hands Google the whole decision.
Frequently asked questions
Why does Google ignore my canonical tag?
Because rel=canonical is a hint, not a directive. If internal links, sitemaps, redirects or the content itself point to a different URL, Google can choose that one instead.
How do I see which canonical Google chose?
Run the URL through URL Inspection in Search Console. It shows both the user-declared canonical and the Google-selected canonical.
Is this status always bad?
No. If Google’s chosen URL is the better page, update your canonical to match it. It is only a problem when Google indexes a version you do not want shown.
Does this happen on multi-language sites?
Often. Regional versions of the same page can be near-identical, so Google may group them. Hreflang is the usual fix rather than cross-region canonicals.
The takeaway Your canonical tag is one vote. Check what Google chose, accept it if it is better, and otherwise make your links, sitemap and redirects vote the same way.
