Google chose different canonical: how to fix it

"Duplicate, Google chose different canonical than user" in Search Console means your page says it's the main version, but Google decided another URL is the better one and indexed that instead. Your page won't show in Search; the other one will. Sometimes that's harmless. When the URL Google picked is wrong, such as a filter URL, a tracking link or an old HTTP page, you can usually fix it by making your signals consistent.

What the status means

Google's Page indexing report help describes it this way: the page is marked as canonical for a set of pages, "but Google thinks another URL makes a better canonical." In other words, your rel="canonical" is a request, not an instruction. Google weighs it against other signals.

It's often confused with two related statuses:

Status	What happened	Action needed?
Duplicate, Google chose different canonical than user	You set a canonical; Google overruled it	Check which URL Google picked
Duplicate without user-selected canonical	No canonical set; Google picked one itself	Usually fine; add canonicals if the choice is wrong
Alternate page with proper canonical tag	Your canonical was accepted	None, per Google

First, find out which URL Google picked

Open the URL in Search Console's URL Inspection tool and look at the indexed result. Two fields matter:

User-declared canonical: the canonical your page states.
Google-selected canonical: the URL Google actually chose.

Use the indexed result, not the live test. Google's help page says the live test "cannot predict" which version will be treated as canonical, because that's decided at indexing time.

Then sort the result into one of three cases:

Google picked a URL you'd also be happy with. For example, it chose /shoes/ over /shoes/?sort=price. No harm done. Fix your canonical tag so it agrees, and move on.
Google picked a worse URL. For example, a UTM-tagged link, the HTTP version or a staging domain. This needs fixing.
Google merged two pages you consider different. For example, two city pages with near-identical text. Google sees them as duplicates, and the real fix is content, not tags.

Why Google overrules your canonical

Google's guide to consolidating duplicate URLs ranks the signals. Redirects and rel="canonical" are strong signals. Sitemap inclusion is weak. Google also prefers HTTPS over HTTP and prefers URLs in hreflang clusters. When these signals point in different directions, Google picks for itself.

The usual causes we see on Indian sites:

Internal links point to the non-canonical URL. Your product page declares /kurta-blue/ as canonical, but the menu, breadcrumbs and "related products" all link to /kurta-blue/?variant=123.
The sitemap lists the wrong version. It includes parameter URLs, www and non-www together, or old HTTP URLs.
HTTPS problems. Google's guide warns that bad certificates or HTTPS-to-HTTP redirects push it strongly towards HTTP.
Tracking links that spread. WhatsApp and Instagram share links with ?utm_source= get shared, linked to and crawled.
Pages that are actually duplicates. For example, a "packers and movers in Bangalore" page and a "packers and movers in Bengaluru" page with the same text. Or 30 area pages for a clinic chain that differ only in the locality name. Google is likely to treat these as one page whatever your tags say.
Conflicting signals. The canonical tag says one URL, the HTTP header says another, and a plugin adds a third. Google's guide says not to specify different canonicals for the same page using different methods.

How to fix it

Work through these in order and stop when the status clears.

Make every signal agree. Pick one URL format, including protocol, www and trailing slash, and use it in the canonical tag, internal links, the sitemap and hreflang.
Add a self-referencing canonical on the page you want indexed, using an absolute URL, as Google recommends.
Redirect true duplicates. If an old URL has no reason to exist, a permanent server-side redirect is the strongest signal you can send.
Clean the sitemap. List only canonical URLs that return 200. The sitemap is a weak signal, but a messy one still works against you.
Fix internal links in templates. Change the menu, breadcrumb and product grid code, not individual links one by one.
Make near-duplicates different, or merge them. A city page earns its own index slot with real local detail: the branch address, local prices in ₹, team photos, reviews from that area, directions. If you can't write that, merge the pages and redirect.
Don't reach for the wrong tools. Google's guide says not to use robots.txt or noindex to choose a canonical, or the URL removal tool. A noindex blocks the page entirely, and a robots.txt block can leave a URL indexed without its content.

After fixing, request indexing for a few key URLs in URL Inspection, then use "Validate fix" in the Page indexing report. Google says validation typically takes up to about two weeks and sometimes longer.

What it means for Indian brands

Three setups produce most of the cases we audit:

D2C stores on Shopify-style platforms where variant, collection-path and filter URLs are all crawlable. The product is fine, but the wrong URL ranks, and that URL may show the wrong colour or price in results.
Multi-city service businesses that copy-paste one page across 20 cities. Google indexes a few and folds the rest in as duplicates.
Bilingual sites (English and Hindi, say) with hreflang set up but canonicals pointing every language back to the English page. Google's guide says canonicals should point to a page in the same language, and that canonical tags with hreflang attributes are ignored for canonicalisation.

If you've recently moved to a CDN or changed hosts, check for HTTP/HTTPS and hostname mismatches too. Our post on CDN migration SEO covers the crawling side. And if you're weighing deleting pages instead, read why content pruning won't fix indexing on its own first.

What to do this week

Export the "Duplicate, Google chose different canonical than user" URLs from the Page indexing report.
Inspect your 10 most important URLs and note the Google-selected canonical for each.
Tag each one as acceptable, wrong URL or merged pages.
Check your sitemap for parameter, HTTP and non-preferred hostname URLs.
Fix internal links in your templates so they point to canonical URLs.
For copy-paste city pages, decide which to rewrite with local detail and which to merge.
Don't make big structural changes while the November 2026 core update is still rolling out, if it hasn't finished when you read this.

FAQ

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

Not always. If Google picked a URL you're happy with, nothing is lost. It matters when the chosen URL is wrong for users or when two pages you want indexed separately are being merged.

Will a canonical tag force Google to index my URL?

No. Google treats rel="canonical" as a strong signal, not a directive. Consistent internal links, a clean sitemap and redirects make it far more likely Google follows it.

How long does it take to fix?

Google says Page indexing validation typically takes up to about two weeks, and sometimes much longer. Inspect key URLs again after that to confirm the Google-selected canonical has changed.