Key takeaways
- "Duplicate without user-selected canonical" means Google decided this page is a near-duplicate of another URL and chose that other URL as canonical, without treating your page's own tag as a real preference
- The textbook cause is no canonical tag at all, but a self-referencing canonical can trigger it too, because self-referencing doesn't tell Google anything about a duplicate pair
- Google explicitly calls this "not an error": it will not serve the page in Search, working as intended
- We checked our own site's live Search Console data while writing this and found two current examples, both with a genuine canonical tag in place today
"Duplicate without user-selected canonical" sits next to "Duplicate, Google chose different canonical than user" in the Page indexing report, and the two names are close enough to blur together. They describe different situations. This one specifically means Google didn't see your page express a preference at all, and that can happen even when your page carries a correct canonical tag right now, as two of our own pages currently show.
What "Duplicate without user-selected canonical" actually means
Google's own definition, from its Search Console Help documentation, is precise:
"This page is a duplicate of another page, although it doesn't indicate a preferred canonical page. Google has chosen the other page as the canonical for this page, and so will not serve this page in Search."
Google is also explicit that this is not an error: it's the system working as intended, because Google does not serve duplicate pages. The textbook cause is a page with no <link rel="canonical"> tag at all, sitting alongside a near-duplicate URL, so Google picks a canonical using its own signals since the page gave it nothing to go on.
Note
See Search Console indexing issues explained for how this status relates to the others in the same report, including "Duplicate, Google chose different canonical than user" and "Crawled - currently not indexed".
Real examples, checked this session, and the nuance they show
Two of our own pages currently carry this status, checked live via URL Inspection on 24 September 2026:
/guides/inspecting-a-url: last crawled 30 June 2026, fetch successful, and the page declares<link rel="canonical" href="https://crawlcove.com/guides/inspecting-a-url">today, self-referencing and correct./tools/utm-builder: last crawled 1 July 2026, fetch successful, Google's own recorded canonical choice is thewwwvariant, and the page also declares a correct self-referencing canonical today.
Neither page is missing a canonical tag. Both genuinely have one, pointing at the right URL. That looks like it should rule this status out, and it's worth saying plainly why it doesn't: a self-referencing canonical only asserts "I am canonical." It says nothing about a duplicate elsewhere, so it doesn't give Google the kind of cross-page preference this status is checking for. If a near-duplicate URL, such as a www or non-www variant, was ever live at the same time without a working redirect between the two, both copies could have self-referenced their own URL, and neither told Google which one should win.
Checked live today: https://www.crawlcove.com/guides/inspecting-a-url and https://www.crawlcove.com/tools/utm-builder both correctly 301-redirect to their apex equivalents in a single hop, with no internal link on the site pointing at either www URL. Whatever duplicate pairing produced this verdict, it isn't live today. Both pages' last crawl dates are roughly three months old, which fits a Google judgement that's trailing a fix already in place rather than describing today's site.
Why this happens
A few situations produce this status:
- No canonical tag published at all, on a page that closely overlaps another URL. This is the textbook case, and the one most guidance describes.
- A
www/non-wwworhttp/httpspair that once existed without a redirect, where each variant self-referenced its own URL. Neither pointed at the other, so Google had no stated preference to work from, even after a redirect later makes one of them the only live copy. - URL parameters or trailing-slash variants that render effectively the same content under different addresses, each self-canonicalising rather than pointing at one shared URL.
In every case, the common thread is the same: Google is not looking for a canonical tag, it's looking for a signal that this specific page should defer to that specific other one. A tag that only confirms the page's own URL doesn't supply that, however correct it is.
What actually helps
Check which URL Google currently considers canonical. URL Inspection shows this directly. If it's the URL you'd choose anyway, there may be nothing to do.
If you disagree with Google's pick, you can mark the canonical explicitly, but only if the page genuinely isn't a duplicate. If the content really does overlap substantially with the URL Google chose, changing the tag again is unlikely to change the outcome, since Google has already read a tag once and reached its own conclusion.
Rule out a live duplicate pair first. Check that www/non-www and http/https variants all redirect cleanly to one canonical URL in a single hop, and that nothing on the site links to the non-canonical form. This is the check that mattered for both examples above.
Give it time. If the underlying duplicate is genuinely gone, as it is for both pages here, the status reflects Google's last crawl, not the current state of the site. It updates on Google's own recrawl schedule, not on request.
Heads up
Don't confuse this with "Duplicate, Google chose different canonical than user." That status means Google actively overrode a real preference you stated. This one means Google never registered a preference from your page in the first place. The fixes look similar on the surface, consistent canonicalisation and clean redirects, but the diagnosis is different, and conflating them can send you editing a tag that was never the actual problem.
Seeing this across your whole site, not one URL at a time
Search Console's URL Inspection tool checks one URL at a time, which is fine for the two pages above but doesn't show you every page on a site carrying this status, or whether a www/non-www pair is quietly serving duplicate content somewhere you haven't checked.
Crawl Cove crawls your whole site to surface duplicate and near-duplicate pages and inconsistent internal links, and its Live Index Status feature calls Google's own URL Inspection API on demand for any URL, without checking one at a time by hand. Run a full SEO audit to see which of your pages are carrying this status and whether the underlying duplicate is still live.
If the cause on your site turns out to be a shared template rather than a one-off page, see how to catch canonical tag template bugs, including one we found and had to fix twice on our own site.
Wrap-up
"Duplicate without user-selected canonical" usually means a page never expressed a preference, most often because it had no canonical tag while sitting next to a near-duplicate URL. But a self-referencing canonical doesn't automatically clear it either, as our own two examples show: it only confirms a page's own identity, not its relationship to a duplicate elsewhere. Check what Google currently treats as canonical, confirm any www/non-www or protocol variants redirect cleanly to one URL, and treat a status tied to an old crawl date as Google catching up, not a fresh defect, once you've verified the duplicate itself is gone.
Frequently asked questions
- What does "Duplicate without user-selected canonical" mean?
- Google's own definition is that the page is a duplicate of another page, the page doesn't indicate a preferred canonical, and Google has chosen the other page as canonical instead, so this page won't be served in Search. Google states this is working as intended, not an error.
- Does this mean my page has no canonical tag?
- Not necessarily. The textbook cause is a missing canonical tag, but we found two of our own pages carrying this status with a genuine, correct, self-referencing canonical tag live today. A self-referencing tag only says "I am canonical" and tells Google nothing about a duplicate elsewhere, so Google can still discount it as not a real preference signal.
- How is this different from "Duplicate, Google chose different canonical than user"?
- That status means you declared a canonical pointing at a specific URL, and Google actively overrode it in favour of a different one, having weighed your tag against its own signals and rejected it. This status means Google didn't see your page express a preference against the duplicate at all.
- What should I check first?
- Use URL Inspection to see which URL Google currently treats as canonical for the page, then check whether an old URL variant, such as a www or non-www version, still exists or once existed as a live duplicate. If it's now a clean single-hop redirect, the status can simply be Google's judgement lagging behind a fix that's already live.
- Should I add or change the canonical tag?
- Only if the page genuinely differs from the URL Google picked. If it's truly the same content, the more useful fix is usually consistent internal linking to the one correct URL and patience while Google recrawls, not repeatedly editing a tag it has already read.