What does “Duplicate, Google chose different canonical than user” mean?
“Duplicate, Google chose different canonical than user” means you declared a canonical URL, but Google thinks another URL is the better main version and indexed that one instead. Google says it sees your page as a duplicate of its choice, not of yours. Compare the three pages in URL Inspection, then fix whatever points the wrong way.
The short version
- Google's definition: “This page is marked as canonical for a set of pages, but Google thinks another URL makes a better canonical. Google has indexed the page that we consider canonical rather than this one.”
- Unlike “Duplicate without user-selected canonical”, which Google says is “not an error”, this status is described in the same help page as an error.
- A
rel="canonical"tag is “a strong signal”, but Google also says that indicating a canonical preference “is a hint, not a rule”. - If the canonical you declared is not similar to the page, Google “won't ever choose that URL as canonical”: a duplicate must be similar to the canonical.
- The live test in URL Inspection cannot show this: “the live test cannot predict whether or not the tested version will be considered canonical.”
What Google weighs
| Signal | What Google says |
|---|---|
| Redirects | “A strong signal that the target of the redirect should become canonical.” |
rel="canonical" annotations | “A strong signal that the specified URL should become canonical.” |
| Sitemap inclusion | “A weak signal that helps the URLs that are included in a sitemap become canonical.” |
| HTTPS | Google prefers HTTPS pages over equivalent HTTP pages, “except when there are issues or conflicting signals”. |
| Similar content | Google clusters pages whose primary content is very similar, then picks the page it finds “objectively the most complete and useful for search users”. |
| Internal links | Not rated strong or weak. Google's advice is to link to the canonical URL rather than a duplicate, which “helps Google understand your preference”. |
These signals can stack, and they can fight: Google tells you not to give different canonicals for one page through different methods, such as one URL in a sitemap and another in the tag.
Why Google picked a different one
Google's troubleshooting page lists the usual reasons. The ones you can check yourself:
- An incorrect canonical element. “Some content management systems (CMS) or CMS plugins can make incorrect use of canonicalization techniques to point to undesired URLs.” Look at the HTML in your browser's developer tools.
- The pages are not really duplicates. Google's fix, in its own words, “boils down to ensuring that the pages that are clustered together are sufficiently different”.
- Language variants without hreflang. Google says hreflang annotations help the right page surface for each region.
- A misconfigured server. Google's example is two unrelated servers returning identical soft 404 pages that Google fails to identify as errors.
- Mixed HTTP and HTTPS signals, such as an HTTPS page that has a canonical to the HTTP page or redirects through one.
- Rarer causes: injected redirects or canonicals after a hack, syndicated copies, and a site copying your content.
Details on the tag itself: it is only accepted in the <head>; Google recommends absolute URLs; a page should have one; and if you use JavaScript, Google says to put the canonical in the HTML source and make sure JavaScript doesn't change it.
Find out which URL Google chose
- In Search Console, run URL Inspection on the URL and read the indexed view.
- User-declared canonical is what your page says (a tag, a header, a sitemap or a few other methods). Google-selected canonical is the page Google chose “when it found similar pages on your site”.
- Open the current page, the declared canonical and Google's choice side by side, and ask which one is the better main version. That is Google's own instruction.
Check what your page declares
Paste the URL. The checker reads the canonical tag (and flags a missing one, several different ones, or a relative one), says whether it points at this page or another, and fetches the target to see whether it returns 200, redirects or fails.
What we tested
On 2026-10-19 we ran the live Meta, Canonical & Noindex Checker on three addresses of this site and on small test pages we built for this guide. The test pages are a preview that tells search engines not to index it, so the checker also reported a noindex item on them; the table lists only the canonical items.
| What we entered | What the checker reported about the canonical |
|---|---|
| One of this site's guides | “Self-referencing canonical”, and the target is this page and returns 200. Passed. |
The same guide with ?utm_source=newsletter added | “The canonical points to a different URL” (the clean address), target returns 200. Review. |
| The same guide with a trailing slash | One permanent redirect (308) to the address without the slash, then a self-referencing canonical. Passed. |
| A page about bicycles whose canonical points to a page about kettles | “The canonical points to a different URL”, target returns 200. Review. Nothing says the two pages have different content. |
| A canonical that points to a URL that does not exist | “The canonical target returns 404”. Fix before publishing. |
| A canonical that points to a URL that redirects | “The canonical target redirects” (301 to the final page). Review. |
| A canonical written as a relative URL | “Self-referencing canonical, but written as a relative URL”. Review. |
| Two different canonical tags | “2 canonical tags with different URLs”. Fix before publishing. |
| No canonical tag | “No canonical tag”. Review. |
The bicycles-and-kettles row is the case Google is describing: a canonical that points at a page that is not similar. The checker can report that the canonical points elsewhere and that the target loads, but it does not compare the content of the two pages, so it cannot tell you whether Google will accept your choice.
How to fix it
- Decide which URL should be the main version. If Google's choice makes more sense for people arriving from search, point your canonical at it, or accept it.
- If your page genuinely differs, make the content differ clearly: Google says pages split out of a duplicate cluster faster when the difference is “clear and significant”.
- If they are duplicates, put a self-referencing, absolute canonical in the
<head>of the page you want indexed, one tag only. - Make the other signals agree: redirects, sitemap, internal links and HTTPS should all name the same URL.
- Then wait. Google says it “might hold pages in a duplicate cluster for up to two weeks” after you fix content issues, and suggests Request Indexing for your most important URLs, since it is subject to quotas.
What this can't tell you
It cannot see which URL Google chose, or whether your page and the target are similar enough: only URL Inspection shows Google's choice, and only on the indexed version. We also found no definition of the sibling status “Duplicate, submitted URL not selected as canonical” in Google's current Page indexing help; the name appears only in a list of issues the live test cannot check, so this guide does not explain it.
Related: Duplicate without user-selected canonical and Alternate page with proper canonical tag.
Sources
We read these official pages on 2026-10-19.
- Page indexing report - Search Console Help
- URL Inspection tool - Search Console Help
- What is URL Canonicalization (page dated 2026-08-20)
- How to Specify a Canonical with rel="canonical" and Other Methods (page dated 2026-07-10)
- Fix Canonicalization Issues (page dated 2026-08-21)
- Understand JavaScript SEO Basics (page dated 2026-03-04)
- Redirects and Google Search (page dated 2026-04-14)
- Build and Submit a Sitemap (page dated 2026-07-08)
- RFC 6596: The Canonical Link Relation
Fixed this one? Before you send people to the page, run the full pre-publish check for everything else: indexing signals, link preview, broken links, alt text, structured data and HTTPS in one pass.