Canonical Points to a Different Internal URL: When to Fix It

What this signals

This audit flag means a page (Page A) contains a rel="canonical" tag that points to a different internal URL (Page B) rather than to itself. In SEO terms, Page A is "canonicalised." You are telling search engines that Page A and Page B are duplicates, that Page B is the preferred version, and that indexing and link signals should be consolidated onto Page B. Crawlers like Screaming Frog and Sitebulb surface this so you can confirm the intent was deliberate, not an accident of your CMS or template.

When it is correct

Cross-canonicalisation is exactly the right tool when you genuinely have duplicate or near-duplicate content and want one URL to absorb the ranking signals. Common legitimate cases include:

Parameter and tracking URLs: filtered, sorted, or session-tagged versions of a page (for example ?color=blue or ?utm_source=...) canonicalising back to the clean URL.
Print and AMP variants: alternate renderings of the same content pointing to the main HTML page.
Syndicated or republished content: a secondary copy pointing to the original.
HTTP/HTTPS or www/non-www legacy duplicates that resolve to one preferred host.

In these cases the canonical consolidates inbound links and relevance signals onto the page you actually want ranking. If Page A has external backlinks, Page B inherits that value. This is the intended, healthy behaviour.

When it is a problem

The flag becomes a real issue when a unique page removes itself from the index. If Page A has its own content, its own keywords, and its own search intent, but canonicalises to an unrelated or only loosely related Page B, you are voluntarily asking Google to drop Page A from results. The likely outcome:

Lost indexation: Page A may be deindexed even though it could rank on its own.
Cannibalised rankings: traffic and link equity flow to a page that does not match the query.
Orphaned value: backlinks earned by Page A get redirected to a page that may not deserve or convert them.

This often happens by mistake: a hardcoded template canonical, a copy-pasted homepage canonical, a staging URL left in place, or a plugin defaulting every page to a single "primary" URL.

How Google treats it: a hint, not a directive

This is the single most important nuance. Unlike a noindex meta tag, which Google must obey, rel="canonical" is only a hint. Google weighs your declared canonical alongside other signals (internal links, sitemaps, redirects, content similarity) and may choose a different canonical than the one you specified. That is why Search Console reports "Duplicate, Google chose different canonical than user." A weak or contradictory canonical signal can be ignored entirely, so you cannot rely on a mistaken canonical to "sort itself out", but you also should not assume every cross-canonical is silently working as intended. Always verify.

How to diagnose which pages

Run a crawl in Screaming Frog or Sitebulb and isolate URLs where the canonical target differs from the address. Then ask, page by page: does Page B genuinely represent the same content as Page A? Check in Google Search Console with the URL Inspection tool to see the "Google-selected canonical" versus your "User-declared canonical." Where they disagree, or where a unique page points away from itself, you have found a candidate to fix.

How to fix it

Decide the canonical intent first, then implement. If the page is a duplicate, leave the cross-canonical in place and confirm Page B is itself self-canonical and indexable. If the page is unique and should rank, give it a self-referencing canonical so it points to its own URL:

<!-- Unique page that should index on its own -->
<link rel="canonical" href="https://example.com/page-a/" />

<!-- Parameter duplicate consolidating to the clean URL -->
<!-- on https://example.com/page-a/?utm_source=newsletter -->
<link rel="canonical" href="https://example.com/page-a/" />

Use absolute URLs, match your preferred protocol and host exactly, and make sure the canonical target returns HTTP 200 and is not itself canonicalised elsewhere or blocked by robots.

Common mistakes

Canonicalising everything to the homepage. A template that drops <link rel="canonical" href="https://example.com/"> on every page tells Google your entire site is one page. This is one of the most damaging and most frequent errors.
Wrong paginated canonicals. Pointing page 2, 3, and 4 of a series back to page 1 hides those URLs and their products or articles. Each paginated page should self-canonicalise.
Canonical chains. Page A points to Page B, which points to Page C. Consolidate directly to the final destination.
Mismatched protocol or trailing slash, which creates an unintended new "duplicate" the canonical never resolves.

FAQ