Should you really disavow links from the old domain after a migration?

Why does Google prioritize the disavow file of the new domain?

When site A redirects to site B using 301 redirects, Google progressively transfers signals from the source domain to the target domain. This process includes the transfer of PageRank, but also that of backlinks — including toxic or undesirable links.

The engine considers that the new domain inherits the link profile of the old one. Therefore, maintaining a disavow file on the old domain no longer makes technical sense: Google now reads signals at the destination domain level. This is where the ranking battle takes place, and this is where action should be taken.

What happens if I already have a disavow file on the old domain?

Google indicates that this file will be probably ignored. The term "probably" leaves a margin of uncertainty, but the intent is clear: after a migration, focus your efforts on the new domain.

If you had disavowed toxic links on the old site, these disavows do not automatically follow. You must resubmit a disavow file for the new domain including the same problematic URLs or domains, as long as they now point to the new site (via redirects).

Does this rule apply to all types of redirects?

Mueller's statement mainly targets permanent 301 redirects, standard in SEO for domain migrations. Temporary redirects (302) or other HTTP statuses transmit signals less effectively, and their impact on the transfer of the link profile remains unclear.

In the case of a complex migration (changing URL structures, merging multiple domains), the disavow question becomes more complicated. If some toxic links point to URLs of the old domain that do not redirect to any page of the new site, their impact is likely zero. However, if these links generate 404 errors or redirection chains, they can indirectly cause harm.

• The disavow file must be submitted for the destination domain after a migration with 301 redirects.
• Disavows from the old domain are not automatically transferred: they must be resubmitted for the new site.
• Audit the link profile before migration to identify toxic backlinks to disavow right at the launch of the new domain.
• Monitor traffic and ranking variations in the weeks following the migration to detect any negative impacts related to links.

Is this statement consistent with observed practices in the field?

Yes, and it clarifies a long-unclear point. In practice, many SEOs have found that manual penalties related to links do not always follow after a domain migration, while positive signals (authority, PageRank) were effectively transmitted. This asymmetry led to the belief that Google manages negative signals differently.

Mueller's position confirms that Google treats the new domain as an independent entity in terms of disavowal. But be careful: this logic does not necessarily apply to algorithmic penalties (like Penguin), which can very well follow the domain if toxic links are redirected and still active. [To be verified] on recent migrations with a proven spam link history.

What nuances should be added to this rule?

First point: this recommendation assumes that all redirects are properly set up. If some URLs from the old domain do not redirect (404, deletion), the links pointing to them have no direct impact. Disavowing these links then becomes unnecessary, unless you fear residual confusion from Google.

Second nuance: timing. Submitting a disavow file for the new domain immediately after migration may seem premature. Google needs time to recrawl the redirects and associate the signals. Wait at least a few weeks, until the new domain's Search Console provides reliable data on detected backlinks.

Third nuance: if the old domain remains active in parallel (rare but possible in some strategies), you will need to maintain two distinct disavow files. However, this scenario goes beyond the classic framework of a migration.

In what cases does this rule not fully apply?

If you are doing a partial migration (only part of the site moves to a new domain), the management of the disavow becomes more complex. You will need to precisely identify which links point to the migrated URLs, and which remain on the old domain.

Another edge case: migrations with a radical change in theme. If the old domain dealt with finance and the new one with gardening, Google may not transfer all signals in the same way. Disavowed links on the old domain could have a residual impact if Google retains a trace of the old thematic profile. [To be verified] by observing traffic fluctuations in the months following the switch.

What should you do concretely before and after a domain migration?

Before the migration, export the complete list of backlinks from the old domain from the Search Console. Identify toxic or spam links (over-optimized anchors, dubious domains, detected PBNs) and prepare a disavow file. Do not submit it yet for the old domain if the migration is imminent.

Once the 301 redirects are in place and the new domain is indexed, wait for Google to start crawling the redirects and displaying backlinks in the new domain's Search Console. This delay can vary from a few days to several weeks depending on the size of the site and crawl frequency. Regularly check the Links tab in the Search Console to see the transferred backlinks appear.

When backlinks start to show up, submit the disavow file for the new domain including the toxic URLs or domains identified earlier. Remember: only the links that now point to the new domain via redirects should be disavowed. Orphan links (to 404s from the old site) likely have no impact anymore.

What critical mistakes should you avoid?

First mistake: continuing to submit or update the disavow file for the old domain after migration. It’s a waste of time since Google clearly states it will be ignored. Focus your efforts solely on the new domain.

Second mistake: completely neglecting disavowal thinking that the migration clears everything. If the old domain had a poor link profile (negative SEO attack, past over-optimization), these links will follow via redirects. Ignoring this cleanup can be costly in terms of ranking.

Third mistake: disavowing too broadly out of fear. Only disavow clearly toxic or spam links. Disavowing neutral or slightly weak links can deprive the new domain of useful signals, especially if the overall link profile is thin.

How can you check that the migration did not degrade the link profile?

Compare the number and quality of referring domains before and after the migration. A significant gap may indicate that some redirects are not working properly, or that Google has not fully transferred the signals yet.

Monitor the ranking fluctuations on strategic keywords. A sudden drop without technical explanation (loading times, modified content) can signal a backlink-related issue, especially if inherited toxic links trigger an algorithmic filter.

Use third-party tools (Ahrefs, Majestic, SEMrush) to cross-check data with the Search Console. These tools sometimes detect toxic links that Google does not immediately show, giving you an advantage in disavowing them.

• Export and audit backlinks from the old domain before migration
• Set up clean 301 redirects to the new domain
• Wait for the new domain's Search Console to display the transferred backlinks
• Submit the disavow file only for the new domain
• Monitor traffic and ranking variations for at least 3 months
• Cross-check Search Console data with third-party tools to detect residual toxic links