stillindexedStart monitoringOpen the app

Search Console Page indexing: Why pages aren't indexed

Duplicate, Google chose different canonical than user

You declared a canonical and Google indexed a different URL. Why Google overrides it, how to compare the two in URL Inspection, and how to align signals.

You declared a canonical for this page, but Google thinks a different URL is the better canonical and indexed that one. Either your declared canonical is not a true duplicate of this page, or other signals point elsewhere. Make redirects, canonical tags, sitemaps and internal links agree, or make the pages distinct.

What "Duplicate, Google chose different canonical than user" means

Google: "This page is marked as canonical for a set of pages, but Google thinks another URL makes a better canonical. Google has indexed the page that we consider canonical rather than this one." A declared canonical has to resemble the page: "If the user-declared canonical is not similar to the current page, then Google won't ever choose that URL as canonical."

Is it a problem?

Usually a problem

Usually worth fixing. Your canonical signals and Google's choice disagree, so the URL in Search may not be the one you intended, and the signals you control are being outweighed. If Google's choice is the page you would have picked anyway, align your signals with it.

Causes, most likely first

  1. Conflicting signals: the canonical tag names one URL while redirects, internal links or the sitemap point at another.
  2. A canonical pointing at a page that is not really a duplicate, such as every page of a paginated series pointing at page one. Google says not to use the first page as the canonical.
  3. A CMS or plugin writing an incorrect canonical, which Google names as a common cause.
  4. A canonical target that redirects, returns an error or is blocked, so Google cannot use it.
  5. Your content copied or syndicated elsewhere, with Google choosing the other site's URL. Google calls the copycat case rare.
  6. Malicious code injecting a cross-domain canonical or redirect, which Google lists among the causes.

How to confirm it

  1. Inspect the URL and compare "User-declared canonical" with "Google-selected canonical". Google's instructions are then to look at the current page, the declared canonical and the selected canonical side by side.
  2. Run the canonical checker on the page and on the declared target. It shows whether the target redirects or fails.
  3. Check that internal links and the sitemap use the same URL as the canonical tag.

Canonical checker

How to fix it

  1. Decide which URL should be canonical, including whether Google's choice is in fact better for searchers.
  2. Point every signal at it: rel="canonical" on each duplicate, 301 redirects where the duplicate does not need to exist, internal links and sitemap entries.
  3. If the pages are not duplicates, make the difference clear and significant, and stop declaring one as the canonical of the other.
  4. Make sure the canonical target returns 200, is indexable and is not blocked by robots.txt.
  5. Request indexing for the most important URLs. Google says the feature is subject to quotas.

How long recovery takes

Google says that after the fix it "might hold pages in a duplicate cluster for up to two weeks", and that pages "will generally split out faster" when the difference between them is clear and significant.

After a fix, Validate fix on the issue asks Google to recheck the affected URLs. Google says validation "typically takes up to about two weeks, but in some cases can take much longer". Without it, the count still updates as Google recrawls, and an issue leaves the table once 90 days pass with no instance.

Would monitoring have caught it?

Monitoring catches the half of this you control. A change to the canonical tag on a monitored URL is a warning, confirmed on the next scheduled check, so a template or plugin update that rewrites canonicals is reported within hours rather than found in this report later. Google's own choice is visible only in URL Inspection.

stillindexed checks each monitored URL every 30 minutes on Starter and every 15 minutes on Agency, so the change is found on the next check and confirmed before it alerts, rather than waiting for this report to update.

See what monitoring covers

A canonical tag pointing at the wrong URL, platform by platform

Further reading

Sources

Every claim above about how Google behaves is from Google's own documentation, read on 2026-10-06. If Google has changed a page since, Google's page wins and we would like to know.