Duplicate without user-selected canonical: how to fix it

What the status means

In the Page indexing report, Duplicate without user-selected canonical means: this page is a duplicate of another page, it has no canonical tag of its own, and Google has chosen the other page as the canonical. The listed URL isn't indexed; the one Google chose is.

Google describes this as working as intended, not as an error. You only need to act in two cases:

• Google chose the wrong URL, for example a parameter version instead of the clean one, or an http:// page instead of https://.
• The page isn't really a duplicate. It's a distinct page whose content is too similar to another, such as two near-identical location pages or products that differ only in a name.

Duplicates aren't a penalty. Google's documentation says some duplicate content is normal and isn't a violation of its spam policies. The cost is control: without a canonical, Google decides which URL appears in results and where links and signals are consolidated.

How it differs from similar statuses

Why duplicates appear

Google lists the usual sources: region variants, device variants, protocol variants, and site functions such as sorting and filtering. In practice, the URLs in this report tend to be:

• Protocol and host variants: http:// and https://, or www and non-www, both answering with 200 instead of one redirecting.
• Trailing slash and case variants: /shoes and /shoes/, or /Shoes/, all returning the same page.
• Index files: /about/ and /about/index.html.
• Parameters: tracking codes, session IDs, sort orders and filters on pages that have no canonical tag.
• Templates with little unique content: tag and archive pages listing the same posts, empty category pages, or location pages that differ only in the city name.
• Copied or syndicated text on your own site, such as the same description on many products.

How to find the duplicates

Start in Search Console. Export the example URLs from the report, then run a few through URL Inspection: under Page indexing, it shows User-declared canonical (here, "None") and the Google-selected canonical. That tells you which URL Google preferred.

Search Console only shows samples. To find every duplicate group on the site, and which canonical each page declares, crawl it:

The checker groups exact and near-duplicate pages, marks groups that are already handled by a canonical, noindex or hreflang, and suggests the URL to keep: the clean version, without parameters or index.html. The Website SEO Audit also flags pages with missing canonical tags and duplicate titles across the site.

How to fix it

Work through the groups one at a time. For each, decide which URL should be in search, then use the strongest signal that fits:

1. Redirect variants that shouldn't exist. If http://, non-www, trailing-slash or index.html versions return 200, set up a permanent redirect (301 or 308) to the one true URL. Google calls a redirect a strong signal that the target should be canonical. Verify with the Redirect Checker.
2. Add a canonical tag to pages that must stay reachable. Parameter, sorted and filtered URLs need to work for visitors, so they can't redirect. Give every page a rel="canonical" tag: the clean URL on the clean page (self-referencing), and the clean URL on every variant.

   <link rel="canonical" href="https://example.com/shoes/">

3. Make similar pages different. If the pages are genuinely distinct, such as service pages for different cities, give each one substantial unique content. Google says pages with clear, significant differences are separated more easily.
4. Consolidate pages that serve no purpose. Two thin tag pages listing the same three posts are better merged, with a redirect from the one you remove.
5. Keep your other signals consistent. List only canonical URLs in your XML sitemap and use them in internal links. Google's documentation warns against giving different canonical URLs through different methods, such as a sitemap URL that differs from the canonical tag.
6. Don't use noindex or robots.txt to hide the duplicates. Google advises against both for canonicalization: noindex removes the page from search entirely, and a URL blocked by robots.txt can still be indexed without its content.

After the changes, use URL Inspection on the most important URLs and request indexing. Google may hold pages in a duplicate cluster for a while; its documentation mentions up to two weeks.

WordPress, Shopify and Next.js

WordPress

WordPress adds a canonical tag to single posts and pages, and SEO plugins such as Yoast and Rank Math extend it to archives and the homepage. If you see this status on a WordPress site, check for parameter URLs on pages without a canonical, a theme that removes the default tag, or an SEO plugin that has been disabled.

Shopify

Shopify themes output a canonical tag through canonical_url in theme.liquid. If URLs show this status on a Shopify store, check that a theme edit or app hasn't removed that line. Otherwise, the usual cause is near-identical product or collection pages, which need their own descriptions.

Next.js

Next.js doesn't add a canonical tag on its own. In the App Router, set it per page with the metadata API: alternates: { canonical: '/shoes/' }, together with metadataBase in the root layout, so the tag is written as a full URL. Also pick one trailing-slash style with the trailingSlash option, so both forms aren't served.

Questions