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

Google crawled the URL, recognised that its content is the same as or very similar to another page, and found no rel=canonical tag telling it which to prefer. It grouped the pages, chose one as canonical, and left this one out of the index. URL Inspection shows which URL Google selected.

The usual sources of unmarked duplicates are listed below.

Choose the version with the cleanest URL, the strongest internal links, and the content you want shown. If Google already selected that version, the status is informational and you can declare a canonical to make the choice explicit. If Google chose a different version, you need to make your preference unambiguous.

Add a self-referencing rel=canonical to the preferred URL in the server-rendered HTML. Redirect true duplicates, such as protocol and host variants, permanently. Point internal links only at the preferred URL. List only canonical URLs in the sitemap. Remove or substantially differentiate near-duplicate pages that have no reason to exist separately.

Canonical tags are a strong hint, not a command. When redirects, links, and the sitemap all agree, Google almost always follows the declared choice.

If the duplicates are separate pages that differ only by a word or two, for example location pages built from one template, a canonical just hides the symptom. Consolidate them into one stronger page or give each genuinely distinct content. In October 2026 we merged sixteen overlapping pages on serionflow.com into the pages that already held their intent and redirected the old URLs, rather than leaving Google to choose. SerionFlow is the wrong tool for repairing duplicates on your existing pages; it blocks new pages that duplicate an intent, but merging and redirecting your own URLs stays with your team.