Page indexing report · Search Console
Duplicate without user-selected canonical
Google decided this page duplicates another one and indexed the other URL. You hadn’t said which you prefer, so Google chose. Google says it’s not an error.1 Here’s how to check whether Google picked the right page, and what to do when it didn’t.
Check the URL first
The checker shows whether the page has a canonical tag and where it points, plus the status code and whether the HTML has real content. It can’t show which URL Google chose. URL Inspection does that.
In 30 seconds
- Google grouped this page with a similar one and indexed the other. It won’t show this URL in Search.1
- If Google kept the URL you want, there’s nothing to fix.1
- If it kept the wrong one, a redirect or canonical tag tells Google your preference. Both are strong signals; neither is binding.3
- If the page isn’t really a duplicate, Google may be seeing an error page or an empty shell.9
What the status means
When Google indexes a page, it works out the main content. If several pages have the same or very similar main content, Google groups them and picks the one it considers most complete and useful as the canonical.2 The others aren’t shown in Search and are crawled less often.2
“Without user-selected canonical” means the page gave no preference: no canonical tag, header or redirect. Google chose on its own.1 Gary Illyes has described how: Google strips boilerplate like menus and footers, reduces the main content to a checksum, groups similar ones and weighs over twenty signals to pick the canonical.6
The status is set at the indexing stage. Select a stage to see what happens there.
Discover
Google learns that a URL exists, mostly from links on pages it already knows and from XML sitemaps.
What goes wrong: Nothing links to the page and it isn’t in a sitemap, so Google never hears about it.
Report statuses at this stage
- URL is unknown to Google (shown in URL Inspection, not in the report)
Crawl
Googlebot checks robots.txt, then requests the URL. It spaces requests out so it doesn’t overload the server.
What goes wrong: The URL is blocked, returns an error, or the server is slow, so Google backs off and crawls less.
Report statuses at this stage
Render
Google runs the page’s JavaScript in a recent version of Chrome to see the finished page.
What goes wrong: Content only appears after a click or scroll, or the scripts fail, so the rendered page is nearly empty.
Report statuses at this stage
- No status of its own. Problems show up at the next stage as thin pages or soft 404s.
Index
Google decides which version of the page to keep and whether it is worth storing at all.
- Group duplicates. Pages with the same or very similar content go into one group.
- Pick a canonical. One URL represents each group. Canonical tags, redirects and sitemaps are hints, not commands.
- Select for the index. Google decides whether the canonical page is worth keeping. Google says this largely depends on quality.
What goes wrong: The page duplicates another, is marked noindex, or Google decides it adds too little to keep.
Report statuses at this stage
- Crawled – currently not indexed
- Duplicate without user-selected canonical (this page)
- Duplicate, Google chose different canonical than user
- Alternate page with proper canonical tag
- Page with redirect
- Soft 404
- Excluded by ‘noindex’ tag
Serve
Indexed pages can appear in search results. Being indexed is not the same as ranking; an indexed page can still get no clicks.
What goes wrong: The page is indexed but doesn’t match what people search for, or other pages answer it better.
Report statuses at this stage
Is it a problem?
Google’s wording is plain: “This is not an error, but is working as intended”.1 Some duplication is normal and isn’t against Google’s spam policies.2
Usually fine
- Filter, sort and tracking-parameter URLs
- http, www or trailing-slash variants of indexed pages
- Print versions and other copies of a page
- Any case where Google chose the URL you want
Worth fixing
- Google chose a URL you don’t want people to land on
- Google chose a page on another website
- Pages with different content marked as duplicates
- A sudden jump in this row after a site or hosting change
Find the cause
Start in URL Inspection: the “Google-selected canonical” field shows which URL Google kept. Only the indexed result shows it; the live test can’t predict canonical choice.5
URL variants of the same page
Google lists the usual sources of duplicates: http and https, mobile and desktop versions, regional versions in the same language, sorting and filtering, and demo sites left open to crawlers.2 These are expected. The only question is whether Google kept the right URL.
Pages with little unique content
John Mueller has listed pages whose unique content is small next to the menus and template among the reasons Google treats pages as duplicates.7 Google’s fix is to make sure clustered pages are sufficiently different.4
Google predicted duplicates from the URL
To save crawling, Google can learn that a part of a URL doesn’t change the content. Mueller gave the example of event sites with the same listings under many city names: Google may decide the city part is irrelevant and treat other city pages as duplicates too.8
Google saw an error page or empty shell
If a host or CDN shows Googlebot a bot check with a 200 status, Google may index that page instead, and pick another site with the same error page as the canonical.9 Mueller has also named pages that fail to render, leaving the same base HTML on every URL.7 Two servers returning identical soft 404 pages can cause the same.4
Pagination pointed at page 1
Google says not to use the first page of a paginated list as the canonical for the rest. Each page should have its own.10
Your content on another site
Rarely, Google picks a URL on a site hosting your content without permission. For syndication, Google recommends that partners block indexing of their copy rather than relying on canonical tags.4
Canonical signals by strength
Google lists the ways to state your preference in order of how strongly they influence its choice.3 Select one to see when to use it.
301 or 308 redirect
Google lists redirects first: a strong signal that the redirect target should be canonical.3 Use it when the duplicate URL has no reason to exist. Visitors and Google both land on one address.
HTTP/1.1 301 Moved Permanently
Location: https://example.com/shoes/rel="canonical" tag
A strong signal, placed in the <head>.3 Use an absolute URL and add a self-referencing tag on the canonical page itself.3 Keep just one per page.11
<!-- on https://example.com/shoes/?sort=price -->
<link rel="canonical" href="https://example.com/shoes/">It’s a hint, not an order. Google says indicating a canonical “is a hint, not a rule”.2
rel="canonical" HTTP header
The same signal as the tag, sent as a response header. It works for files without an HTML head, such as PDFs.3
Link: <https://example.com/guide.pdf>; rel="canonical"Sitemap listing
Listing a URL in your sitemap is a weak signal for it to become canonical.3 List only the preferred version. Google warns against naming one URL in the sitemap and another in the canonical tag.3
<url>
<loc>https://example.com/shoes/</loc>
</url>Internal links
Google asks you to link to the canonical URL rather than a duplicate, because consistent links help it understand your preference.3 Gary Illyes has said PageRank is still one of the canonical signals.6
<a href="https://example.com/shoes/">Shoes</a>
<!-- not /shoes/?ref=nav or /Shoes -->HTTPS
Google prefers HTTPS over HTTP as canonical. A bad certificate or a redirect from HTTPS to HTTP makes it strongly prefer HTTP instead.3 Illyes has said redirects carry much more weight than HTTPS alone.6
http://example.com/shoes/ -> 301 -> https://example.com/shoes/
Strict-Transport-Security: max-age=31536000Don’t use these
Google recommends against all of these for choosing a canonical:3
- robots.txt: Google may still index a blocked URL, without its content.
- noindex: it blocks the page from Search entirely.
- The URL removal tool: it hides every version of the URL.
- A URL fragment (
#section) as the canonical.
Use one or more, but make them agree. If JavaScript sets the canonical, it must match the one in the original HTML.11
How to fix it
- Inspect a few example URLs and note which URL Google chose for each.5
- Where Google chose the URL you want, stop. Optionally add a canonical tag to make it explicit.
- Where it chose the wrong one, redirect the duplicate if visitors don’t need it; otherwise add a canonical tag to it.3
- Make internal links, the sitemap and hreflang point at the preferred URL.3
- Where the page isn’t a duplicate, fix what Google receives (errors, bot checks, empty HTML) or make the content clearly different.4
- Request indexing for your most important URLs. It’s subject to a quota.4
What other guides get wrong
| Often said | What’s actually true |
|---|---|
| It’s an error you need to fix | Google says it’s not an error but working as intended.1 Fix it only when Google chose the wrong URL. |
| Add noindex to the duplicates | Google doesn’t recommend noindex for choosing a canonical within a site, because it blocks the page from Search entirely.3 |
| A canonical tag and a 301 are equally strong | Google lists redirects first and the canonical tag second, in order of strength.3 |
How long it takes
- Up to 2 weeksfor Google to release pages from a duplicate cluster after you change the content.4
- Days to weeksfor Google to recrawl a page after a request.12
- Up to about 2 weeksfor Search Console to validate a fix, sometimes much longer.1
Google adds that pages split out faster when the difference from the other pages is clear and significant.4
Compared with “Google chose different canonical than user”
| Duplicate without user-selected canonical | Duplicate, Google chose different canonical than user | |
|---|---|---|
| Did you declare a canonical? | No | Yes, and Google picked another URL |
| Is this URL indexed? | No | No |
| First fix | State a preference: redirect or canonical tag | Make all your signals agree, or accept Google’s choice |
Questions
Is “Duplicate without user-selected canonical” bad?
Usually not. Google says it isn’t an error: Google found duplicates and indexed one of them. It matters only when Google indexed the wrong one, or when the page isn’t really a duplicate.
Should I add noindex to the duplicate pages?
No. Google recommends a canonical tag or a redirect instead. A noindex removes the page from Search completely and doesn’t tell Google which URL you prefer.
Canonical tag or 301 redirect?
Use a 301 or 308 redirect when the duplicate URL has no purpose, such as http or www variants. Use a canonical tag when visitors still need the duplicate, such as a filtered or tracking URL. Google ranks redirects as the stronger signal.
Why is a unique page marked as a duplicate?
Google may be seeing something other than what you see: an error page, a bot check or an empty JavaScript shell. Pages that share a large template with little unique content can also be grouped. Check what Google receives with URL Inspection’s live test.
How do I fix this on Shopify?
Shopify products can load under collection paths as well as /products/. Check that those URLs carry a canonical tag pointing to the /products/ URL, and link to /products/ URLs where you can. If Google already picks the /products/ URL, there’s nothing to fix.
Should I click Validate fix?
Only if you fixed something, such as a rendering or server problem that made pages look identical. If Google simply chose the right duplicate, there’s nothing to validate.
Sources
- Google, “Page indexing report”, Search Console Help
- Google, “What is URL canonicalization”, Search Central, updated August 2026
- Google, “How to specify a canonical URL with rel=“canonical” and other methods”, Search Central, updated July 2026
- Google, “Fix canonicalization issues”, Search Central, updated August 2026
- Google, “URL Inspection tool”, Search Console Help
- Gary Illyes (Google), Search Off the Record, 2020, reported by Search Engine Journal, November 2020
- John Mueller (Google), Reddit r/bigseo, reported by Search Engine Journal, April 2026
- John Mueller (Google), Search Central SEO hangout, March 2021, reported by Search Engine Journal
- John Mueller and Martin Splitt (Google), Search Off the Record episode 112, “How to read the Indexing Report”, July 2026 (transcript)
- Google, “Pagination, incremental page loading, and their impact on Google Search”, Search Central, updated December 2025
- Google, “Understand the JavaScript SEO basics”, Search Central, updated March 2026
- Google, “Ask Google to recrawl your URLs”, Search Central, updated December 2025