Why Has Google Chosen a Different Canonical URL?

A canonical URL is the representative address selected for a set of duplicate or very similar pages. Your website can indicate a preference, but Google may choose a different representative.

That is not automatically an error. The first question is whether Google’s choice is a suitable page for customers and the business. If it is not, investigate conflicting signals rather than repeatedly changing a canonical tag without a plan.

Compare the two addresses

In Search Console, record the user-declared canonical and Google’s selected canonical where available. Open both addresses and compare their content, response and final destination.

Check simple differences first: HTTP versus HTTPS, www versus non-www, trailing slashes, parameters or an older route.

The indexed-page checking guide helps collect the evidence. Do not assume that two similar-looking addresses serve identical content or that the current page matches an older crawl.

Treat canonicalisation as a set of signals

Google’s canonicalisation documentation explains that redirects, canonical declarations and sitemap inclusion provide signals, with different strengths. Consistency helps communicate the intended representative.

Internal links should also lead naturally to the preferred destination. A sitemap naming one address while navigation consistently points elsewhere creates an avoidable mismatch.

Canonical preference is not a device for forcing unrelated pages to consolidate.

A worked audit example

Consider an illustrative decorator website with a current service route and an old campaign variation. Both now show substantially the same service information.

Signal	Current observation	Proposed correction
Preferred public page	New service route	Retain as the intended destination
Canonical declaration	Old campaign points to itself	Review whether it should point to the service route
Main navigation	Uses the current route	Keep consistent
Sitemap	Contains both versions	Review intended indexable entries
Old links	Still point to campaign address	Update links where controlled
Campaign requirement	No longer needed separately	Consider a relevant permanent redirect

This is a fictional decision exercise. A live campaign with different content or contractual requirements might need another approach.

Decide whether both pages should exist

If the older page no longer serves a distinct purpose, a redirect may be clearer for visitors as well as crawlers. Our redirect guide explains that mechanism.

If both pages genuinely need to remain, check whether they are actually duplicates and whether the declared relationship makes sense. Do not canonicalise a detailed service page to a broad homepage just because both mention the business.

For location pages, see near-duplicate location content. A technical declaration does not turn weak repeated content into useful local information.

Inspect the implementation, not only the setting

Ask the developer to check the rendered page and response headers. Confirm that templates, plugins or scripts are not outputting conflicting declarations.

Check that the preferred destination is available, relevant and not itself redirected or unintentionally excluded. Follow the complete route, not only the first response.

The technical SEO guide helps place the problem alongside access, status codes and site structure.

Change one coherent set of signals

Write down the intended representative and why it serves the customer. Align the relevant links, sitemap and declarations with that decision, testing in a safe environment before release.

If a redirect is part of the solution, verify the destination and avoid chains. Our Page with redirect guide explains which Search Console exclusions are expected afterwards.

Keep a record of the changes and allow time for reprocessing. There is no reliable promise that a selected canonical changes immediately.

Judge the outcome by the right page

Success means the intended, useful destination is being understood consistently. It does not mean every duplicate variation must be indexed separately.

If the page is instead reported as crawled but not indexed, investigate its actual status rather than assuming canonicalisation is always responsible.

Choose a representative URL, make its purpose clear and keep the technical signals consistent. Use the evidence from those checks to decide whether a canonical setting needs changing.

Thinking about your own rebuild?

Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.

Tell us about your project↗

• Google indexing
• Small business