Skip to content
Application notes · 7 min read

Part of Page Indexing Report in Google Search Console: Every Status Explained

Duplicate Without User-Selected Canonical: Meaning and Fix

Duplicate without user-selected canonical means Google sees the page as a copy and chose the canonical itself. How to check its choice and declare yours.

Duplicate without user-selected canonical means Google treats the page as a duplicate of another URL, the page doesn't say which version it prefers, and Google picked the canonical on its own. The URL Google picked is the one it can show in Search; this one stays out. Google's Page indexing report help says this isn't an error: Google doesn't serve duplicate pages, by design. It needs a fix in two cases: Google kept the wrong URL, or the page isn't really a copy.

It's one of three canonical reasons in the page indexing report. Alternate page with proper canonical tag means the page declared a canonical and Google agreed. Duplicate, Google chose different canonical than user means the page is marked as canonical and Google prefers another URL. Here, nothing was declared, so Google went by its own signals.

What Duplicate without user-selected canonical means

Google groups pages with the same or very similar content and picks the most complete and useful one in each group. Its canonicalization guide names signals such as HTTP or HTTPS, redirects, sitemap inclusion and rel="canonical" annotations. The “user-selected” canonical is the one your page declares, in a <link rel="canonical"> element or a Link HTTP header. Google treats it as a hint, not a rule. With no hint, Google decides from the other signals, and this status says it did.

It isn't a penalty: the same guide says some duplicate content on a site is normal and doesn't violate Google's spam policies (more in duplicate content SEO). What you lose is control over which URL appears and collects the links.

Where these duplicates come from

Usually one page answers at several URLs. Google treats each URL separately, so /shoes and /shoes/ are two URLs (To slash or not to slash, 2010). The bare root is the exception: https://example.com and https://example.com/ are the same. Paths are case sensitive, and Google's URL structure guidelines name referral, sort and session ID parameters as sources of extra URLs. The canonicalization guide adds same-language region variants and demo sites left open to crawlers.

SourceSame page atUsual fix
Trailing slash/shoes, /shoes/Redirect one form to the other, site-wide.
Index file/, /index.htmlRedirect /index.html to / and link to /.
Protocol and hosthttp://example.com/, https://www.example.com/Redirect every variant to the one HTTPS host you use.
Letter case/Shoes, /shoesPick one case and redirect the other.
Tracking and session parameters/shoes?utm_source=newsletter, /shoes?sessionid=8f2aCanonical to the clean URL; never use them in internal links.
Sort and filter parameters/shoes?sort=price, /shoes?color=redCanonical to the unfiltered list, or keep filters out of the crawl.
Same file, two formats/white-paper.docx, /white-paper.pdfA canonical HTTP header on the copy.
Same-language regions/en-us/pricing, /en-gb/pricinghreflang annotations between the versions.
Demo or staging copystaging.example.comPut it behind a login.

These variants usually reach Google through links, not your sitemap: a newsletter link with utm_ tags, a sort menu built from plain links, a template that links to /index.html. Choosing one form for slashes, www and HTTPS is covered in trailing slash SEO.

Read Google's selected canonical in URL Inspection

  1. Filter the report. Open the reason in the Page indexing report and switch the filter from All known pages to All submitted pages. A sitemap URL in this list means your sitemap and Google disagree about which version is the page: fix those first.
  2. Inspect an example. In the URL Inspection tool, the Page indexing section reads Page is not indexed: Duplicate without user-selected canonical. Further down that section, User-declared canonical shows None and Google-selected canonical shows the URL Google kept, a value Google says can be a few hours out of date (URL Inspection tool help).
  3. Find the source. Referring page is a page Google possibly used to discover the URL, often the link or template that produces the variant.
  4. Inspect the URL Google kept. If it's on Google and it's the version you want, nothing is broken. If Google kept the http://, parameter or wrong-slash version, fix the signals below.
  5. Don't rely on the live test. The Page indexing report help says duplicate and canonical conditions aren't tested there. Use its View tested page only to confirm the canonical tag is in the HTML Google renders.

In bulk, the URL Inspection API returns the same data, within 2,000 calls a day per property (usage limits). Its reference says userCanonical is absent when you declared none and googleCanonical is absent when the page isn't indexed, so handle missing fields and fall back to Search Console for Google's pick:

curl -s -X POST "https://searchconsole.googleapis.com/v1/urlInspection/index:inspect" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"inspectionUrl": "https://example.com/shoes?sort=price", "siteUrl": "sc-domain:example.com"}' \
  | jq '.inspectionResult.indexStatusResult | {coverageState, userCanonical, googleCanonical, lastCrawlTime}'

How to fix Duplicate without user-selected canonical

If Google kept the URL you want, you can leave it. Declaring the canonical anyway makes the choice explicit, and Google recommends a self-referencing canonical on the canonical page (How to specify a canonical URL). If Google kept the wrong one, work through these steps in order.

1. Pick one URL per page

HTTPS (Google favors it over HTTP when picking a canonical), one host, one trailing-slash rule, one letter case, no parameters that don't change the content. Templates, redirects, internal links and the sitemap should all produce exactly this URL.

2. Redirect the variants nobody needs

Slash, case, index.html, http:// and www variants have no reason to resolve. Redirect them permanently: Google counts redirects as a strong canonical signal and suggests them for retiring a duplicate. Next.js redirects /about/ to /about by default, and one setting flips it:

// next.config.js
module.exports = {
  trailingSlash: true, // now /about redirects to /about/
};

