Duplicate, Google chose different canonical than user: how to fix it

Last updated: 2026-10-30

In short

This status means the page is marked as canonical for a set of pages, but Google decided another URL is the better representative and indexed that one instead. A canonical tag is a hint, not a rule. Compare the pages involved, then make redirects, canonical tags, internal links and sitemaps all point at the same URL.

Exact label in Search Console: Duplicate, Google chose different canonical than user

What it means

Google's Page indexing help says the page is marked as canonical for a set of pages, but Google thinks another URL makes a better canonical and has indexed that URL rather than this one. URL Inspection shows both values: User-declared canonical (yours) and Google-selected canonical (Google's choice).

Google's documentation is explicit that a canonical preference is a hint, not a rule. Its signals include redirects, rel="canonical" annotations, sitemap inclusion, HTTPS over HTTP and hreflang clusters. Google adds a useful test: if your user-declared canonical is not similar to the current page, Google will never choose it, because a duplicate must be similar to its canonical. If the Google-selected canonical is the inspected page itself, Google thinks the page is not similar to any other page.

Is it a problem?

Check the Google-selected canonical first. If it is a URL you are happy with, for example the HTTPS version of a page you tagged with HTTP by mistake, little is lost. It is a problem when Google picks a parameter URL, an old URL, another host or a page on a site you do not control, because clicks and reporting then go to that URL. Google warns that if the canonical sits in a property you do not own, you will not see traffic for your duplicate page.

Common causes

Conflicting signals

The canonical tag says one URL, but internal links, redirects or the sitemap point to another. Google says these methods stack, so signals that disagree weaken your preference.

Canonical points at a different page

A canonical to a category page, the homepage or any page with different content is not followed, because Google only treats similar pages as duplicates.

HTTPS and certificate problems

Google prefers HTTPS, but an invalid certificate, an HTTPS-to-HTTP redirect or a canonical from HTTPS to HTTP make it prefer the HTTP version.

CMS, plugin or JavaScript errors

Google's troubleshooting guide names CMS plugins that output wrong canonical elements. Canonicals rewritten by JavaScript after load add more confusion.

Misconfigured servers, hacks or copied content

Google lists servers returning content from another host, injected cross-domain canonicals or redirects after a hack, and copycat sites hosting your content.

Syndication

When partners republish your articles, Google may choose their copy. Google says canonical tags are not the recommended fix here; the partner blocking indexing of its copy is.

How to fix it

  1. Compare the three pages. As Google's help suggests, open the current page, your declared canonical and Google's selected canonical side by side, and decide which one really should represent the content.
  2. Align every signal on one URL. Use rel="canonical" with an absolute URL, link internally only to that URL, list only that URL in your sitemap and 301 redirect duplicates nobody needs. Never name one URL in the sitemap and another in rel="canonical".
  3. Fix technical overrides. Check the raw and rendered HTML in URL Inspection for duplicate or JavaScript-modified canonical tags, check response headers for a Link rel="canonical" that disagrees with the HTML, and fix certificate or HTTPS redirect problems.
  4. Make different pages clearly different. If Google clustered pages that should stand alone, Google says the fix comes down to making them sufficiently different, and that pages split out faster when the difference is clear and significant.
  5. Give it time, then request indexing. Google says it may hold pages in a duplicate cluster for up to two weeks after content fixes. After that, use Request indexing for your most important URLs only, since the feature has a quota.

Check it with GSC Magic

Run gsc_inspect_urls_batch on the affected URLs and have your assistant list every case where the Google-selected canonical differs from the user-declared one, grouped by the URL Google chose. Patterns show up quickly: a template pointing to HTTP, a paginated series collapsing onto page one, or a plugin writing the wrong host. gsc_query_analytics by page shows which URL actually collects the impressions before and after your fix.

gsc_inspect_urls_batchgsc_inspect_urlgsc_query_analytics

Prompts to copy

Inspect these URLs and list every one where the Google-selected canonical differs from the user-declared canonical. Show both values and group the rows by host and path pattern of the Google-selected URL.

For URLs where Google chose a different canonical, check whether the Google-selected URL differs from the declared one only by protocol, host, trailing slash or query string.

Compare clicks and impressions over the last 28 days for each declared canonical and the URL Google selected instead, and tell me which version gets the traffic.

Guides on the blog

Duplicate without user-selected canonical

This status means Google sees the URL as a duplicate of another page, you did not declare a canonical, and Google picked the other URL to show in Search. Google calls this working as intended. Act only if Google picked the wrong URL or if the page is not really a duplicate.

 Alternate page with proper canonical tag

This status means the URL is an alternate version that correctly points to another canonical page, and that canonical is indexed. Google says there is nothing you need to do. Spot-check that the canonical is the URL you want and that no important page ended up here by mistake.

 Page with redirect

Page with redirect means the URL is a non-canonical URL that redirects to another page, so Google does not index it. That is expected for old URLs, HTTP or www variants and moved pages. Check that the redirect target is correct and indexable, and stop linking to redirecting URLs from your pages and sitemap.

 Crawled - currently not indexed

Crawled - currently not indexed means Googlebot fetched the page but Google decided not to add it to the index, at least for now. Google says it may or may not be indexed later and that you do not need to resubmit it. For pages that matter, make them clearly distinct and useful, link to them internally and check canonical signals.

Frequently asked questions

Why does Google ignore my canonical tag?

Google treats rel="canonical" as a strong signal but only a hint. It can choose another URL when your signals conflict, when the declared canonical is not similar to the page, or when content and technical signals favor another version.

Can the live test show whether my canonical will be accepted?

No. Google's URL Inspection help says the canonical can only be determined in the indexed data, and the live test cannot predict whether the tested version will be considered canonical.

How long does it take after I fix it?

Google's canonical troubleshooting guide says it may hold pages in a duplicate cluster for up to two weeks after content fixes. Recheck the URL after that and request indexing for the most important pages.

Google picked a URL on another site. What can I do?

Google's guide covers this: check for server misconfiguration or hacking, ask syndication partners to block indexing of their copies, and for copied content contact the site's host or file a DMCA request with Google.

Sources