knowledge base284 articles
knowledge base/seo & search
glossary term

"'Duplicate Without User-Selected Canonical' and Other Duplicate Statuses"

Updated

Search Console's three duplicate-page statuses, which of them are fine, and the one that sometimes needs a fix.

What it means

"Duplicate without user-selected canonical" means Google found two or more addresses showing the same or nearly the same page, you didn't say which one is the main version, so Google picked one itself and left this one out of search. Google calls this "working as intended": it doesn't show duplicate copies in results.

A canonical is the version of a page you want search engines to treat as the real one. You declare it with a canonical tag in the page's code, with a redirect, or (more weakly) by listing only that version in your sitemap. Search Console has three statuses about duplicates, and they mean quite different things:

Status What happened Do you need to act?
Duplicate without user-selected canonical The page is a duplicate, it doesn't name a main version, and Google chose another page as the main one Usually no. Only if Google picked the wrong page, or the page isn't really a duplicate
Alternate page with proper canonical tag The page correctly points to its main version, which is indexed No. Google says there is nothing you need to do
Duplicate, Google chose different canonical than user You named a main version, but Google thinks a different address is the better one and indexed that instead Check it. This is the one most worth a look

Why it matters

Seeing hundreds of pages under these statuses looks alarming, but Google is explicit that duplicate and alternate pages shouldn't be indexed, and that having pages marked duplicate or alternate "is usually a good thing" because it means Google found and indexed the main version. What matters is that the right version is the one in search.

Duplicates usually come from ordinary site mechanics, not copied content:

  • www and non-www: example.com/menu and www.example.com/menu
  • http and https versions of the same page
  • Tracking or filter parameters: ?gclid=… from an ad click, ?sort=price, ?color=green
  • Separate mobile pages, such as m.example.com
  • The same product or post reachable through two category paths

When Google picks the wrong main version, the address that shows in search may be an ugly parameter version, or a page you meant to retire.

How to fix it

For Alternate page with proper canonical tag, do nothing. It's a confirmation, not a problem.

For Duplicate without user-selected canonical:

  1. See which page Google chose. In Search Console, open Indexing → Pages, click the status, then click the inspect icon next to an example address. Under Page indexing, look at Google-selected canonical.
  2. If Google's choice is the page you want in search, stop. It's working as intended. Adding a canonical tag is still good practice, but not urgent.
  3. If Google chose the wrong page, add a canonical tag on each duplicate pointing to the version you want, and make sure your own menus and sitemap link only to that version.
  4. If the page isn't really a duplicate, make its content clearly different: Google decides what counts as a duplicate by how similar the content is. Two near-identical service pages for neighboring towns are a classic example.

For Duplicate, Google chose different canonical than user:

  1. Compare the two choices. Inspect the page and read both User-declared canonical and Google-selected canonical under Page indexing.
  2. Open all three pages in your browser: the inspected page, the one you declared, and the one Google chose.
  3. Check that your declared page is genuinely similar. If the page you pointed to doesn't closely match the content, Google won't accept it. Fix the canonical tag so it points to a true copy.
  4. Remove mixed signals. Google treats a redirect and a canonical tag as strong signals and a sitemap entry as a weak one. If your sitemap lists one version, your links point to another and your canonical tag names a third, Google will make its own call. Make them all agree.
  5. For a page that should no longer exist at all, a permanent redirect to the main version is stronger than a canonical tag. See 301 vs. 302 redirects.

Note that Search Console's live test doesn't check duplicate or canonical conditions, so after a fix the report updates only as Google recrawls the pages. Google's guide to consolidating duplicate URLs covers each method in more detail.

ask datanephew

Did Google pick the right version of my page?

Ask datanephew to inspect the page. It reads the URL inspection result from Search Console for free, including the canonical you declared and the one Google chose, and tells you whether they match and which address is actually showing in search.

Which of my duplicate pages actually need fixing?

Ask datanephew to list the pages under each duplicate status and flag the ones where Google overrode your choice. Those are the ones worth your time; alternate pages with a proper canonical tag can be left alone.

Can datanephew fix the canonical tags for me?

Not directly. datanephew can't edit canonical tags, redirects or your site's code. It can tell you exactly which pages need a tag and where it should point, so you or your web developer can make the change.