Why Is Google Indexing the Wrong Canonical URL?

What does “Google chose different canonical than user” mean?

Google groups duplicate or substantially similar pages together and selects one representative URL as the canonical.

Google Search Console may therefore display:

Canonical selection is one of the core areas of technical SEO, because Google treats your tag as a hint, not a rule.

• User-declared canonical: the URL specified in your canonical tag
• Google-selected canonical: the URL Google has chosen to index

If these differ, Google believes another URL represents the duplicate group more effectively.

This is not always an error. Google may have selected the correct version despite an incorrect tag. It becomes a problem when an outdated, insecure or otherwise unwanted URL appears in search instead of the intended page.

Why might Google choose the wrong canonical?

Common causes include:

• The old and new URLs both return a 200 OK response
• An old URL has stronger internal links
• The XML sitemap contains the wrong version
• Canonical tags conflict across duplicate pages
• A temporary redirect is used instead of a permanent one
• Redirect chains make the preferred destination unclear
• The intended page redirects somewhere else
• The canonical destination is blocked or marked noindex
• HTTP, HTTPS, www or trailing-slash versions are inconsistent
• Hreflang annotations reference different URLs
• The selected pages are not sufficiently similar
• The new page appears incomplete or behaves like a soft 404

An old URL may also have more established external links and a longer history. That does not make it permanently preferred, but it increases the importance of sending clear migration signals.

Canonicalisation is one of several issues assessed during a technical SEO audit.

How do redirects affect canonical selection?

If a page has permanently moved, use a direct server-side 301 or 308 redirect from the old URL to the new one.

The redirect should go directly to the final destination:

Old URL → New URL

Avoid chains such as:

Old URL → Temporary URL → New URL

If both URLs remain accessible because users genuinely need them, use canonical tags appropriately. However, when the old page has been replaced completely, a permanent redirect normally sends a clearer signal than leaving both versions live.

Do not block the old URL in robots.txt before Google can process its redirect or canonical information.

After fixing signals, allow time for Google to reindex the site, and make sure the preferred URL is not one of your orphan pages.

How do you fix conflicting canonical signals?

Start by inspecting both URLs in Google Search Console. Confirm which URL Google selected and whether it matches the version currently appearing in search.

Then check the following:

• The preferred URL returns 200 OK
• The old URL redirects directly to it when appropriate
• The preferred page has a self-referencing canonical
• The canonical uses the exact preferred protocol, hostname and path
• Internal links point directly to the preferred URL
• The XML sitemap contains only the preferred URL
• Structured data references the preferred URL
• Hreflang annotations are consistent
• Navigation and breadcrumbs use the preferred version
• No noindex or crawling rule blocks the intended page

The signals should all tell the same story. A canonical tag pointing to the new page will be less persuasive if the sitemap and every internal link continue pointing to the old one.

Our SEO website checklist can help uncover related indexing and URL inconsistencies.

What if Google groups two pages that should be separate?

Google may consider two pages duplicates when their primary content is extremely similar.

This commonly affects:

• Location pages with only place names changed
• Service pages targeting minor keyword variations
• Printer-friendly versions
• Parameter URLs
• Regional pages with nearly identical copy
• HTTP and HTTPS versions

If the pages should remain separate, make their purpose and main content meaningfully different. Changing only the title, introductory paragraph or location name may not be enough.

If they serve the same intent, consolidation is usually cleaner. Retain the strongest page, merge useful information and redirect the redundant URL.

How long does Google take to accept the canonical?

Canonical changes are not always reflected immediately. Google must recrawl the relevant URLs and reassess the duplicate group.

After correcting the signals:

• Request indexing for the most important preferred URL
• Submit an accurate sitemap
• Monitor both versions in Search Console
• Check server logs or crawl data where available
• Avoid repeatedly changing the setup

Google advises that reassessing clustered pages can take time. Larger migrations and less frequently crawled websites may take longer than individual page corrections.

Frequently asked questions

Consistency is the real fix

When Google indexes an unexpected canonical, do not keep changing the canonical tag in isolation.

Check the complete set of signals: redirects, internal links, sitemaps, page content and technical accessibility. Make the preferred URL clearly indexable, remove contradictions and allow Google time to process the changes.

Understanding these relationships is a core part of technical SEO and is usually more effective than repeatedly requesting indexing without correcting the underlying cause.