Duplicate without user-selected canonical: what it means, and when to fix it

It's one of the reasons listed under Why pages aren't indexed in the Page indexing report. Google's help defines it plainly: the 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, "and so will not serve this page in Search."

Three words in the status name do the work. Duplicate: Google's grouped this URL with at least one other that has the same or very similar main content. Without user-selected: nothing on the page, no canonical tag, HTTP header or sitemap entry, told Google which version you prefer. Canonical: so Google picked the representative URL by itself.

The next sentence in Google's help is the one most articles leave out: "This is not an error, but is working as intended, because Google does not serve duplicate pages." The report is telling you what Google did, not that something broke. Whether you act depends on which URL Google picked and whether you agree with it.

Because it only wants one copy of any piece of content in its results. Google's canonicalization documentation says that when it finds multiple pages that seem the same, or whose primary content is very similar, it clusters them, then marks as canonical the page it judges "objectively the most complete and useful for search users." The canonical gets crawled most regularly; duplicates are crawled less often.

Google names the signals that feed that choice: whether the page is served over HTTP or HTTPS, redirects, whether the URL is in a sitemap, and rel="canonical" annotations. With none of your own to go on, it uses whatever else it has. Even when you do declare one, Google says a canonical preference is "a hint, not a rule."

The same page lists the usual sources of duplicates: region variants, device variants, HTTP and HTTPS versions, sorting and filtering on category pages, and demo or staging copies left open to crawlers. It also says some duplicate content on a site is normal and isn't a breach of Google's spam policies. The cost is split signals and harder tracking, not a penalty.

Fix every instance first, then press Validate fix on the issue in the Page indexing report. Google's help says validation stops as soon as it finds a single remaining instance, and it typically takes up to about two weeks, though in some cases much longer. You don't have to validate at all: Google updates the count whenever it recrawls an affected page.

Content fixes take their own time. Google's canonicalization troubleshooting page says that even after you fix the content, it might hold pages in a duplicate cluster for up to two weeks, and pages split out faster when the difference is clear and significant. For the few URLs that matter most, Request Indexing in URL Inspection asks for a re-evaluation, but it's subject to quotas, so I save it for those.

One check after validation passes: inspect the URLs again and confirm the Google-selected canonical is now the one you wanted. A cleared count can also mean the URLs simply dropped out of Google's crawl, which isn't the same thing.