3. Declare the canonical on variants that stay live

Parameter URLs, print views and file copies must keep working for visitors, so tag them instead. Put a rel="canonical" link with an absolute URL in the <head>, the only place Google accepts it, on each duplicate and on the canonical page itself:

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

For a non-HTML file, Google's example sends it as an HTTP header on the copy:

Link: <https://example.com/downloads/white-paper.pdf>; rel="canonical"

Build the canonical from the route, never from the request URL, so parameters can't leak into it. In the Next.js App Router, with metadataBase set in the root layout (generateMetadata):

// app/shoes/[slug]/page.tsx
import type { Metadata } from "next";

type Props = { params: Promise<{ slug: string }> };

export async function generateMetadata({ params }: Props): Promise<Metadata> {
  const { slug } = await params;
  // From the route only: ?sort= and ?utm_source= never reach the canonical.
  return { alternates: { canonical: `/shoes/${slug}` } };
}

Set it per page. Next.js merges metadata shallowly and pages inherit fields they don't set, so a canonical: "/" in the root layout lands on every page without its own alternates, declaring each a copy of the homepage. More on how Google weighs the tag in the canonical tag.

4. Make the other signals agree

  • Internal links. Google asks you to link to the canonical URL, not a duplicate. Fix the menu or template Referring page led you to.
  • Sitemap. List canonical URLs only. Inclusion is a weak signal, and Google tells you not to name one URL in the sitemap and another in rel="canonical".
  • hreflang. Use canonical URLs in the annotations. Google prefers URLs that are part of hreflang clusters, and its canonicalization troubleshooting guide recommends hreflang for regional versions in one language.

5. If the page isn't a copy, make it different

Sometimes Google is right that two pages are too alike: product variants that differ by one word, location pages with a swapped city name. Google's help says a page that isn't a duplicate should be substantially different from the Google-selected canonical. The troubleshooting guide adds that Google might hold pages in a duplicate cluster for up to two weeks after a content fix, and that a clear, significant difference separates them sooner. If two pages can't be made distinct, merge them and redirect one.

What not to use

  • noindex. Some guides suggest it for duplicates that must stay live. Google advises against it for choosing a canonical within a site: it keeps the page out of Search instead of consolidating it.
  • robots.txt. Google says not to use it for canonicalization. Google can't read the canonical on a URL it may not crawl, and a disallowed URL can still be indexed without its content. Blocking filter URLs to save crawling is a separate decision (faceted navigation SEO).
  • The removal tool. It hides every version of a URL from Search.
  • The URL Parameters tool. Google deprecated it in 2022, saying only about 1% of the configurations in it were useful for crawling.

What the report shows after the fix

Nothing changes until Google recrawls the variants. Going by Google's definitions, a duplicate that now points to a canonical Google accepts should move to Alternate page with proper canonical tag, and a redirected variant to Page with redirect. Both are the end states you want. Duplicate, Google chose different canonical than user means your signals still disagree.

Google says crawling can take a few days to a few weeks and that asking again for the same URL won't speed it up. Its troubleshooting guide suggests requesting indexing after a fix, kept for your most important URLs because requests are limited.

How IndexCyborg tracks duplicate pages

Once you connect Search Console, IndexCyborg inspects the URLs in your sitemaps with the URL Inspection API, within Google's daily quota, and stores Google's coverageState word for word, with the user-declared and Google-selected canonicals when Google returns them. This status lands in the Duplicate / canonical exclusion bucket together with the other two canonical reasons: GET /v1/sites/{id}/urls?status=excluded_duplicate lists them, and the MCP tool get_indexing_status returns Google's verbatim result for one page, which tells them apart. Since the inventory comes mainly from your sitemaps, a page there is usually a URL you submitted that Google treats as a copy. Each is re-checked after 7 days, so you see when it moves.

Technical checks record the canonical each page's HTML declares and raise an issue with the evidence when it points to another page. Once a page declares one, a Google-selected canonical that differs raises Google selected a different canonical. Automatic indexing requests through the Chrome extension skip duplicates, since a request can't change which URL Google keeps; once you've fixed a page, you can queue it by name with request_google_indexing. More on the features page.

Frequently asked questions

Is Duplicate without user-selected canonical bad for SEO?

Not on its own. Google says it isn't an error: Google doesn't serve duplicate pages, so it shows the URL it selected as canonical instead. It only needs work when Google kept a URL you don't want in search, or when the page isn't really a copy.

What does User-declared canonical: None mean in URL Inspection?

The page doesn't declare a canonical URL, either with a rel=canonical link element or a Link HTTP header. Google says None is fine for a page that isn't an alternate; on a duplicate, it means Google chose the canonical from its other signals.

Should I noindex duplicate pages?

Not to pick a canonical within your own site. Google advises against noindex for that because it keeps the page out of Search instead of consolidating it with the main version. Use a redirect, or rel=canonical when the duplicate has to stay live.

How long does it take for a duplicate to drop out of this status?

It changes only after Google recrawls the URL and sees your redirect or canonical. Google says crawling can take a few days to a few weeks, and that it may keep pages in a duplicate cluster for up to two weeks even after you fix their content.

Do I need a canonical tag on every page?

It isn't required, but Google recommends a self-referencing rel=canonical on canonical pages and a canonical on each duplicate pointing to the main URL. Google treats it as a strong signal, not a rule, so redirects, internal links and the sitemap should agree with it.