Quick answer: "Duplicate without user-selected canonical" means Google found several URLs with the same (or nearly the same) content, none of them told Google which one is the main version, so Google picked one itself and left this URL out of search. It is often harmless. Fix it only when Google picked the wrong URL, or when the page is not really a duplicate. The fix is usually a self-referencing rel="canonical" tag on the preferred page, canonical tags or 301 redirects on the copies, and internal links and a sitemap that only use the preferred URL.
What the duplicate without user-selected canonical status means
You see this status in the Page indexing report of Google Search Console. In Google's own words, the page "is a duplicate of another page, although it doesn't indicate a preferred canonical page." Google has chosen another URL as the canonical (the main version) and "will not serve this page in Search."
The key phrase is user-selected. You (the user) never declared a canonical URL, so Google had to decide on its own. Google's documentation is clear that this is "not an error, but is working as intended, because Google does not serve duplicate pages."
Should you fix it or ignore it?
Start by asking one question: is the URL Google chose the one you want people to land on?
- Yes, Google chose the right page. Leave it. The duplicate is out of the index, which is what you want. Adding a canonical tag is still good hygiene, but nothing is broken.
- No, Google chose the wrong page. For example, it chose the version with a tracking parameter, or the
http://version. Fix it with the steps below. - The page is not a duplicate at all. For example, two product pages that only differ by a color name. Make the content substantially different, as Google recommends, or merge the pages.
Google's help center also reminds site owners that most sites have at least a few unindexed pages, and that duplicate URLs shouldn't be indexed. A handful of these URLs is normal. A sudden spike after a site change is worth investigating.
Common causes of duplicate URLs
Most cases come from the same page being reachable at more than one address:
- Protocol and host variants:
http://andhttps://, orwww.example.comandexample.com, all serving the same page. - URL parameters: sorting and filtering (
?sort=price,?color=green), session IDs, or tracking tags such as?utm_source=and?gclid=. - Trailing slashes and file names:
/pricing,/pricing/and/pricing/index.htmlreturning the same content. - Uppercase and lowercase paths:
/Blog/Postand/blog/poston servers that treat them as the same page. - Printer-friendly or AMP versions without a canonical pointing back to the main page.
- Near-duplicate templates: location pages, tag pages or product variants with almost identical text.
How to fix it, step by step
1. Find out which URL Google picked
In Search Console, open the Page indexing report, click Duplicate without user-selected canonical and inspect an example URL with the URL Inspection tool. Under the indexing details you will see the Google-selected canonical. Compare it with the URL you want to rank. Group the affected URLs by pattern (parameters, www, trailing slash), because one template fix usually solves the whole group.
2. Choose one preferred URL for each page
Decide on the single version you want in search results, for example https://example.com/dresses/green-dresses: HTTPS, one host, one trailing slash style, no parameters. Write this rule down so your whole team links the same way.
3. Add a self-referencing canonical tag to the preferred page
Google recommends putting a rel="canonical" link on the canonical page itself (a self-referential canonical). Place it in the <head>, and use an absolute URL:
<head>
<title>Green dresses</title>
<link rel="canonical" href="https://example.com/dresses/green-dresses" />
</head>
Most CMSs and SEO plugins can add this automatically. Check the live HTML afterwards: Google only accepts the canonical link if it appears in the <head>. You can confirm it in seconds with our free canonical tag checker.
4. Point the duplicates to the preferred URL
For copies that need to stay reachable (filtered views, tracking URLs, print pages), add the same canonical tag pointing to the preferred URL. For copies that should not exist at all (HTTP, www or old URLs), use a permanent 301 redirect. Google describes redirects as a strong signal that the target should become canonical. On Apache, a redirect to HTTPS and the non-www host can look like this:
RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} ^www\. [NC]
RewriteRule ^ https://example.com%{REQUEST_URI} [L,R=301]
After you deploy it, test a few old addresses with the URL redirect checker to make sure each one lands on the final URL in a single 301 hop, with no chains or loops.
For non-HTML files such as PDFs, you can send the canonical as an HTTP header instead:
HTTP/1.1 200 OK
Link: <https://example.com/downloads/guide.pdf>; rel="canonical"
5. Make every other signal agree
Canonical tags work best when the rest of your site sends the same message:
- Internal links: link to the preferred URL everywhere, including menus, breadcrumbs and buttons.
- Sitemap: list only canonical URLs. Google treats sitemap inclusion as a weaker signal, but a sitemap full of parameter URLs works against you. Run your sitemap through the sitemap checker.
- hreflang: if you have language versions, each one should have a canonical in the same language, not a canonical pointing to the English page.
- HTTPS: Google prefers HTTPS pages as canonical unless something conflicts, such as an invalid certificate or a redirect back to HTTP.
6. Make unique pages truly unique
If the flagged URL deserves its own place in search, give it content that clearly differs from the page Google grouped it with: its own title, headings, description, images and copy. Otherwise, merge the two pages and redirect the weaker one.
7. Validate the fix and give it time
Back in the Page indexing report, click Validate fix. Google says validation typically takes up to about two weeks, and sometimes longer. You don't need to request indexing for every URL. Google rechecks the affected pages as it crawls them.
Mistakes to avoid
These come straight from Google's canonicalization guidelines:
- Don't use
robots.txtto handle duplicates. Blocked URLs can still be indexed without their content. - Don't use
noindexto choose a canonical within one site. It removes the page from Search entirely. - Don't use the URL removal tool for canonicalization. It hides all versions of a URL.
- Don't send mixed signals, such as one URL in the sitemap and a different one in the canonical tag.
- Don't use a URL fragment (
#section) as the canonical, and avoid relative canonical paths. - Don't let JavaScript change a canonical tag that is already in the HTML source.
Check your pages for free with Page Behavior
Duplicate URLs usually show up next to other problems: missing canonical tags, redirect chains, stray noindex tags and messy sitemaps. A Page Behavior audit checks for a missing canonical tag along with titles, meta tags, headings, links, images and speed, then explains each fix in plain language. If you suspect a page is blocked by mistake, the noindex checker gives you an answer in seconds.
Want a quick look first? Run a free SEO audit on any page, no account needed.
Create your free Page Behavior account to audit your pages and schedule re-audits. No credit card, no trial, no catch.
FAQ
Is duplicate without user-selected canonical bad for SEO?
Not by itself. It means Google is keeping one version of a page in its index and leaving copies out, which is how it is meant to work. It only hurts when Google keeps the wrong version, or when a page you want to rank is treated as a copy.
How is it different from Google chose different canonical than user?
With "without user-selected canonical", you never declared a canonical, so Google chose one. With "Google chose different canonical than user", you did declare one, but Google decided another URL is a better canonical. The second case often means the declared canonical is not similar enough to the page.
Should I use a canonical tag or a 301 redirect?
Use a 301 redirect when the duplicate URL should not exist for visitors (old URLs, HTTP, www variants). Use a canonical tag when the duplicate has to stay available, such as a filtered or tracked version of a page. Both are strong signals, and they work best combined with consistent internal links and a clean sitemap.
Does Google always follow my canonical tag?
No. Google treats rel="canonical" as a strong signal, not a command. It weighs it against redirects, sitemaps, internal links, HTTPS and content similarity. The more of these signals agree, the more likely Google picks your preferred URL.
How long does it take for the status to clear?
Google needs to recrawl the affected URLs. When you start a validation in Search Console, Google says it typically takes up to about two weeks, and in some cases longer.
Sources: Google Search Console Help, Page indexing report; Google Search Central, How to specify a canonical URL.