Duplicate Without User-Selected Canonical: Pick One and Align Signals

The Search Console status "Duplicate without user-selected canonical" says that Google considers a page a duplicate of another page, you did not tell Google which version you prefer, and Google therefore picked one itself. The page in the report is not shown in search results. The page Google chose is.

For some sites this is fine, because Google's choice matches theirs. For others it is a quiet loss: a product page, a landing page or a language version you wanted in search is being treated as a copy of something else. This guide is for site owners and developers who need to decide which case they are in, choose a preferred URL, declare it clearly, and make every other signal agree. You will also learn what to do if the page is not really a duplicate. A canonical tag is a strong hint, not an order, so the guide ends with how to check what Google finally selected.

Before you begin

You need Search Console access, the ability to edit page templates or HTTP headers, and the ability to change redirects and the XML sitemap. Use a browser to view page source, and note which pages Google lists.

Set aside an hour for the review and a couple of weeks for the effect. Google's canonicalization troubleshooting guidance says pages can stay in a duplicate cluster for up to two weeks after you fix them, and that clear, significant differences split pages out faster. Before editing templates, save the current versions. Canonical tags are applied across many pages at once, so a mistaken template change can mark thousands of pages as duplicates of one URL.

What the status means

Google's Page Indexing help defines the status: the page is a duplicate of another page, it does not declare a preferred canonical, and Google chose a different page as the canonical, so it will not serve this one. Google says this is not an error. If Google picked the wrong canonical, you should explicitly mark the one you want. If the page is not really a duplicate, you should make its content differ substantially.

Two similar statuses cause confusion:

Alternate page with proper canonical tag. The page declares a canonical and Google agrees. See Alternate Page With Proper Canonical Tag.
Duplicate, Google chose different canonical than user. You declared a canonical, but Google selected another URL. Google's help says to use URL Inspection to compare the Google-selected canonical with your declared one, and notes that Google will not choose a declared canonical that is not similar to the duplicate page.

Our status is the one with no declaration at all.

Step-by-step instructions

Step 1: List the affected URLs and find the pairs

In Search Console open Indexing, then Pages, and select "Duplicate without user-selected canonical". Pick a URL and inspect it in the URL Inspection tool. In the indexing section, read the "Google-selected canonical". That is the page Google treats as the main version. Write each pair as "this URL, so it duplicates that URL".

What success looks like: For a sample of affected URLs you know which page Google chose as the canonical.

Step 2: Decide whether they are true duplicates

Open both pages and compare the main content. There are three outcomes.

True duplicates. The same content is reachable at two addresses, for example with and without a trailing slash, with a tracking parameter, or on http:// and https://. You need to declare one preferred URL.
Near duplicates that should be separate. Two product variants, two city pages or two category pages share most of their text. If you want both in search, make each page substantially different and useful, for example with unique descriptions, details and images. The thin and duplicate content guide discusses how to judge this.
Unrelated pages that look the same to Google. A misconfigured server or an error template can make unrelated pages look identical. Google's troubleshooting page notes that unrelated servers can return identical soft 404 pages. Check soft 404 errors if the pages show an error message.

What success looks like: Every pair is labelled true duplicate, near duplicate to differentiate, or misconfiguration.

Step 3: Choose the preferred URL

For true duplicates, choose the address you want in search. Prefer the one that is shorter, cleaner, on HTTPS, uses the host you have settled on, and receives the most internal links. Google says it prefers HTTPS unless there are conflicting signals, so choose the HTTPS version if your site is secure. Make the choice once and write it down, so templates, redirects and sitemaps can all use it.

What success looks like: There is one documented preferred URL for each page.

Step 4: Declare the canonical

Add a rel="canonical" link element in the <head> of each duplicate, pointing to the preferred URL, and a self-referential canonical on the preferred page itself:

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

Follow Google's advice for these tags:

