Duplicate, Submitted URL Not Selected as Canonical

What 'submitted URL not selected as canonical' means

In the Page indexing report in Google Search Console, this label appears next to a URL that you actively submitted for indexing, most often by listing it in an XML sitemap. Google evaluated that URL alongside a cluster of duplicate or near-duplicate pages and chose a different URL as the canonical, or representative, version. The submitted URL still exists and Google can still crawl it, but Google indexes the other URL and folds this one's ranking signals into that other page instead.

This is best understood as the sitemap-submitted counterpart of a more general phenomenon: Google overriding a signal you provided about which URL should be canonical. Google's current help documentation for the Page indexing report foregrounds the wording for the case where you set an explicit rel=canonical tag and Google overrides it. The sitemap-submitted variant covered here is real, is still seen in Search Console accounts, and is documented by reputable SEO guides, but it should not be treated as a separately, permanently documented status with its own fixed definition. Functionally, it is the same override behavior, triggered through a different signal.

How this differs from the other duplicate canonical statuses

Google Search Console has more than one status for pages Google declined to treat as canonical, and the distinguishing feature here is simple: you submitted this specific URL, typically through a sitemap, and Google still rejected it in favor of another version.

Compare the three related cases. When a page shows as duplicate without a user-selected canonical, no canonical signal exists at all — no rel=canonical tag, no redirect, nothing. When a page shows as having a different canonical chosen than the user declared, you set an explicit rel=canonical tag on the page itself and Google overrode it. In the submitted-URL case, the signal in question is sitemap inclusion rather than an on-page tag. You are telling Google, through the sitemap, that this URL is worth indexing, and Google is telling you, through the report, that it disagrees.

Why does sitemap inclusion carry less weight than a canonical tag? Because Google explicitly ranks sitemap inclusion as a weak signal in its own guidance on consolidating duplicate URLs, while it calls rel=canonical and 301 redirects strong signals. A URL's mere presence in a sitemap is easy for Google to overrule when stronger signals, such as a canonical tag elsewhere, internal linking patterns, or HTTPS status, point somewhere else.

Why a submitted URL gets rejected as canonical

Three patterns account for most cases of this status.

• The URL is a genuine duplicate or near-duplicate. Google's algorithms found the submitted URL substantially similar to another URL on the site and consolidated the two into one cluster, then picked what it judged the better version to index.
• Non-canonical URLs were included in the sitemap in the first place. This is the most frequent trigger. Faceted navigation URLs, parameterized URLs (sort, filter, session identifiers), paginated duplicates, or tag and category archive pages that overlap with other archives sometimes end up in an auto-generated sitemap even though they were never meant to be the canonical version of anything.
• Signals are mismatched across the site. The sitemap lists one URL as worth indexing, but the rel=canonical tag on that page, or on a competing page, points elsewhere; internal links favor a different URL; or a redirect somewhere in the chain targets a different destination. Google weighs all of these signals together, and when they disagree, the sitemap entry — being a weak signal — tends to lose.

How to diagnose it

Two checks resolve most cases.

First, run the flagged URL through the URL Inspection tool in Search Console. The report shows both the user-declared canonical (what your page, or lack of a page-level declaration, indicates) and the Google-selected canonical (the URL Google actually chose to index). Comparing the two tells you whether Google's choice looks correct, and which URL is now receiving the consolidated signals.

Second, audit the sitemap itself. Export or open the sitemap file and check whether the URLs it lists are actually the canonical, indexable versions of their respective pages. Look specifically for parameterized URLs, session-specific URLs, paginated or faceted variants, and any URL that carries a rel=canonical tag pointing to something other than itself. If a listed URL's own canonical tag names a different page, that mismatch is very likely the cause.

How to fix it

The fix depends on which URL should actually win.

• List only canonical, indexable URLs in sitemaps. Remove parameterized, faceted, paginated, or otherwise non-canonical URLs from the sitemap entirely. A sitemap should be a clean list of the URLs you want indexed, not a full crawl of every URL variant on the site.
• If Google's chosen canonical is correct, align the submitted URL's signals with it. Add or correct a rel=canonical tag on the submitted URL so it points to the URL Google selected, then drop the submitted URL from the sitemap so you stop asking Google to index a page you have effectively deferred to another.
• If the submitted URL should be the canonical, strengthen it. Add a self-referencing canonical tag on the URL, make sure its content is sufficiently unique rather than a near-duplicate, and point internal links at it rather than at the competing version. Then confirm that no other page's canonical tag, redirect, or sitemap entry contradicts that choice.

In both cases, the underlying goal is the same: make every signal — the sitemap, the rel=canonical tags, the internal links, and any redirects — agree about which URL is canonical, since Google consolidates all of them when deciding.

Sitemap hygiene that prevents it

Because sitemap inclusion is a weak signal that is easily contradicted, most instances of this status trace back to a sitemap that was generated without enough care about which URLs it contains. A few habits prevent recurrence.

• Generate sitemaps from canonical, indexable URLs only, excluding parameters, session identifiers, and pagination artifacts by default rather than filtering them out after the fact.
• Regenerate the sitemap whenever URL structure or canonicalization rules change, so it does not drift out of sync with the site's actual rel=canonical tags.
• Periodically cross-check a sample of sitemap URLs against their own canonical tags to confirm the sitemap is not listing pages that defer to a different canonical.
• Keep the sitemap aligned with redirects: a URL that 301-redirects elsewhere should not also appear in the sitemap as if it were still live and canonical.

Treated this way, the sitemap becomes a consistent, corroborating signal alongside rel=canonical rather than a source of conflicting information that Google has to resolve on your behalf.

Frequently Asked Questions