“Duplicate without user-selected canonical” is a reason Google Search Console gives for not indexing a page. It means Google found the page, decided it is a duplicate of another URL, and noticed that the page doesn't say which version should be indexed, because it has no canonical tag. So Google picked the main version itself and left this one out.
That's often harmless: the URL listed may be a variant you never wanted indexed, such as a parameter URL. It becomes a problem when the page Google left out is the one you wanted in search results, or when hundreds of these variants are being crawled.
Where you see it
In Search Console, open Indexing → Pages and look under Why pages aren't indexed. Click the row to see example URLs. It sits alongside two related statuses that are easy to confuse:
| Status | What it means |
|---|---|
| Duplicate without user-selected canonical | The page has no canonical tag; Google chose another URL as the main version. |
| Duplicate, Google chose different canonical than user | The page has a canonical tag, but Google disagreed and picked a different URL. |
| Alternate page with proper canonical tag | The page points to another URL as canonical, and Google agrees. Usually fine; see Alternate page with proper canonical tag. |
Step 1: find out which URL Google chose
- Copy one of the example URLs from the report.
- Paste it into the URL Inspection bar at the top of Search Console.
- Expand Page indexing and look at User-declared canonical (it will say None) and Google-selected canonical.
The Google-selected canonical tells you what happened. If it's the version you want indexed, Google got it right and the flagged URL is just a variant. If it's a URL you don't want, such as a parameter or http:// version, or a different page altogether, you need to send clearer signals.
Common causes
Most duplicates come from the same content being reachable at more than one URL:
- Protocol and host variants:
http://andhttps://,wwwand non-www, all returning 200 instead of redirecting. - Trailing slashes and case:
/pageand/page/, or/Pageand/page, serving the same content. - URL parameters: sorting, filters, tracking tags (
?utm_source=), session IDs,?ref=and?replytocom=in WordPress comments. - Index files:
/folder/and/folder/index.html. - Faceted navigation: category pages filtered by colour, size or price, which can produce thousands of near-identical URLs.
- Print, AMP or feed versions of a page without a canonical.
- Near-duplicate pages: templated location or product variant pages where only a word or two differs. Google may treat these as duplicates even though the URLs are “real” pages.
How to fix it
1. Add a self-referencing canonical to every page
Each indexable page should declare itself as canonical with an absolute URL:
<link rel="canonical" href="https://example.com/blue-widgets/">
Duplicates and variants should point to the main version. Most CMSs and SEO plugins do this automatically; if yours doesn't, it's usually a single template change. Check what a page actually outputs with the Canonical Tag Checker, which also compares the raw HTML to the rendered page and catches JavaScript-only canonicals.
2. Redirect variants that should never exist
For protocol, host, trailing-slash and case variants, a 301 redirect is stronger than a canonical, because visitors and crawlers never see the duplicate at all. Make sure each variant reaches the final URL in a single hop; the Redirect Checker confirms it. Which code to use is covered in 301 vs 302 redirects.
3. Stop linking to duplicates yourself
Google often finds parameter URLs through your own internal links: a sort drop-down rendered as links, tracking tags on internal banners, or a mix of /page and /page/ in navigation. Link to the canonical URL everywhere, and list only canonical URLs in your XML sitemap. Conflicting signals are the main reason Google ignores a canonical tag.
4. Make near-duplicates genuinely different, or merge them
If Google groups pages you consider distinct, such as city pages that differ only by the city name, adding canonical tags won't make Google index both. Either give each page substantial unique content, or merge them into one stronger page and redirect the others.
5. Validate the fix
After deploying, inspect a few affected URLs with URL Inspection and choose Request indexing for the important ones. In the Page indexing report, open the issue and click Validate fix. Google re-crawls the examples over the following days or weeks; the count falls as it processes them.
When you can ignore it
If the Google-selected canonical is the URL you want indexed and the flagged URLs are variants nobody should land on, such as tracking parameters or ?replytocom links, the report is simply describing what Google filtered out. Adding canonical tags is still good practice because it puts the choice in your hands, but there's no ranking problem to solve. The count in this report also never reaches zero on most sites, and that's expected.
Frequently asked questions
Does “Duplicate without user-selected canonical” mean I have duplicate content penalties?
No. Google doesn't penalise ordinary technical duplication; it just picks one version to index. The risk is that it picks a version you don't want, or wastes crawling on variants.
Should I noindex the duplicate URLs instead?
Usually not. A noindex removes a URL from results but doesn't tell Google which version is preferred, and noindex combined with a canonical sends mixed signals. Use a canonical tag or a redirect.
Should I block the parameter URLs in robots.txt?
Only for parameters that create effectively infinite crawl paths, such as faceted filters. Blocked URLs can't pass their signals to the canonical, and Google can't see a canonical tag on a page it isn't allowed to crawl. Test any rule with the Robots.txt Tester before deploying it.
How long until the status clears?
It depends on how often Google crawls the affected URLs. Frequently crawled pages update within days; old parameter URLs Google rarely revisits can stay in the report for months without causing harm.



