Skip to content
SearchSee plans and prices

"Duplicate without user-selected canonical" on WordPress

Google calls this page a duplicate and says you did not name a preferred address. It chose another URL and will not show this one. The help page says that is not an error. On WordPress, archives and filtered addresses are the usual rows, because canonical links are printed on posts and pages only.

By
WP Ministry
Published

In short

  • Google says the page is a duplicate, names no preferred canonical, and will not be shown. It calls this working as intended, not an error.
  • Inspect the URL to see which address Google selected. The live test does not check duplicate or canonical conditions.
  • WordPress prints a canonical link on posts and pages. Archives, the blog home and search results do not get one.
  • Name a canonical when Google chose the wrong address. Make the content differ when the page is not a duplicate.
  • Do not use robots.txt to pick a canonical. Google says it may still index a blocked URL without reading it.
  • Which URL Google keeps is Google's decision. A sandbox cannot open the report.

"Duplicate without user-selected canonical" means Google has decided this address repeats another page, and that your page did not say which address it prefers. Google chose the other one. It will not show this address in Search. The help page's own words: "This is not an error, but is working as intended, because Google does not serve duplicate pages."

"Alternate page with proper canonical tag" is the neighbor. There your page did name a canonical, Google agrees, and the help says there is nothing to do. Here your page named nothing.

What the report is telling you

Open one example in the URL Inspection tool. The help says to inspect the URL to see which address Google considers canonical. Two lines matter: the user-declared canonical, which will be empty or absent for this status, and the Google-selected canonical, which is the address Google will show instead.

The same help page says the live test does not check duplicate or canonical conditions. A live test that looks fine does not clear this status. The indexed information is the crawl Google already did.

Google's canonical documentation adds the frame. If you name no canonical, "Google will identify which version of the URL is objectively the best version to show." The signals it documents, from stronger to weaker, are a redirect, a rel="canonical" link, and being listed in a sitemap. It says none of them is required. It also says not to use robots.txt to choose a canonical, because Google may still index a disallowed URL without its content, and not to use noindex to keep a duplicate out of the running, because that blocks the page from Search entirely.

Where WordPress leaves the choice to Google

A test recorded on what WordPress does with no SEO plugin found a canonical link on posts, pages and a static home page, and none on a home page that lists posts, on category, tag, author and date archives, or on search results. A post with a tracking parameter still named the clean address. An archive with a parameter names nothing, so it can land here. Search results also carry noindex, which is a different reason in the report.

Filtered and sorted store addresses are the other common pile. WooCommerce filter URLs is that case. Attachment pages, when they are still on, are covered in attachment pages in Google.

A WordPress SEO audit is the job when many of the pages you want found have a Google-selected canonical you disagree with.

What causes it

  • The address is a duplicate and names no preferred URL

    Common

    Google's help says the page is a duplicate of another and does not indicate a preferred canonical. Google chose the other page and will not serve this one. WordPress prints rel=canonical for singular queries, so many of its list and archive addresses name nothing.

    Fix: Leave addresses that should not be the one in Search

  • Google chose an address you do not want shown

    Sometimes

    The help says that if you think Google chose the wrong URL, you can mark the canonical yourself. A redirect, a rel=canonical link and a sitemap entry are the signals it documents, and it ranks a redirect and a canonical link above a sitemap.

    Fix: Name the address you want, when Google chose another

  • The page is not the same as the one Google grouped it with

    Sometimes

    The help says that if the page is not a duplicate of the Google-chosen canonical, the content of the two pages should differ substantially. A canonical link does not make two different pages into one.

    Fix: Make the two pages different, if they are not duplicates

How to fix it

Leave addresses that should not be the one in Search

  • Easy
  • No risk
  • About 15 minutes
  1. Step 1: Inspect one example of each kind

    For an archive, a filter address and a parameterized copy, read the Google-selected canonical. If it is the post, the plain category or the unfiltered collection, Google has already chosen the address a visitor should see.

  2. Step 2: Stop there

    The help page says this is working as intended. Do not add noindex only to move the row to another reason, and do not disallow the address in robots.txt. Google's canonical guide says both of those are the wrong tool.

The count can stay large. The help's note on sites with more non-indexed than indexed pages treats a mass of sorted and filtered duplicates as something that probably should not be indexed.

Name the address you want, when Google chose another

  • Takes care
  • Low risk
  • About 30 minutes

Do this when Inspection shows a Google-selected canonical you do not want, such as a filtered URL in place of the plain one.

  1. Step 1: Pick one address

    Choose the URL that should appear in results. Google's guide says to use an absolute URL, and to put the same rel="canonical" link on the canonical page itself.

  2. Step 2: Say it in the HTML

    On the duplicate, and on the page you chose, the link belongs in the document head. Google's example is a link element with rel="canonical" and an absolute href. WordPress already prints that element on posts and pages. An archive or a filter that does not is where a theme or a plugin has to add it. Link to the canonical URL from the rest of the site as well. Google's guide calls consistent internal links another signal.

  3. Step 3: Do not contradict it

    The same guide says not to name one URL in a sitemap and a different one in rel="canonical". WordPress's sitemap lists the current addresses of posts and pages. A hand-written sitemap that still lists the duplicate fights the link.

  4. Step 4: Wait for another crawl

    The live test will not confirm this status. Inspect the URL again after Google has fetched it, and read the Google-selected canonical.

A redirect is the stronger signal, and the right one when the duplicate address should not load at all. Page with redirect is that status, and how to set up redirects is the WordPress side. Use a redirect only when you are retiring the extra address, which is what Google's guide says the method is for.

Make the two pages different, if they are not duplicates

  • Takes care
  • No risk
  • About 30 minutes

The help page says that if you believe the page is not a duplicate of the one Google chose, the content of the two should differ substantially. A canonical link pointed at a page that is not the same work will not make Google treat them as one. Its note under a different status says a duplicate has to be similar to its canonical, because that is what duplicate means.

Rewriting a thin archive into a page of its own is a content change, not a tag. After it is published, the same wait applies: the status moves when Google crawls again, or it does not.

When to get help

When the Google-selected canonical for pages you want found is a filtered address, a parameter URL or another post, and adding the link is more than a few templates. Reading Inspection beside the templates is the work.

Common questions

Do I have to fix every row?

No. Google's help says the status is not an error. Fix a row when the address Google chose is not the one you want visitors to land on. Leave feeds, filters and archives whose selected canonical is the real page.

Why does my post not have this status, while its category does?

WordPress prints a canonical link on the post and not on the category. The post can still be filed under Alternate page with proper canonical tag when a parameter URL points at it. The category, naming nothing, can be filed here.

Will a sitemap entry fix it?

It is a weak signal. Google's guide says a sitemap suggests canonicals and that Google still decides which URLs are duplicates. A rel="canonical" link is the stronger of the two. Listing both the duplicate and the original as if both were canonical fights the link.

The live test says the page is fine. Why is it still listed?

The Page indexing report's help says the live test does not test duplicate or canonical conditions. The status comes from the last crawl, not from the live test.

More on this subject

Would you rather we fixed it?

SEO audit is $249. A written audit, each finding with its source, and up to 2 hours of fixes done and tested again.

More about this work: WordPress SEO audit

May we measure how this site is used?

A yes notes the pages of this visit and loads Google Analytics. A no keeps and loads nothing. See the cookies page.

If you say yes, we note the pages you look at during this visit and load Google Analytics. If you say no, nothing is kept and nothing is loaded. The site works the same either way. The cookies page has the details.