Skip to content

Duplicate, Google chose different canonical than user: fixes

What Duplicate, Google chose different canonical than user means, how to compare the two URLs, and when to accept Google's choice or make the pages distinct.

By Crawlito · 10 min read

In short

  • Duplicate, Google chose different canonical than user means you declared a page canonical, Google clustered it with another URL and indexed that URL instead.
  • Google's help page says that if the inspected page is not similar to your declared canonical, Google will not choose your declared URL.
  • The URL Inspection live test cannot show or predict the Google-selected canonical, because Google decides canonicals at indexing time.
  • Google says fixing canonicalization comes down to making clustered pages sufficiently different, and that pages can stay in a duplicate cluster for up to two weeks after content fixes.
  • Duplicate without user-selected canonical is not an error: Google picked a canonical for a page that declared none, and you either confirm the choice or make the page substantially different.
On this page

"Duplicate, Google chose different canonical than user" means a page told Google it was canonical (or named another URL as canonical), but Google grouped it with other similar pages and indexed a different URL from that group. The page you declared is not indexed. The fix is a decision, not a setting: read which URL Google picked, compare the two pages, then either accept Google's choice and make your signals agree with it, or change the pages so they are no longer duplicates.

This post is the decision flow for that status and for its sibling, "Duplicate without user-selected canonical", with most space on near-duplicate templates. The individual signal conflicts (sitemap, redirects, internal links, hreflang) are covered in canonical tags and duplicate URLs, and this post links there instead of repeating them. Facts come from Google Search Central and Search Console Help, read on 15 November 2026.

What the two duplicate statuses mean

Google's Page indexing report help lists three canonical-related reasons. They look alike in the report but call for different actions.

StatusWhat Google says happenedAction
Duplicate, Google chose different canonical than userYou marked a canonical, but Google thinks another URL makes a better canonical and indexed that oneCompare the two URLs, then align or differentiate
Duplicate without user-selected canonicalThe page is a duplicate of another page and does not declare a preferred canonical; Google chose oneNot an error: confirm the choice, declare your preference, or make the page substantially different
Alternate page with proper canonical tagThe page points to its canonical, and that canonical is indexedNothing to do (see alternate page with proper canonical tag)

The first status is the only one where Google is overriding something you said. Google's canonicalization overview explains why that is allowed: a canonical preference "is a hint, not a rule". Google clusters pages with the same or nearly the same content and picks the one it considers most complete and useful for searchers, weighing HTTPS, redirects, sitemaps and rel="canonical" together.

The same page also says duplicate content on its own is normal and not a violation of Google's spam policies. These statuses are about which URL gets indexed, not a penalty.

Step 1: read the Google-selected canonical

Open the affected URL in the URL Inspection tool and expand the page indexing section. Two fields matter:

  • User-declared canonical: the URL your page names. Google says "None" is fine for a page that is not an alternate.
  • Google-selected canonical: the URL Google indexed for the cluster. If the page has no alternates, this is the inspected URL itself.

Three practical limits apply. Google notes the Google-selected value "can be a few hours out of date" compared with the index. The live test does not show it at all: Google says the live test "cannot predict whether or not the tested version will be considered canonical", because that is decided at indexing time. And URL Inspection only gives details of the canonical version if it is in a property you own; Google's troubleshooting guide adds that when the canonical sits in a property you do not own, you will not see any of the traffic for your duplicate page. For how the rest of the inspection screen works, see the URL Inspection tool guide.

Write down the three URLs: the inspected page, your declared canonical and Google's choice.

Step 2: compare the two pages as content, not as URLs

Google's help page spells out what the status means: Google thinks the inspected page is not a duplicate of your user-declared canonical, but is a duplicate of the Google-selected canonical. It adds that if the user-declared canonical is not similar to the current page, Google "won't ever choose that URL as canonical". That gives you two comparisons: the inspected page against Google's choice (Google thinks they are the same), and, if your canonical points to another URL, the inspected page against that URL (Google thinks they differ). Compare what a reader actually gets on each.

A quick text comparison from the terminal shows how much of the main content is shared:

bash
A="https://www.example.com/plumbers/leeds"
B="https://www.example.com/plumbers/bradford"
words() {
  curl -sL "$1" \
    | perl -0777 -pe 's/<(script|style)\b.*?<\/\1>//gis; s/<[^>]+>/ /g' \
    | tr -cs '[:alnum:]' '\n' | tr '[:upper:]' '[:lower:]' | sort -u
}
words "$A" > a.txt
words "$B" > b.txt
comm -12 a.txt b.txt | wc -l   # words both pages share
comm -3  a.txt b.txt | wc -l   # words only one page has

This is a rough guide, not Google's algorithm, and the raw HTML includes navigation and footer text that every page shares. What you are looking for is the body: does the main content of page A contain anything that page B does not? If you can only find the city name, a product colour or a tag label, Google is probably right that the pages are duplicates.

Then answer one question: would a searcher landing on Google's choice be worse off than one landing on yours? Google's canonicalization troubleshooting guide asks much the same thing in its first step: whether the Google-selected canonical makes more sense than your preferred URL for users coming from Google Search. The answer sends you down one of two paths.

Your findingPath
The pages are true duplicates (same content, different URL)Accept Google's choice or move the signals to your preferred URL
The pages share a template but should serve different searchersDifferentiate the content
Google picked a URL on a host or domain you did not expectCheck for misconfiguration, copying or hacking first

Path A: true duplicates, so make every signal agree

True duplicates are the same content at two addresses: /shoes and /shoes?ref=nav, a printer view, an old path still served without a redirect. Here Google's choice is often fine, and the cheapest fix is to accept it. Change your rel="canonical" to the URL Google picked, so your declared and Google-selected canonicals match and Google is no longer overriding you. Google does not document how quickly the report updates after that.

