Updated
“Duplicate, Google chose different canonical than user” means this URL declares a canonical (often itself), but Google decided a different URL is the better canonical and indexed that one instead. A canonical tag is a hint, not a rule. Fix it by making every signal agree on the URL you want, or by making the page different enough that it isn’t a duplicate. When Google picked a better URL than you did, accept its choice.
What “Duplicate, Google chose different canonical than user” means
Google’s Page indexing help puts it this way: the page is marked as canonical for a set of pages, but Google thinks another URL makes a better canonical, and has indexed that one instead. Google’s canonicalization guide explains why that is allowed: indicating a canonical preference “is a hint, not a rule”. Google groups pages with the same or very similar main content and picks the version it judges most complete and useful.
This is the canonical status people most often mix up with duplicate without user-selected canonical. The difference: here you did declare a canonical, and Google overruled it.
| Alternate page with proper canonical tag | Duplicate without user-selected canonical | Duplicate, Google chose different canonical than user | |
|---|---|---|---|
| Did this URL declare a canonical? | Yes, pointing to another URL | No | Yes (often itself) |
| Did Google agree? | Yes | Nothing to agree with; Google picked one | No; Google picked a different URL |
| Which URL is indexed | The canonical you declared | The URL Google chose | The URL Google chose |
| Usually means | Working as intended | Duplicates with no canonical set | Your signals disagree, or the pages are not true duplicates |
| Action | Usually none; check the target is right | Pick the canonical and declare it, or redirect | Align your signals, or accept Google’s choice |
| Guide | Alternate page with proper canonical tag | Duplicate without user-selected canonical | This page |
Read the inspection result correctly
Inspect an example URL in the URL Inspection tool and look at three URLs under Page indexing:
- The tested URL: the page you inspected.
- User-declared canonical: what your canonical tag (or header) says.
- Google-selected canonical: what Google indexed.
Open all three in your browser. Google’s help spells out what the combinations mean:
- Google thinks the tested page is a duplicate of the Google-selected canonical, not of the one you declared.
- If the Google-selected canonical is the tested page itself, Google thinks the page isn’t similar to any other page, so it ignored a canonical pointing elsewhere.
- If the canonical you declared isn’t similar to the current page, Google will never choose it. A duplicate has to be similar to its canonical.
The live test doesn’t check canonical selection, so use the indexed result, not a live test, to diagnose this status (URL Inspection help).
Why Google overrides your canonical
Google’s canonical troubleshooting guide says it may choose a different canonical “for various reasons, such as the quality of the content or technical signals.” In practice the causes fall into a few groups:
| Cause | How to confirm it | Fix |
|---|---|---|
| The pages are too similar. Two pages you treat as different are duplicates to Google, so it picks one. | Compare the main content of the tested page and Google’s pick. Same text with a city name swapped is a duplicate. | Make each page substantially different, or merge them and redirect one. |
| Your canonical target is too different. You pointed a canonical at a page that isn’t a duplicate, so Google ignores it. | Google-selected canonical is the tested page itself. | Point the canonical at a true duplicate, or make the page self-canonical. |
| Your signals disagree. The tag says A, but internal links, the sitemap or a redirect point to B. | Check which URL your navigation, breadcrumbs and sitemap use. Check whether A redirects. | Make tag, links, sitemap and redirects all name the same URL. |
| The declared canonical is broken. It redirects, returns 404, is noindexed or is blocked by robots.txt. | Inspect the declared canonical URL itself. | Point the canonical at a live, indexable 200 URL. |
| HTTP vs HTTPS. Google generally prefers HTTPS, unless the certificate is invalid, the page loads insecure content, or HTTPS redirects to HTTP. | Compare the protocols of your canonical and Google’s pick. | Fix the certificate and mixed content; redirect HTTP to HTTPS. |
| Language or country versions without hreflang. Near-identical pages for the US, UK and Australia look like duplicates. | Google picked a version in another region. | Add hreflang annotations; keep canonicals within the same language. |
| Canonical changed by JavaScript or set in two places with different values. | Compare view-source with the rendered HTML in URL Inspection. | Set one canonical in the HTML source and don’t let scripts change it. |
| Another site carries your content: syndication, a copycat, or a hack that inserts a cross-domain canonical or redirect. | Google’s pick is on another domain. | Ask partners to noindex syndicated copies; check the Security issues report; for copied content, see Google’s copyright removal process. |
Signal strengths and best practices are from Google’s guide to specifying a canonical: redirects and canonical tags are strong signals, sitemap inclusion a weak one, and Google prefers URLs in reciprocal hreflang clusters.
How to get your canonical accepted
- Decide whether you’re right. Google’s troubleshooting guide suggests first asking whether its pick makes more sense for searchers than yours. If it does, see the next section.
- Make every signal name the same URL. A self-referencing canonical on the canonical page; canonical tags on the duplicates pointing to it; internal links, breadcrumbs and sitemaps using only that URL;
hreflangpointing at it. Use absolute URLs, and put the tag in the HTML<head>. - Make sure the canonical URL is healthy: it returns 200, isn’t noindexed or blocked, and loads over valid HTTPS.
- Redirect duplicates that don’t need to exist. A redirect is the strongest signal Google lists.
- If the pages shouldn’t be duplicates, make them different. Google’s guide says fixing these issues “boils down to ensuring that the pages that are clustered together are sufficiently different,” and that clearer differences split out faster.
- Request indexing for the few that matter most, then wait. Google may hold pages in a duplicate cluster for up to two weeks after a fix. Request indexing is quota-limited, so save it for key URLs.
Two worked examples
A city page folded into its neighbour
You inspect /plumbers/pflugerville-tx. User-declared canonical: itself. Google-selected canonical: /plumbers/round-rock-tx. Opening both, you see why: Pflugerville has no plumbers of its own, so the template fills it with the same six “nearby” Austin-area businesses Round Rock shows, under the same intro with the town name swapped. To Google they are one page.
Changing tags won’t help, because the tags were already right. The options are content decisions: add businesses that really serve Pflugerville and local detail only that page has; noindex the page until it has listings; or stop publishing towns with no listings and let a broader area page cover them. Pages like this often sit in crawled, currently not indexed too.
A listing whose links point somewhere else
You inspect /listing/joes-plumbing, which is self-canonical. Google picked /plumbers/austin-tx/joes-plumbing, the same listing under a category path. Here the content is identical, so it is a signals problem: the category pages, breadcrumbs and sitemap all link to the category path, and only the canonical tag names /listing/joes-plumbing. Google went with the majority. The fix is to make every link and the sitemap use one URL, and redirect the other path to it. Either URL can win; what matters is that all your signals pick the same one.
When to accept Google’s choice
Not every instance is a problem. Leave it when:
- Google picked the clean or HTTPS version and you declared a messier one by mistake. Fix your tag to match Google instead.
- The two pages really are the same, and Google’s pick is one you link to and are happy for people to land on.
- The URL is one you would happily merge, such as two near-identical articles. Redirect the weaker one to Google’s choice and the status goes away.
It is worth a fight when Google’s pick is a URL you are about to remove, a parameter or tracking URL, a page on another domain, or a page that serves a different place or service from the one searchers asked for.
On directory websites
Directories hit this status in a few predictable ways:
- Two URL patterns for the same place and category, such as
/plumbers/austin-txand/austin-tx/plumbers, both self-canonical. Google keeps one. Pick a pattern, redirect the other. - City pages that differ only by name. If
/plumbers/pflugerville-txshows the same five Austin businesses and the same intro as/plumbers/round-rock-tx, Google may fold one into the other however you set the tags. Real local listings and local details fix it; tags don’t. See location pages SEO. - Duplicate listings: the same business added twice (
/listing/joes-plumbingand/listing/joes-plumbing-2), or one chain with the same description on twelve location listings. Merge true duplicates; give each location its own address, hours, photos and reviews. - Paginated pages canonicalised to page 1. Google sees page 3 isn’t a copy of page 1 and may ignore the tag. Give each page its own canonical (Google’s pagination guide).
Find every overridden canonical with DirectoryLens
In DirectoryLens’s Google indexing report, the Individual pages tab flags Google picked another canonical on any inspected URL where your declared canonical and Google’s differ, and its history shows both URLs side by side. Filter by that flag and by page type to see whether it’s a few listings or a whole template, and click any URL to see Google’s canonical on each past inspection. Runs on a page type or sitemap go beyond the 1,000 examples Search Console shows.
For every other status and what it means, see the page indexing issues guide. To try the report on sample data first, open the live demo.