What Does "Duplicate, Google Chose Different Canonical Than User" Mean?

What "Duplicate, Google chose different canonical than user" means

The status sits in the "Not indexed" group of the Page indexing report. Google's description is two sentences: "This page is marked as canonical for a set of pages, but Google thinks another URL makes a better canonical," and Google has indexed the page it considers canonical rather than this one. ^{[1]Google Search Console Help. Page indexing report} In Google's reading, the inspected page is a duplicate of the Google-selected canonical, not of the canonical you declared. ^{[1]Google Search Console Help. Page indexing report}

The status exists because of how canonicalization works. When Google finds multiple pages whose primary content is the same or very similar, it clusters them and marks as canonical the one that its signals suggest is the most complete and useful for search users. ^{[2]Google Search Central. What is canonicalization} The factors include whether the page is served over HTTP or HTTPS, redirects, the presence of the URL in a sitemap, and rel="canonical" link annotations. ^{[2]Google Search Central. What is canonicalization} You can state a preference with these techniques, but indicating a canonical preference is a hint, not a rule, and Google may choose a different page than you do. ^{[2]Google Search Central. What is canonicalization} Google's troubleshooting page names two kinds of reasons: the quality of the content and technical signals. ^{[6]Google Search Central. Fix canonicalization issues}

The status is one of three canonical outcomes in the report. Its siblings are Duplicate without user-selected canonical, where nothing was declared, and Alternate page with proper canonical tag, where Google accepted the declaration.

When to fix it and when to leave it

Google's introduction to the "Not indexed" group says these pages have not been indexed, but not necessarily because of an error, and that having a page marked duplicate or alternate is usually a good thing, because it means Google found the canonical page and indexed it. ^{[1]Google Search Console Help. Page indexing report} The content is in the index. The open question is which URL carries it.

The last row follows from one line in Google's help text: a duplicate page must be similar to the canonical. ^{[1]Google Search Console Help. Page indexing report} A canonical that points to a page with different content is not a weaker hint; it is one Google does not act on.

Language versions are a frequent cause of the third row. Different language versions of a page count as duplicates only if the primary content is in the same language, so a "translated" page where only the header and footer changed is treated as a duplicate of the original. ^{[2]Google Search Central. What is canonicalization}

The status is also a neighbor of keyword cannibalization. When two URLs are similar enough, Google folds one into the other and you see a duplicate status. When they are similar but not similar enough, both stay indexed and compete for the same queries, which is the internal cannibalization pattern. A canonical tag cannot settle the second case, because the pages are not duplicates; that is a merge or redirect decision.

Example: one guide, four URLs

The table below is constructed to illustrate the pattern. Each row is a URL as it appears in the Page indexing report and the URL Inspection tool, with 28 days of clicks from the Performance report.

Row three is an old blog copy of the guide that still declares itself canonical. Google disagreed, and it chose the URL you would have picked. The fix is housekeeping: redirect the old copy, or point its canonical at /guides/trail-shoes.

Row four is the one that costs something. The German URL has a translated navigation and an English body, so Google treats it as a duplicate of the English guide and German searchers are served the English URL. A canonical tag does not fix this; translating the primary content does.

The zero clicks on rows two to four are not lost traffic. Click, impression and position data for all variations of a page are assigned to the canonical URL that Google selects, so the 860 clicks on row one include the visits that the variants would have earned. ^{[5]Google Search Console Help. What are impressions, position, and clicks?}

How to check it and fix it

1. Open the Page indexing report, click the status under "Why pages aren't indexed", and export the example URLs.
2. Inspect a URL and read two fields under "Page indexing". "User-declared canonical" shows the canonical the page explicitly declares, and "Google-selected canonical" shows the page Google selected as the authoritative URL when it found similar pages on your site. ^{[4]Google Search Console Help. URL Inspection tool}
3. Open the inspected page, the user-declared canonical and the Google-selected canonical in a browser and compare them. ^{[1]Google Search Console Help. Page indexing report}
4. Decide which URL should rank, using the table above.
5. Make the signals agree. Do not specify different URLs as canonical for the same page with different techniques, link internally to the canonical URL rather than a duplicate, keep a self-referential rel="canonical" on the canonical page, and remember that every URL in a sitemap is suggested as a canonical. ^{[3]Google Search Central. How to specify a canonical URL with rel="canonical" and other methods} A redirect and a rel="canonical" annotation are both strong signals, sitemap inclusion is a weak one, and the methods become more effective when combined. ^{[3]Google Search Central. How to specify a canonical URL with rel="canonical" and other methods}
6. Do not use robots.txt for canonicalization, and do not use noindex to prevent the selection of a canonical within one site, because it blocks the page from Search completely. ^{[3]Google Search Central. How to specify a canonical URL with rel="canonical" and other methods}
7. Re-inspect after the next crawl and read the indexed result, not the live test.

The full diagnosis, signal by signal, is in why Google chooses different canonical URLs. To run the comparison across many URLs at once, the Google Index Checker inspects them through the URL Inspection API and compares the canonical you declare with the one Google chose.

The thing people get wrong

"Google ignored my canonical tag, so the tag must be broken." Usually the tag is read correctly and outvoted. Google's documentation calls a canonical preference a hint, not a rule, and URL Inspection says there is no guarantee that Google will choose your preferred canonical, only that it will take it into consideration. ^{[2]Google Search Central. What is canonicalization [4]Google Search Console Help. URL Inspection tool} Re-adding the same tag changes nothing. What changes the outcome is removing the signals that contradict it, or accepting that Google's choice was the better one.

Duplicate, Google chose different canonical than user vs the other canonical statuses

A keyword map that assigns one URL to each topic is the simplest way to keep new duplicates out of all three rows.

Where the report can mislead

The example list under the status does not necessarily show all URLs with the issue and is limited to 1,000 rows, so a falling count is a trend, not a complete inventory. ^{[1]Google Search Console Help. Page indexing report} The Google-selected canonical in URL Inspection can be a few hours out of date from the index value. ^{[4]Google Search Console Help. URL Inspection tool} The live test cannot help here at all: information about Google's canonical choice is determined at indexing time, and the live test cannot predict whether the tested version will be considered canonical. ^{[4]Google Search Console Help. URL Inspection tool}

Patience is part of reading the report. Google might hold pages in a duplicate cluster for up to two weeks, and validation of a fix typically takes up to about two weeks and can take much longer. ^{[6]Google Search Central. Fix canonicalization issues [1]Google Search Console Help. Page indexing report}

Two preferences can also produce the status with no content change on your side: Google prefers HTTPS pages over equivalent HTTP pages as canonical, and it prefers URLs that are part of hreflang clusters. ^{[3]Google Search Central. How to specify a canonical URL with rel="canonical" and other methods} Finally, because performance data is assigned to the Google-selected canonical, the overruled URL has no impressions, average position or CTR of its own, so its empty row in the Performance report says nothing about demand. ^{[5]Google Search Console Help. What are impressions, position, and clicks?}