Can rel=canonical really transfer a penalty from one domain to another?

Why does Google transfer penalties via rel=canonical?

The rel=canonical is not just a simple indicator of preferred content. Google treats it as a signal of authority consolidation between two URLs or domains. When you point a canonical from domain A to domain B, you are explicitly asking Google to consider B as the official version.

The issue? This consolidation is bidirectional concerning signals. If domain A accumulates toxic backlinks, spam patterns, or a manual penalty, these negative markers migrate to B. Google does not filter: it aggregates the entire profile of signals, both positive and negative.

What types of penalties are involved?

Mueller distinguishes two categories in his statement: manual penalties (visible manual actions in Search Console) and algorithmic signals. The former are documented and traceable. The latter are more insidious: devaluation of the link profile, manipulation patterns detected by core algorithms, spam history.

A domain may appear clean on the surface but carry an invisible toxic history that will be transmitted via canonical. This is particularly insidious during redesigns or migrations: you think you are starting with a clean slate, but you are actually bringing over all the negative baggage.

Why block via robots.txt instead of just removing the canonical?

Removing the canonical is not enough. As long as the old domain remains crawlable, Google can continue to associate the two properties through other signals: residual redirects, cross-mentions, patterns of duplicate content. The robots.txt file enforces a clear separation by preventing any crawl of the toxic domain.

The separate user redirect mentioned by Mueller aims to preserve visitor experience without creating an SEO bridge. Technically, this can involve a client-side JavaScript redirect or a meta refresh that Googlebot ignores. The goal: to guide humans without providing a consolidation signal to bots.

• The rel=canonical transfers the entire signal profile, not just positive authority
• Algorithmic penalties (not visible in Search Console) also migrate silently
• Blocking in robots.txt is the only guaranteed method to cleanly sever SEO links between two domains
• User redirects (JS, meta refresh) help maintain UX without creating an SEO link
• A domain can be toxic without a visible penalty: algorithmic history matters as much as manual actions

Is this statement consistent with real-world observations?

Yes, and it confirms what SEO practitioners have observed for years during poorly prepared migrations. Sites migrating from a penalized domain via canonical have seen their rankings plummet within a few weeks, even with impeccable content and technique on the new domain.

The rarely documented critical point by Google: the duration of persistence of these negative signals. Even after cutting the canonical, how long does it take for Google to completely dissociate the two domains? [To be verified] because Mueller gives no timeframe. Observations suggest at least 3 to 6 months, sometimes longer if the toxic link profile is massive.

Is the robots.txt advice really the best solution?

It is a radical yet effective solution. It forces Google to treat the two domains as completely distinct entities. But it comes at a cost: you lose all the positive SEO juice that may still exist on the old domain.

A more nuanced approach in some cases: conduct a granular audit of the link profile of the old domain. If only a portion of the backlinks is toxic, a mass disavow before migration may suffice. But it’s a risky bet, as algorithmic signals are not limited to links: historical user behavior, content patterns, everything counts.

When does this rule not apply?

Mueller's statement specifically targets inter-domain migrations from a penalized site. It does not concern standard on-site canonicals (www vs non-www, HTTP vs HTTPS) where no toxicity is involved.

Another edge case: multi-regional or multi-language domains with cross canonicals. If a regional subdomain accumulates localized negative signals, the transfer via canonical may be partial depending on the geolocation of queries. But again, Google remains vague about the granularity of this transfer.

What should be done before any migration from a risky domain?

First step: audit the complete history of the source domain. Search Console will show you active manual actions, but not algorithmic downgrades. Analyze the organic traffic evolution over 2-3 years: a sharp drop not correlated to a known update often signals an underlying algorithmic issue.

Second step: test the dissociation before the final migration. Implement the robots.txt block on the old domain for 2-3 weeks while monitoring the metrics of the new domain. If you see an improvement in rankings, it was indeed a toxicity transfer issue.

What mistakes should be absolutely avoided?

Classic mistake: using rel=canonical as a quick fix during a redesign. It’s tempting because it avoids managing complex 301 redirects, but if the old site has any questionable history, you're importing its baggage.

Another trap: combining canonical and 301 from a penalized domain. Some think that 301 “overrides” the canonical or vice versa. False. Both are consolidation signals and both can transfer toxicity. If you need to separate, block with robots.txt AND remove any form of server-side redirect.

How to check that the separation is effective?

Monitor the server logs to confirm that Googlebot no longer crawls the old domain after implementing the robots.txt. Also verify that the pages of the old domain gradually drop out of the index (site: command in Google).

On the new domain, track the ranking fluctuations on your strategic queries. If you notice gradual improvement over 4-6 weeks after dissociation, that's a sign that Google is beginning to treat the new domain independently.

• Audit the history of the source domain (Search Console, traffic evolution, link profile over 2-3 years)
• Block the old domain in robots.txt before any canonical migration
• Set up a user redirect (JS or meta refresh) to maintain UX without an SEO signal
• Remove any 301 redirects between the two domains if toxic history is confirmed
• Monitor server logs to verify the cessation of crawling of the old domain
• Track the new domain's rankings over 4-6 weeks to validate dissociation