Should you really disavow 301 redirects pointing to other domains?

Why does Google consider redirects in indexing?

Google does not treat a 301 redirect as a simple transparent substitution. When Domain A redirects to Domain B, the engine analyzes the full chain and associates link signals with the target domain. This logic aims to prevent manipulation through networks of expired domains.

Specifically, if a backlink points to example-old.com, which redirects in 301 to example-new.com, Google attributes that link to example-new.com. The problem arises when this redirect comes from a domain you do not control or one from which you do not want to inherit toxic signals.

What changes with Mueller's statement?

Traditionally, SEOs believed that disavowing the source URL was sufficient. Mueller clarifies that you need to target the final destination URL in the disavow file if you want to block the transmission of link juice.

This nuance disrupts backlink audits, especially for sites that have migrated or merged. You now have to map not only your direct incoming links but also the redirect chains that end up with you.

In what scenarios does this issue actually arise?

Three classic scenarios: the acquisition of an expired domain with a questionable history that you redirect to your money site; taking over a competitor that pointed to PBN networks; or a poorly cleaned technical migration where old satellite domains continue to redirect.

In each of these cases, you are potentially inheriting toxic links through redirects that you thought were harmless. The risk: a manual or algorithmic penalty by association.

• Google treats 301 redirects as signal transfers, not as mere technical aliases
• Disavowing a source URL is not enough if it redirects — you must target the destination URL
• Cross-domain migrations and acquisitions of expired domains create risks of inheriting toxic profiles
• Thorough mapping of redirect chains becomes a prerequisite for any serious backlink audit

Is this rule really enforced by Google's algorithm?

Let's be honest: this statement lacks documented use cases. Mueller provides no numerical examples or impact metrics. In the field, observations are mixed. [To be verified] as many SEOs report that disavowing the source URL works perfectly in most cases.

The technical logic holds — Google tracks redirects to consolidate signals — but strict enforcement of this rule would create an operational nightmare. Imagine auditing 50,000 backlinks while tracking all possible redirect chains.

When does this recommendation become truly critical?

The real question is about volume and toxicity. If you are redirecting three clean domains to your main site, this disavow target story is anecdotal. However, if you are operating a network of 200 expired domains with mixed histories, then yes, you are in a danger zone.

The risk increases proportionally to the number of redirects and the proportion of spammy links in the source domains. An expired domain bringing in 80% casino or pharma links will pollute your profile, even via 301.

What contradiction does this statement raise with observed practices?

Google has been stating for years that 301 redirects pass almost 100% of PageRank. If this is true, then negative signals should logically transit as well. Yet, in practice, many sites purchase expired domains without facing immediate penalties.

This grey area suggests either that the algorithm applies a contextual filter (legit usage versus clear PBN), or that Mueller describes a technical ideal that is not always strictly enforced by ranking systems.

How to audit inherited redirects on my site?

First step: list all external domains redirecting to yours. Use Ahrefs, Majestic, or Semrush to identify backlinks with HTTP status 301/302. Then, crawl each source domain to check if it really redirects and to which final URL.

Second step: cross-check this list with your current disavow file. If you have disavowed example-spam.com but that domain redirects to yoursite.com/landing, you need to add yoursite.com/landing in the disavow, which is absurd. Solution: block the redirect at the server side or contact the source domain owner.

What to do if I don’t control the domain redirecting to me?

This is the most frustrating case. Someone purchased an expired domain and pointed it to you, intentionally or through negligence. You cannot break the 301 yourself. Your only option: disavow the target URL as Mueller suggests, but that means rejecting your own pages.

Pragmatic alternative: identify the IP and registrar of the source domain, send a takedown request, and if that fails, use a 410 Gone on your target URL to signal to Google that this page no longer exists. Radical, but sometimes necessary to cut off toxic influx.

What mistakes to avoid during implementation?

Never disavow in bulk without fine analysis. Some inherited redirects may come from legitimate authoritative domains that have simply changed architecture. Rejecting these signals would cost you valuable link juice.

Another trap: multiple redirect chains (A > B > C > your site). Google may stop before the end of the chain if it exceeds 3-4 hops. In this case, simply disavowing the final URL resolves nothing — you need to backtrack the chain.

• Thoroughly map all third-party domains redirecting to your URLs
• Check the HTTP status of each incoming link (200, 301, 302, 404) using a crawler
• Cross-reference the redirect list with your existing disavow file to identify gaps
• Contact source domain owners before disavowing your own URLs
• Implement monthly monitoring for newly detected redirects
• Document each disavow decision with the complete redirect chain for future auditing