SEO Research

Duplicate Without User-Selected Canonical: When to Fix It

Google chose another URL for a page you expected to index. Check which version it picked, why the signals may disagree, and whether the page needs a fix.

Written bySavageAudit TeamProduct & Research
XinShare on LinkedIn
Three overlapping paper browser windows with an orange tab marking the front page
Short answer

Google grouped the inspected URL with another page and chose the other URL as canonical. Open URL Inspection to see which URL Google chose. If it is the page you want people to find, the exclusion may be expected. Investigate when Google chose the wrong duplicate or grouped two pages that should stand on their own.

You find your new service page under Duplicate without user-selected canonical in Search Console. Before touching the tag, check which URL Google picked. If it picked the clean copy of the same page, inspect that destination and confirm it’s indexed. If it picked an older page for a different service, open both and see what a visitor would actually get.

What the Search Console status means

Google found duplicate content at another address, recorded no preferred version for this URL, and chose the other address to represent the group. Search Console calls that address the Google-selected canonical. In Google’s Page indexing documentation, the duplicate’s exclusion is expected when the selected page represents the content you want people to find.

What to record before changing a tag

Take one example from Indexing → Pages, ideally an address you recognize. For a large report, pick a few from different groups. Twenty addresses with the same tracking parameter are less useful than a tracking URL, a product variant, and a page you expected to rank for a different service.

  1. Inspect the exact reported URL. Include the hostname, path and query string. Under Page indexing, record the last crawl date, User-declared canonical, and Google-selected canonical, where available.
  2. Open both addresses. Note whether either redirects. Check the final response, the main content and any canonical in the HTML or HTTP headers. A tracking URL and a clean URL may display the same article. Two category pages might look similar until you compare the product lists.
  3. Inspect the preferred destination on its own. If you control it, confirm what Google reports about that exact URL. Then check its current response, indexing directives, sitemap membership and links from the site. For a page you want in Search, a redirect to another address or an unintended noindex needs its own investigation.

Write down the crawl date. If you changed the tag this morning and Google last crawled the page on Tuesday, the inspection result may still describe the old page. The live test checks what Google can fetch now. To find the canonical Google selected, use the indexed result, as Google explains in its URL Inspection help.

If the field is unavailable or points outside a property you can inspect, record exactly what you could see. You can still check public responses and compare content. Record Google's choice only from the indexed inspection result.

What a clean duplicate setup looks like on SavageAudit

On November 17, 2026, we requested our AI website builders guide with and without a tracking parameter. Both addresses returned HTTP 200 at the requested URL. We checked the canonical tag in the HTML and the entries in the public sitemap.

URL we requestedResponseCanonical declared in HTMLIn the sitemap
`/blog/best-ai-website-builders`200Clean article URLYes
`/blog/best-ai-website-builders?utm_source=example`200Clean article URLNo

A visitor can follow the tracking link and stay on that address. The canonical tag and sitemap both point to the clean version. This example shows the preference in the live HTML and sitemap. Use the indexed URL Inspection result on your site to verify Google’s choice. Open the clean article · Open the parameterized address · Open the sitemap

To check your own page, use your browser's View Page Source and find rel="canonical". If you want to see the unredirected status and whether the server sets a canonical HTTP header, use the headers from a GET request. This command repeats the request for our tracking example and keeps the raw response for inspection.

bash
curl --silent --show-error --user-agent 'Mozilla/5.0' \
  --dump-header canonical-headers.txt --output canonical-page.html \
  'https://savageaudit.com/blog/best-ai-website-builders?utm_source=example'

Check canonical-headers.txt for the status line, Location and any Link header. Check canonical-page.html for the canonical element. If the source and rendered page show different canonical values, look for a script or routing template that changes the head after load. JavaScript SEO audit checklist

Google chose the right page

Suppose the reported URL adds a newsletter parameter to an article, and URL Inspection shows Google selected the clean article. Inspect the clean page. If it is the version you want in Search and Google indexed it, the duplicate's exclusion serves that purpose. Check a few more URLs with the same pattern before spending time on the rest of the report.

Where you control the links, use the clean URL in navigation, editorial links and the sitemap. A campaign link can still use tracking parameters. You can make the canonical preference explicit on copies that remain accessible, especially if the site generates many variants, but keep the clean page as the search destination.

Google chose the wrong copy

