Coverage states
Fix "Duplicate without user-selected canonical" in Search Console
Search Console: "Duplicate without user-selected canonical" — Google chose a different URL.
Google found two or more URLs it considers the same page and, with no canonical from you, picked one itself — often the wrong one. Add a self-referencing canonical to the preferred URL, point all variants at it, keep your sitemap and internal links consistent, and 301-redirect variants where you can. Then verify the user-declared and Google-selected canonical match.
"Duplicate without user-selected canonical" means Google found two or more URLs it considers the same page, you didn't tell it which one is the real one, so Google chose for you. Sometimes it chooses well. Often it picks a tracking-parameter URL or a print version, and your preferred URL gets buried.
Why this happens
- URL parameters: ?utm_source=, ?ref=, ?sort=, session IDs — each creates a "new" URL with identical content.
- Trailing-slash and case variants: /page, /page/, /Page all serving the same thing.
- HTTP and HTTPS, or www and non-www, both resolving without a canonical signal.
- Pagination, faceted navigation, or printer-friendly versions duplicating the main page.
The fix: declare your canonical explicitly
- Add a self-referencing <link rel="canonical"> to every page pointing at the clean, preferred URL.
- Make sure parameter and variant URLs point their canonical at the same clean URL — not at themselves.
- Keep canonical URLs consistent with your sitemap: the sitemap should list only the canonical versions.
- Where possible, 301-redirect the variants (e.g. HTTP→HTTPS, non-www→www) so there's only one reachable URL at all.
Google treats rel=canonical as a strong suggestion, not a directive. If your "duplicates" are too different, or your internal links and sitemap contradict the canonical, Google may override you. Make every signal — canonical tag, internal links, sitemap, redirects — point the same way.
Verify Google accepted your choice
Run the preferred URL through a status check. The URL Inspection result shows both the "user-declared canonical" (what your tag says) and the "Google-selected canonical" (what Google actually chose). When those two match, you've won. If they still differ, your other signals are contradicting the tag — audit internal links and sitemap entries.
Then push the canonical to re-crawl
Once your signals agree, push the canonical URL through the Indexing API so Google re-crawls and re-evaluates the cluster sooner. The canonical & meta finder makes it quick to spot any straggler pages still pointing at the wrong URL.
IndexerNow runs on your own Google account, your own Cloud project, and your own quota — we never pool submissions through a shared account. Connect your GSC and push the URL through Google's Indexing API in two clicks.
Connect your own GSC and index nowFrequently asked
Why did Google pick a different canonical than my tag?
rel=canonical is a hint. If your internal links, sitemap, or redirects point at a different URL than your canonical tag, Google weighs all the signals and may override the tag. Make every signal agree, then it usually honours your choice.
How do I see which canonical Google chose?
URL Inspection (in Search Console or via the API) reports both the user-declared canonical and the Google-selected canonical for a URL. When they match, the issue is resolved.
Do I need to noindex the duplicates?
No. Canonical consolidation is the right tool for true duplicates — it passes signals to the canonical. Use noindex only for pages you never want indexed at all; for duplicates, canonical (or a 301) is cleaner.
Related fixes
Fix "Excluded by 'noindex' tag" when you didn't mean to block the page
Google obeyed a noindex directive on your page — but you never intended to add one. Here's how to find the accidental noindex and get the page back in the index.
Fix: "URL is not on Google" in URL Inspection
Search Console says "URL is not on Google" — here's what that verdict means, how to read the details, and the exact steps to get the URL indexed.
Fix "Blocked by robots.txt" in Google Search Console
"Blocked by robots.txt" means Google can't crawl your URL at all. Here's how to find the offending rule, fix it, and get the page indexed.