Use an absolute URL, not a relative path.
Keep the tag inside a valid <head>.
Use only one canonical method per page. Google allows an HTTP header for non-HTML files such as PDFs, but warns against using both the element and the header, since they can disagree.
Do not use a URL fragment (the part after #) as the canonical.
For JavaScript-rendered pages, put the canonical in the HTML source if you can.

If the duplicate has no reason to exist, a permanent 301 redirect to the preferred URL is a stronger signal than a canonical tag, according to Google's documentation. See 301 vs 302 redirects for the choice of code.

What success looks like: View-source on a duplicate shows one canonical pointing at the preferred URL.

Step 5: Make every other signal agree

Google weighs several signals together: redirects are strong, the rel="canonical" element is strong, and sitemap entries are weak. Conflicts between them cause the exact uncertainty that leads to this status. Check each of these:

Internal links. Link to the preferred URL everywhere. Google recommends linking internally to the canonical rather than to duplicates.
Sitemap. List only the preferred URLs. Do not name a sitemap URL that differs from the rel="canonical" URL.
Protocol and host. Redirect HTTP to HTTPS and the non-preferred host to the preferred host so only one version stays reachable.
Parameters. If tracking or sorting parameters create copies, canonicalise them to the clean URL or stop linking to them. See faceted navigation and URL parameters.
Hreflang. For sites with language versions, Google says the canonical should match the page's language or the closest substitute, and that pages joined by reciprocal hreflang links are preferred over pages outside the cluster. Use rel="alternate" for language versions, not canonical attributes.

Do not use robots.txt to settle which duplicate wins. Google says disallowed URLs can still be indexed without their content. Do not use the URL removal tool either, since it hides all versions. And avoid noindex for choosing between duplicates on one site, because it removes the page from search altogether.

The duplicate URLs and canonical tags guide walks through the redirect side of this in more detail.

What success looks like: Redirects, canonical tags, links and the sitemap all name the same URL.

Step 6: Differentiate pages that are not really duplicates

If Step 2 showed pages that should stand on their own, change them so they do. Rewrite the shared text, add information that is specific to each page, and make sure the titles and headings describe what is unique. Merging is also a legitimate answer: if two pages say the same thing, combine them and redirect the weaker URL.

Differences must be real. Changing a few words in a boilerplate paragraph is unlikely to separate pages that otherwise match. Google's guidance is to make the clustered pages sufficiently different from one another.

What success looks like: Pages that should rank separately each have distinct main content.

Step 7: Recheck and wait

After the changes are live, inspect an affected URL again. The user-declared canonical should show your preferred URL, and the Google-selected canonical should follow in time. Request indexing only for your most important URLs, because Google says it has quotas; see Request Google Indexing the Right Way. Expect the status to clear over days to weeks, not minutes. Google's help also says that if you fix all instances, you can use Validate fix once and wait for it to finish.

What success looks like: The user-declared canonical matches your choice, and the report count falls as Google recrawls.

Final verification checklist

Each affected URL is labelled true duplicate, near duplicate or misconfiguration.
Each page has one documented preferred URL.
Duplicates carry a canonical element pointing to that URL, or redirect to it.
The preferred page has a self-referential canonical.
Canonical URLs are absolute and use HTTPS where available.
Internal links and the XML sitemap use the preferred URL only.
No page uses both an HTML canonical and a conflicting header.
Pages meant to be separate have clearly different main content.

Common mistakes to avoid

Treating the status as an error on every page. Google says it is not an error. Act only when Google's choice is wrong.
Pointing different methods at different URLs. Canonical tag, sitemap and redirects must agree.
Using relative canonical URLs. Use absolute URLs.
Setting every canonical to the home page. The tag claims that all pages are copies of the home page.
Using noindex to pick a winner. It removes the page from results instead of consolidating signals.
Blocking duplicates in robots.txt. Blocked URLs can still be indexed, and the tag cannot help.
Making trivial edits to separate near-duplicates. Pages need real differences in useful content.
Requesting indexing for every URL. Quotas apply. Request only your most important pages.

Frequently asked questions

Is this status bad for SEO?

Not by itself. It means Google picked one version of duplicate content to show. It matters when Google's pick is not the page you want.

What is the difference between this and "Alternate page with proper canonical tag"?

With an alternate, you declared a canonical and Google agreed. With this status, you declared nothing and Google chose for you.

Do I always need a canonical tag?

Google says that if you do not specify one, it chooses the version it considers best, and many sites do fine this way. A self-referential canonical on each page is a sensible default.

Will adding a canonical remove the page from the report right away?

No. Google may hold pages in a duplicate cluster for up to two weeks after fixes. Clearer content differences split them faster.

Can Google ignore my canonical?

Yes. Google says it might choose a different canonical even when you designate one, for example because of conflicting signals or pages that are not similar.

What if the page is a syndicated copy on another site?

Google's troubleshooting page says canonical tags are not the recommended way to handle syndication, and that partners should block indexing instead. See cross-domain canonical and syndication.

Official references

Next step: See how Crawvix checks a website and capture a baseline once scanning opens. This guide provides technical information, not a guarantee of rankings, traffic or index inclusion.