IndexVerdict
Canonicalization

Duplicate without user-selected canonical

Google sees this page as a duplicate and has selected another version. Decide which version should represent the content before trying to get both indexed.

Troubleshooting guide · Public signals and practical next steps

What this means

Search Console reports duplicate content without a user-declared canonical preference for this URL. Google selected a different canonical.

When it’s normal—and when to investigate

Often expected

Tracking parameters, printer views, and alternative routes can show the same content. It is usually appropriate for one version to represent that content in search.

Worth investigating

Act if the wrong page is selected, your preferred page is excluded, or different systems send conflicting signals about which URL is primary.

Work through these checks

  1. Compare both versions in URL Inspection

    Read the Google-selected canonical in the recorded inspection result when available. Open the duplicate and preferred page and compare their main content and purpose.

  2. Inspect the declared canonical

    Check the raw HTML and HTTP Link header. Resolve relative URLs carefully, especially when a base element changes how they are interpreted.

  3. Check for conflicting signals

    Does the canonical point to a redirect, a missing page, or a noindex page? Do navigation links and sitemap entries prefer a different version? Check the destination separately.

  4. Decide whether both pages need to exist

    If one version is unnecessary, a relevant permanent redirect may be simpler. If both serve users, keep them accessible and declare a consistent preference where appropriate.

FREE URL DIAGNOSTICOne page. Public signals.

Use a public HTTP or HTTPS URL. No login needed. Don’t submit private links or URLs containing access tokens.

HTTP & redirectsCrawl & index controlsCanonical & content

Common causes

  • Tracking or filter parameters reproduce the same main content.
  • A template omits canonical tags.
  • HTTP, HTTPS, www, and non-www variants remain accessible.
  • Different routes publish substantially equivalent pages.

Possible fixes

  • Declare the preferred absolute URL with rel="canonical" on duplicate versions.
  • Use a self-referencing canonical on the preferred page and ensure it works.
  • Update internal links and sitemaps to favor that version.
  • If the pages truly serve different purposes, make their useful content distinct rather than only changing headings.

Make changes that match the page’s intended purpose. A technically valid page is not guaranteed to be indexed.

What this tool can and cannot verify

It can

Find declared HTML and basic HTTP canonicals, resolve their URLs, and compare them with the submitted and final URLs.

It cannot

See Google’s chosen canonical, compare content across the whole site, or guarantee that a declared preference will be followed.

Google’s own indexing status is available through Search Console / URL Inspection for a verified property. The live test and the recorded indexing report answer different questions.

A useful follow-up

Should I add noindex to the duplicate?

Do not use noindex as a substitute for expressing a canonical preference. Choose the consolidation method that matches the purpose of the duplicate and keep signals consistent.

Official reference: Google: Consolidate duplicate URLs. See also the Page indexing report documentation.