Page indexing report · Search Console
Duplicate, Google chose different canonical than user
You told Google which URL is canonical, and Google indexed a different one.1 The content is usually still in Search under the other address, so it’s often not urgent. Here’s how to find out why Google disagreed and whether to fix it or accept it.
Check the URL first
The checker reads the canonical tag on the URL and tests whether the target works. It can’t see which URL Google chose; URL Inspection shows that.
In 30 seconds
- A canonical tag is a hint. Google weighs it against other signals and can pick another URL.2
- Google won’t pick a declared canonical that isn’t similar to the page.1
- The usual fixes: make redirects, sitemap, internal links and hreflang agree, or accept Google’s choice.3
- Google’s John Mueller says Google picking another URL on your site is normal.6
What the status means
The page declares a canonical, either itself or another URL, but Google thinks a different URL is the better canonical and indexed that one instead.1 Google groups pages with the same or very similar main content and picks the most complete and useful one. Your canonical is one factor; redirects, sitemaps and HTTPS are others.2
The choice is made at the indexing stage. Select a stage to see what happens there.
Discover
Google learns that a URL exists, mostly from links on pages it already knows and from XML sitemaps.
What goes wrong: Nothing links to the page and it isn’t in a sitemap, so Google never hears about it.
Report statuses at this stage
- URL is unknown to Google (shown in URL Inspection, not in the report)
Crawl
Googlebot checks robots.txt, then requests the URL. It spaces requests out so it doesn’t overload the server.
What goes wrong: The URL is blocked, returns an error, or the server is slow, so Google backs off and crawls less.
Report statuses at this stage
Render
Google runs the page’s JavaScript in a recent version of Chrome to see the finished page.
What goes wrong: Content only appears after a click or scroll, or the scripts fail, so the rendered page is nearly empty.
Report statuses at this stage
- No status of its own. Problems show up at the next stage as thin pages or soft 404s.
Index
Google decides which version of the page to keep and whether it is worth storing at all.
- Group duplicates. Pages with the same or very similar content go into one group.
- Pick a canonical. One URL represents each group. Canonical tags, redirects and sitemaps are hints, not commands.
- Select for the index. Google decides whether the canonical page is worth keeping. Google says this largely depends on quality.
What goes wrong: The page duplicates another, is marked noindex, or Google decides it adds too little to keep.
Report statuses at this stage
- Crawled – currently not indexed
- Duplicate without user-selected canonical
- Duplicate, Google chose different canonical than user (this page)
- Alternate page with proper canonical tag
- Page with redirect
- Soft 404
- Excluded by ‘noindex’ tag
Serve
Indexed pages can appear in search results. Being indexed is not the same as ranking; an indexed page can still get no clicks.
What goes wrong: The page is indexed but doesn’t match what people search for, or other pages answer it better.
Report statuses at this stage
Read the result carefully. If your page names itself as canonical, Google thinks it duplicates the URL Google chose. If it names another URL, Google thinks that URL isn’t the right representative.1
Is it a problem?
Often not. Mueller said in 2026 that Google picking another URL within a site happens all the time and the content remains findable. Whether to adopt Google’s choice is a separate decision.6
Usually fine
- Google chose a www, non-www or trailing-slash variant
- Google chose a URL that still shows in search
- A few URLs, steady over time
Worth fixing
- Google chose a page on another website
- Google chose a URL with different content or the wrong language
- Unique pages treated as copies of one another
- A sudden shift across many pages
Find the cause
Google’s own steps: inspect the URL, compare the “User-declared canonical” with the “Google-selected canonical”, then open all three pages in a browser.1 The live test can’t show canonical choice; use the indexed result.5
The canonical names a different page
If your declared canonical isn’t similar to the page, Google won’t ever choose it.1 Google names CMSs and plugins that output the wrong canonical as one source of this.4
Google thinks your page is a copy
With a self-referencing canonical, the status means Google grouped your page with another and preferred the other.1 Mueller has listed causes from Google’s side: little unique content next to the template, pages that fail to render, bot-check pages, and plain misjudgement. He said no tool explains the decision and the systems aren’t perfect.8
Your signals point in different directions
Google ranks redirects as the strongest signal, canonical tags as strong and sitemaps as weak, and says not to name different URLs with different methods.3 Illyes has said redirects carry more weight than HTTPS, and that PageRank still counts.7
Everyone links to another variant
Martin Splitt gave the example of a site using www while external sites link to the non-www version. Google may pick the shorter, more-linked URL, and adopting it can be the cleaner option.6
A copy on another site won
Google lists hacked sites, syndication and copycats among the causes. If the canonical is in a Search Console property you don’t own, you won’t see its traffic.4
Why Google overrides a canonical
Select a reason to see what Google says about it and how to check for it.
The pages aren’t similar
A canonical tag tells Google the page is a copy of the target. If the target has different content, Google won’t use it: “A duplicate page must be similar to the canonical.”1
Check: open the page and the declared canonical side by side and compare the main content, ignoring menus and footers.
Other signals disagree
Redirects, canonical tags and sitemaps all count, and Google warns against naming different URLs with different methods.3 Gary Illyes has said Google weighs over twenty signals, including PageRank.7
Check: the sitemap URL, internal links, redirects and hreflang should all use the same URL as the canonical tag.
HTTPS and certificates
Google prefers HTTPS as canonical. Invalid certificates, HTTPS-to-HTTP redirects, or a certificate issued for the wrong host make Google prefer HTTP, and HSTS can’t override that.3
Check: load both versions of the URL. The certificate must match the exact host, and http must redirect to https.
hreflang and regional pages
Google prefers URLs that are part of a reciprocal hreflang cluster.3 Regional versions in the same language are duplicates unless you annotate them, and Google suggests hreflang for them.4 The canonical should be in the same language as the page.3
Check: every hreflang alternate links back, and no page’s canonical points to another language or region.
JavaScript changes the canonical
Google says not to use JavaScript to change the canonical to something different from the one in the original HTML. If JavaScript injects one, it must be the only canonical on the page.9
Check: compare the canonical in View Source with the one in the browser’s element inspector.
CMS or plugin bug
Google names content management systems and plugins that output the wrong canonical or redirect as a common cause.4
Check: inspect the HTML on several templates: home, category, product, article, paginated pages.
Hacking, copies and syndication
Attackers sometimes inject a redirect or a cross-domain canonical. Google may also pick a syndication partner’s or a copycat’s URL.4 Mueller has described bot-check pages served with a 200 status leading Google to pick another site’s page as canonical.6
Check: look for canonical tags, Link headers or redirects to domains you don’t control.
How to fix it
- Inspect the URL and decide whether Google’s choice is acceptable. If it is, you can stop, or update your canonical to match.6
- Point the canonical at a page with the same content, or at the page itself.1
- Make the sitemap, internal links, hreflang and redirects use the same URL.3
- Redirect variants visitors don’t need with a 301 or 308, and check the HTTPS certificate.3
- If Google thinks two distinct pages are copies, make the main content clearly different.4
- Request indexing for the most important URLs. It’s subject to a quota.4
How long it takes
- Up to 2 weeksfor Google to re-evaluate a duplicate cluster after you change the content.4
- Days to weeksfor Google to recrawl a page after a request.10
- Up to about 2 weeksfor Search Console to validate a fix, sometimes much longer.1
Compared with “Duplicate without user-selected canonical”
| Duplicate, Google chose different canonical than user | Duplicate without user-selected canonical | |
|---|---|---|
| Did you declare a canonical? | Yes | No |
| What Google did | Overrode your choice1 | Chose on its own1 |
| First fix | Make every signal agree, or accept Google’s choice | State a preference with a redirect or canonical tag |
Questions
Why does Google ignore my canonical tag?
Because a canonical is a hint, not an instruction. Google ignores it when the target isn’t similar to the page, when other signals like redirects, sitemaps and internal links point elsewhere, or when it thinks another URL is a better representative.
Should I change my canonical to the one Google chose?
It’s up to you. If Google’s choice is a reasonable URL and it shows in search, accepting it is often the simplest fix. If you need your URL, make every signal point to it and redirect the alternative.
Is my content still in Google?
Usually yes. Google indexed the URL it chose, so the content can still be found, just under that address. Check the chosen URL with URL Inspection and look for it in the Performance report.
What is the difference from “Duplicate without user-selected canonical”?
In both, Google indexed another URL. Here you declared a canonical and Google overrode it. In the other status you declared nothing and Google chose on its own.
How long does it take Google to accept my canonical?
Google says pages can stay in a duplicate cluster for up to two weeks after you fix content issues, and recrawling can take days to weeks. Making the difference between pages clear speeds it up.
Can the live test in URL Inspection tell me if it worked?
No. Canonical choice is made at indexing time, and the live test can’t predict it. Check the indexed result after Google recrawls the page.
Sources
- Google, “Page indexing report”, Search Console Help
- Google, “What is URL canonicalization”, Search Central, updated August 2026
- Google, “How to specify a canonical URL with rel=“canonical” and other methods”, Search Central, updated July 2026
- Google, “Fix canonicalization issues”, Search Central, updated August 2026
- Google, “URL Inspection tool”, Search Console Help
- John Mueller and Martin Splitt (Google), Search Off the Record episode 112, “How to read the Indexing Report”, July 2026 (transcript)
- Gary Illyes (Google), Search Off the Record, 2020, reported by Search Engine Journal, November 2020
- John Mueller (Google), Reddit r/bigseo, reported by Search Engine Journal, April 2026
- Google, “Understand the JavaScript SEO basics”, Search Central, updated March 2026
- Google, “Ask Google to recrawl your URLs”, Search Central, updated December 2025