Say both /resources/launch-checklist and /blog/launch-checklist show the same checklist. The blog URL is the one you want to keep. If people still need the resources URL to load directly, both pages can declare the blog URL in their canonical tags. If the older address has been retired, send it to the equivalent article with a permanent server-side redirect, such as a 301 or 308.

Then check the menu links and the sitemap. If navigation still leads to the old route or the sitemap lists both versions, update them to use the address you want Google to pick. Check that the destination responds successfully, can be crawled, and declares itself when you use canonical tags. Google's canonical URL guidance describes redirects and canonical annotations as strong signals and sitemap inclusion as a weaker one. Align them around the same address.

Both pages deserve a result

Imagine a bookkeeping firm has one page for monthly bookkeeping and another for catch-up bookkeeping. The two pages reuse the same service description, process and pricing paragraph, with little beyond the title to distinguish them. If Google groups them, open both. Ask whether a customer can see which service applies to them from the main content.

For monthly work, explain the recurring scope, what the firm reconciles each month and what clients receive. For catch-up work, explain the records needed, how the backlog is assessed and what happens when the accounts are current. Check the rendered pages too. If a routing error sends both URLs the same default content, fix that before editing copy.

Once the pages serve separate needs, check that each delivers its own content at its intended URL and declares its own canonical. Link to each from the page where it makes sense for the reader. A self-referencing tag is a preference. The content and the rest of the site's signals still have to support it. Google's canonical troubleshooting guide recommends checking for technical conflicts and making independently useful pages substantially different.

Check the signals that often disagree

Check where each signal comes from before changing a shared template.

What you seeFirst place to check
The page points at a different host or an old slugCompare the HTML canonical and the HTTP `Link` header. Find the template or CMS field that sets them.
The preferred address redirectsFollow the redirect to its final destination. Check whether the canonical tag, internal links and sitemap use that destination.
The preferred address is missing from the sitemapCheck if the sitemap's URL generator applies the same host and path rules as the page.
The canonical changed after Google last crawled the pageVerify the live output. Record the crawl date and compare it after Google revisits the URL.
Two distinct URLs show the same placeholder or fallbackCheck the response status and the main content Google can render. Fix the routing or data issue.

Apply the same checks to one working URL that uses the template. A problem on one article might be a bad CMS entry. A problem across several article URLs with the same pattern might be in the template. Treat those as different fixes, even when the Search Console report groups them together. How to check an XML sitemap

Avoid using robots.txt or noindex to pick a preferred duplicate. Google needs crawl access to read the page's canonical tag. Use noindex when you want a page excluded from Search, and use canonical signals when your goal is to indicate which equivalent address should represent the group.

Verify the change using the same URLs

After you ship a fix, request the old URL and the intended destination again. Record the status, final URL and current canonical tag. Check the links or sitemap entries you changed. For a permanent move, keep the path direct and confirm the new destination serves the content you meant to preserve.

Run URL Inspection's live test if you need to check the current fetch and rendering. Later, when the crawl date advances, open the indexed inspection result and check Google's selected canonical again. The aim is to see the intended page representing the group, or to see both genuinely distinct pages assessed on their own. Count the affected URLs if it helps track the repair, but prioritize the pages customers need to find.

If the inspection result says Crawled, currently not indexed, follow the checks for that status.

FAQ

Common questions

Is Duplicate without user-selected canonical an error?

It describes Google's handling of a duplicate URL. Check the Google-selected canonical and inspect that address. If it is the page you intend people to find, the excluded copy may need no change. Investigate when the selected URL is the wrong copy or the pages should serve different searches.

How do I find the canonical URL Google selected?

Enter the affected address in Search Console's URL Inspection tool and open Page indexing → Google-selected canonical in the indexed result, when available. The current HTML shows what the site declares. The live test can check the current response and rendering. Google reports its canonical selection in the indexed data.

Should I use a canonical tag or a 301 redirect?

Use a canonical tag when duplicate or very similar pages should stay accessible and you want to declare a preferred URL. Use a permanent redirect such as a 301 or 308 when an old address has moved and visitors should go straight to the replacement. Point both methods to the intended destination if both are in use across the site.

Why does Search Console still show the status after I added a canonical?

Compare the report's last crawl date with the change date and check the live HTML. If Google crawled the page after the change and still prefers a different URL, check the rendered content, redirects, internal links and sitemap. Canonical tags express a preference and Google can choose another URL.

SavageAudit

Run your own public presence audit

See how your website, search footprint, AI visibility, social proof, and conversion trust look from the outside.

Roast My SiteView pricingCompare sites