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

Why does Google ignore my canonical tag?

Because the tag is a request. Google calls a canonical preference “a hint, not a rule.” It reads your tag next to everything else your site says about the page. A redirect counts at least as much: Google lists it first and calls both the redirect and the tag “a strong signal.” Your sitemap is a weak one. Google also prefers HTTPS over HTTP, and it reads which URL your own links use. When all of them name one URL, they add up. When they don’t, Google weighs them and picks.

There’s a second way to land here: Google decides your page is a copy of some other page and groups the two, whatever your tag says. And your tag can’t point just anywhere. A tag that names a page this one doesn’t look like never wins, since a duplicate “must be similar to the canonical. (That’s what duplicate means.)”

How do I see which URL Google chose?

Open the Page indexing report in Search Console, click this status and inspect one of its example URLs. Two lines under Page indexing tell the story. User-declared canonical is the URL your page names. Google-selected canonical is the one Google indexed.

Read the indexed result, not the live test. Google decides the canonical when it indexes a page, so “the live test cannot predict” it, and it can’t confirm a fix either.

Then look at the URL Google picked. It’s one of three kinds, each with its own fix.

The third kind is the one founders argue with. One poster on r/bigseo found “almost 100 pages that have not been indexed because Google thinks they are duplicates (they are not).” They had “a similar page format but unique photos, text, and field values.” Google groups pages whose main content looks nearly the same, and on a software site that can be the integrations page that swaps one partner’s name for another.

What sends Google two answers about one page?

Usually something small, and most sites get it right. On November 13, 2026, we checked the homepages of 292 startup sites, a random sample of the active B2B companies in a public copy of Y Combinator’s directory. We read each homepage’s canonical tag, then asked for the same page on the site’s other host (with or without www) and on plain http. 14 of the 292, about 5%, told Google two different things about which URL is the homepage.

13 homepages carry a canonical tag that names a different URL from the one that loads. In 10 of them, the difference is the www. On 5, the URL the tag names redirects straight back to the page. So the redirect says one URL is the original, the tag says the other, and Google has to overrule one of its two strong signals.

6 serve the homepage on a second host with 200 OK, and that copy’s tag names itself. That’s the setup for this status. 2 more homepages carry two canonical tags, and Google’s 2013 advice is that it then ignores all of them.

A second copy is common: 43 of the 292 answered on the other host or plain http instead of redirecting, 46 copies in all. What a copy’s tag says decides which status it shows up under, if Google finds it. On 18 of the 46, it points home, which makes it an alternate page with proper canonical tag. On 21, there’s no tag at all, so Google picks for it.

Does it matter which URL Google picked?

Sometimes not at all. If Google indexed the URL you’d want a buyer to land on, people still find the page. Google’s own troubleshooting guide asks you to think about whether its pick “makes more sense than your preferred canonical URL” for people coming from Search.

When it’s the wrong one, the cost is more than an ugly address. Google “uses the canonical page as the main source to evaluate content and quality,” so the copy you don’t want is the one it judges and shows. Only that URL can be a link in AI Overviews or AI Mode, which need a page “indexed and eligible to be shown in Google Search with a snippet.” And Bing says duplicate URLs “reduce Bing’s confidence in selecting a URL for grounding results or citations.”

How do you get Google to use your URL?

Start with the strongest signal you can use, and make every other one agree with it.

• Redirect the copies nobody needsThe other host, plain http, an old URL: send each one to the original with a 301. Our own www host does this, and Search Console lists www.firstindex.com as Page with redirect, with nothing left for Google to decide.
• Tag the copies that have to existA link with ?utm_source still loads its page. That copy’s tag should name the original as a full URL, in the head of the HTML. Google ignores it anywhere else.
• List only originals in your sitemapIt’s the weakest signal, but it still shouldn’t name a different URL than the tag does.
• Link to the originalNav, footer and links in your copy should all use the same URL. Every link to the other version is a small vote for it.
• Make look-alike pages different, or merge themIf Google picked a different page, tags won’t fix it. The pages have to differ. Give each integration page what only it has: what the integration does, how to set it up, what customers use it for. If two pages really say the same thing, keep one and 301 the other to it.

Don’t noindex a copy or block it in robots.txt to force Google’s hand. Google says noindex “will completely block the page from Search” and tells you not to use robots.txt for this.

Then let Google look again. Request indexing for the few URLs that matter most (it has a quota), or click Validate fix in the report. Google says its old grouping of the pages can stay “for up to two weeks” after you fix the content, and validation “typically takes up to about two weeks.” Check the indexed result in URL Inspection after the next crawl. If the URL turns up under crawled - currently not indexed instead, that’s a different problem, and we have a guide for it too.

Google and AI have to know which URL is yours before anyone can recommend it. Making a site’s redirects, tags, sitemap and links name the same URLs is the kind of change we ship every day for 30+ software companies, for $2,000 a month. Here’s what the plan covers.

Questions