If you want your URL to win instead, you have to give Google more reasons to agree than to disagree. That means redirects, internal links, sitemap entries and the canonical tag all naming the same URL. Each of those conflicts, and how to test it with curl, is in the canonical audit section. Two rules from Google's consolidation guide are worth keeping in mind here: don't use robots.txt or the URL removal tool for canonicalization (the removal tool hides all versions of a URL from Search), and Google does not recommend noindex to prevent selection of a canonical within one site, because it blocks the page from Search completely. If the duplicate comes from query strings, URL parameters and AI search covers where they come from and how to classify them.

Path B: near-duplicate templates, so make the pages different

This is the harder case. The URLs are meant to be separate pages, but the template does most of the talking. Google's troubleshooting guide says fixing canonicalization issues "technically boils down to" making sure the clustered pages are "sufficiently different". Three template families come up often.

Location pages

A service business with /plumbers/leeds, /plumbers/bradford and /plumbers/york, where each page is the same text with the town swapped in. To Google these are one page in three copies. They also come close to an example in Google's spam policies under doorway abuse: "multiple domain names or pages targeted at specific regions or cities that funnel users to one page".

Each page earns its own URL only with information that is true for that place and not the others: the address or service area, opening hours, staff, local prices, jobs done there, directions. If you do not have that information, one page listing all the areas you serve is the honest structure, and the town pages can redirect to it.

For same-language sites serving different countries, such as English pages for the US, UK and Australia, Google's troubleshooting guide points to hreflang annotations rather than rewriting. Google's canonicalization overview adds that language versions are still treated as duplicates if only the header, footer and other non-critical text is translated while the body stays the same.

Product variants

A red and a blue version of the same shirt on separate URLs, with identical descriptions. Google's ecommerce URL structure guide says each variant should be identifiable by its own URL, that for optional query-parameter variants you should use the URL without the parameter as the canonical, and that for products with unique variant URLs you should include the canonical product URL on all variant pages. Google's product variant structured data guide describes two models: a single-page site with one canonical URL for the whole product group, and a multi-page site where variants are spread across equally important pages. If your variant pages differ only by a colour name, "chose different canonical" is a sign that Google is treating them as the single-page case while your template declares each variant as its own canonical. Decide which model you run, then follow product variants and AI search to keep the selected offer consistent on each URL.

Tag, category and archive pages

A blog where /tag/robots-txt and /category/robots-txt list the same five posts, or a shop where a thin category and its only subcategory show the same products. Google does not give a tag-page rule, so apply the content test: if two listing pages contain the same items in the same order with no text of their own, they are duplicates. Either merge the taxonomies, add an introduction and a distinct selection to the page you want indexed, or let one canonical to the other. Google's ecommerce guide adds that an empty category should carry a noindex robots meta tag.

After you change the content

Google says it may keep pages in a cluster for up to two weeks after content fixes, and that pages generally split out faster when the difference from the other clustered pages is "clear and significant". Once the change is live, use Request Indexing in URL Inspection on the most important URLs only, since Google says it is subject to quotas. If a page stays out of the index for other reasons afterwards, the crawled, currently not indexed guide covers the next status you may see.

When Google's choice points somewhere unexpected

If the Google-selected canonical is on a host or domain you do not recognise, stop the content work and check these first. Google's troubleshooting guide lists them as causes:

  • A CMS or plugin printing the wrong canonical or redirect. Inspect the HTML in your browser's developer tools; if the tag is wrong, the template is the bug.
  • A misconfigured server returning one domain's content for another, or identical soft 404 pages across unrelated hosts.
  • A hacked site with an injected 3xx redirect or a cross-domain canonical pointing at spam.
  • Syndicated content. Google does not recommend the canonical element for avoiding duplication with syndication partners; it says the most effective solution is for partners to block indexing of your content.
  • A copycat site that republished your content. Google says you can ask the host to remove it or file a DMCA request.

Why this matters beyond Google

Google's AI features guide says a page must be indexed and eligible to be shown in Google Search with a snippet to be a supporting link in AI Overviews or AI Mode. A URL that loses the canonical choice is not indexed, so the duplicate cluster decides which of your URLs is even eligible. Other AI search tools do not document how their crawlers treat canonical tags at the time of writing. Pages that are genuinely distinct, with one URL per distinct page, are the setup that does not depend on any crawler's undocumented behaviour. That removes a technical barrier; it does not promise that any assistant will cite the page.

Frequently asked questions

Is "Duplicate, Google chose different canonical than user" an error?

Google's help page calls it an error in the sense that your declared canonical was not used, but it is not a penalty. Google indexed a different URL from the cluster, so the page in this status is not indexed.

Can I force Google to use my canonical?

No. Google treats your canonical as a hint. You can make every signal point at your URL, or make the pages different enough that Google stops treating them as duplicates.

Why does the live test not show the Google-selected canonical?

Google decides the canonical at indexing time, so the live test cannot predict it. Read the Google-selected canonical from the indexed result instead, and allow for it to lag by a few hours.

How long until the status changes after a fix?

Google says pages can stay in a duplicate cluster for up to two weeks after content fixes. Requesting indexing for key URLs can prompt a re-evaluation, within the daily limit.

What should I do with "Duplicate without user-selected canonical"?

Check which URL Google chose. If you agree, add a canonical on the duplicate pointing to it; if you disagree, declare your preference; if the page is not really a duplicate, make its content substantially different.

Check the page Google passed over

Before you rewrite a template, confirm the page you want indexed returns its main content, one canonical and no conflicting robots rules to crawlers. The free check reads a single page the way crawlers fetch it and shows what they receive.

Filed under Structure and schema. Topics: canonical, search-console, google, troubleshooting