Duplicate Without User-Selected Canonical: What It Means in Search Console and When to Fix It
Google lists a page as a duplicate without user-selected canonical when it finds the same content at more than one URL and the page names no preferred version. Often nothing is wrong. Here is how to tell, the fix when something is, and a script that tests the six duplicate URLs most sites create.
Duplicate without user-selected canonical is a Search Console status for a URL that Google sees as a copy of another page, where the page doesn't name a preferred version with a canonical tag.
Google calls the status "not an error" and "working as intended": it shows one version of duplicate pages in search, so fix it only when Google picked the wrong version or the listed URLs should not exist.
Google ranks the signals it uses to pick a canonical: redirects and rel=canonical are strong signals, a sitemap is a weak one, and Google says not to use robots.txt or noindex for this.
In our Nov. 15, 2026 test of six common duplicate URLs on three sites, every site redirected http and www versions and served tracking-parameter URLs with a canonical tag pointing to the clean URL.
After a fix, use Validate fix in the Page indexing report; Google says validation can take about two weeks.
Duplicate without user-selected canonical is a status in Google Search Console's Page indexing report. Google's definition: "This page is a duplicate of another page, although it doesn't indicate a preferred canonical page." Google picked one version of the content to show in search and left this URL out.
Most of the time that is fine. Google's own help page says the status "is not an error, but is working as intended, because Google does not serve duplicate pages." It becomes a problem in two cases: Google kept the wrong version, or the listed URLs shouldn't exist at all. This guide shows how to tell which case you have and how to fix it, with a test you can run on your own site in a minute.
What does duplicate without user-selected canonical mean?
When Google finds the same, or nearly the same, content at more than one address, it groups the addresses and chooses one as the canonical: the version it indexes and shows. The others are duplicates.
"User-selected" means you. If the duplicate URL has no rel="canonical" tag (or the tag can't be read), you haven't told Google which version you prefer, so Google chose, and it reports the leftover URL under this status.
Common sources of these URLs:
http:// and https:// versions of the same page
www. and non-www. versions
with and without a trailing slash
tracking parameters such as ?utm_source=newsletter, and filter or sort parameters on shop category pages
print versions, session IDs, and copies on a staging or preview domain that search engines can reach
Is duplicate without user-selected canonical bad for SEO?
Not by itself. Google indexes one version and shows it, which is what you want. Google's help page also reminds site owners that "Not indexed is not necessarily bad."
It is worth acting on when:
Google's chosen version is the wrong one, for example the http:// page or a URL with a parameter.
The URL is an important page, such as a product or service page, that you expected to be indexed in its own right.
The list is large and growing, which usually means your site generates duplicate URLs, often from filters, parameters or internal links to the wrong version.
How do I see which version Google chose?
Use the URL Inspection tool. Google's help page says to inspect the URL "to see which URL Google considers canonical for this page." The result shows two lines: the user-declared canonical (yours, or none) and the Google-selected canonical.
In the "Why pages aren't indexed" table, click Duplicate without user-selected canonical.
Click an example URL and inspect it (the help page calls this the INSPECT button).
Compare the two canonical lines. If the Google-selected canonical is the page you want in search, you can usually leave it.
How do I fix duplicate without user-selected canonical?
Tell Google which version you want, using the signals it trusts most. Google's canonical guide ranks them:
Redirects: "a strong signal that the target of the redirect should become canonical." Use a permanent redirect (301 or 308; Google treats both as permanent) for versions nobody needs to visit, such as http:// and www. copies. Temporary redirects (302, 303, 307) don't count as a canonical signal.
rel="canonical": "a strong signal that the specified URL should become canonical." Use it for versions people do need, such as URLs with tracking parameters. Put <link rel="canonical" href="https://example.com/page"> in the <head> of every version, including the preferred page itself. Google says to pick the HTML tag or the HTTP header, not both.
Sitemap: "a weak signal." List only canonical URLs in your sitemap, but don't rely on it alone.
Two things Google says not to do: don't use robots.txt to hide duplicates (Google may still index a blocked URL without its content), and don't use noindex to choose a canonical within a site, because it removes the page from search completely.
Also fix the cause. If your own menus, internal links or sitemap point to the wrong version, Google keeps finding it. Link to the canonical URL everywhere.
Duplicate, Google chose different canonical than user: what's the difference?
That status means you did name a canonical, and Google disagreed: "This page is marked as canonical for a set of pages, but Google thinks another URL makes a better canonical." Google lists reasons it may override you, including conflicting signals (a canonical tag saying one thing and a redirect or sitemap another), its general preference for HTTPS over HTTP, URLs in hreflang clusters, and a canonical tag that only appears after JavaScript runs. Look for the conflict and remove it.
What does alternate page with proper canonical tag mean?
That one needs no work. Google's words: "This page correctly points to the canonical page, which is indexed, so there is nothing you need to do." It is what a tracking-parameter URL with a correct canonical tag should show.
Our test: six duplicate URLs on three sites
To see how well-run sites handle the usual duplicates, we wrote a short Node script that requests six versions of a URL and reports what each returns. On Nov. 15, 2026 we ran it on one of our own story pages, the WordPress.org News page and the Shopify blog:
Version requested
The Search Post
WordPress.org News
Shopify blog
Other protocol (http://)
301 to the https page
301 to the https page
301 to the https page
www. added or removed
301 to the main host
301 to the main host
301 to the main host
Trailing slash added or removed
308 to the main URL
301 to the main URL
301 to the main URL
?utm_source=test added
200, canonical to the clean URL
200, canonical to the clean URL
200, canonical to the clean URL
Uppercase path
404
301 to the main URL
404
All three did what Google recommends: permanent redirects for versions no one needs, and a canonical tag on the parameter version, which still has to load for tracking to work. An uppercase path returning 404 is fine too, since it creates no duplicate. We also found that our own preview copy (preview.thesearchpost.pages.dev) returns 200 for every page, but sends X-Robots-Tag: noindex and a canonical tag pointing to the live site, so it can't become a duplicate in Google.
We also ran two other large sites, and left them out of the table because their answers depended on our test location: Google's own documentation redirected some versions to other language editions, and one news site refused plain http:// requests from our data center.
Here is the script. It needs Node 18 or later and no packages; run node canonical-check.mjs https://example.com/your-page:
// canonical-check.mjs: request the common duplicate versions of a URL and report// what each returns. Node 18 or later, no packages. Usage: node canonical-check.mjs <url>const url = new URL(process.argv[2]);const swapWww = (h) => (h.startsWith('www.') ? h.slice(4) : `www.${h}`);const path = url.pathname;const variants = { 'as given': url.href, 'other protocol': url.href.replace(/^https?:/, url.protocol === 'https:' ? 'http:' : 'https:'), 'www swapped': url.href.replace(url.host, swapWww(url.host)), 'trailing slash': url.href.replace(path, path.endsWith('/') ? path.slice(0, -1) || '/' : `${path}/`), 'tracking parameter': `${url.origin}${path}?utm_source=test`, 'uppercase path': `${url.origin}${path.toUpperCase()}`,};for (const [label, href] of Object.entries(variants)) { try { const res = await fetch(href, { redirect: 'manual' }); const where = res.headers.get('location'); let canonical = ''; if (res.status === 200) { const html = await res.text(); canonical = html.match(/<link[^>]+rel=["']canonical["'][^>]*>/i)?.[0].match(/href=["']([^"']+)/i)?.[1] ?? 'none'; if (res.headers.get('link')?.includes('canonical')) canonical += ' (+ Link header)'; } const verdict = res.status >= 300 && res.status < 400 ? `redirects to ${where}` : res.status === 200 ? `200, canonical: ${canonical}` : `${res.status}`; console.log(`${label.padEnd(18)} ${res.status} ${verdict}`); } catch (e) { console.log(`${label.padEnd(18)} error ${e.cause?.code ?? e.message}`); }}
Our run on our own page printed:
as given 200 200, canonical: https://thesearchpost.com/topical-authorityother protocol 301 redirects to https://thesearchpost.com/topical-authoritywww swapped 301 redirects to https://thesearchpost.com/topical-authoritytrailing slash 308 redirects to /topical-authoritytracking parameter 200 200, canonical: https://thesearchpost.com/topical-authorityuppercase path 404 404
What to look for in yours: any line that says 200 with canonical: none, or a canonical that isn't your preferred URL, is a duplicate Google has to sort out on its own. Any 302 or 307 where you meant a permanent move should become a 301. The script reads the canonical tag from the HTML as served, so a tag added later by JavaScript shows as none, which is also how Google can miss it.
After the fix: validate it
Once every affected URL is fixed, open the issue in the Page indexing report and click Validate fix. Google says not to click it again until validation passes or fails, and that validation can take about two weeks. If it fails, See details shows the URL that caused it.
Kiran runs Kihan Marketing, a web design, SEO and ads agency, and manages dozens of websites across real estate, home services and healthcare. He writes about SEO, AI search and paid ads news, and what it means for the people who run websites.