Should you transfer your disavow file during a domain migration?

Why doesn't the disavow file automatically follow redirects?

Google treats disavow files as domain-specific instructions, not as metadata that automatically migrates with 301 redirects. This technical logic can be surprising since other signals such as domain authority and part of PageRank do transfer well during migration.

The main reason lies in the architecture of Search Console. Each property is treated as a distinct entity. A disavow file uploaded for domain-A.com remains exclusively associated with that property, even if you redirect everything to domain-B.com.

What happens if you forget this transfer?

The toxic links you carefully disavowed on the old domain become active from Google’s perspective once the migration is complete. The search engine does not connect your two Search Console properties, even with perfectly configured 301 redirects.

You end up with a backlink profile that potentially includes spam links, over-optimized anchors, or artificial link networks that you had neutralized. The risk of manual or algorithmic penalties rises mechanically.

How does Google handle the transition of signals during a redirect?

Google gradually transfers several signals from a redirected domain to the target domain: authority, content history, quality signals. But this transfer is neither instantaneous nor 100% complete. Certain elements, such as manual penalties, may follow, while others, like disavows, do not follow by default.

This asymmetry creates situations where a site can inherit the negative aspects of an old domain without benefiting from the protection the disavow file provided. Hence, it's crucial to treat this step as a critical migration task, just like redirects or property verification.

• The disavow file is linked to a Search Console property, not to a domain itself
• 301 redirects transfer signals but not disavow instructions
• A forgotten transfer potentially reactivates toxic links you had neutralized
• The migration of the disavow should be part of your standard migration checklist
• No automatic mechanism manages this transfer for you

Is this recommendation consistent with real-world observations?

Yes, and it's even a welcome confirmation of a practice that experienced SEOs have been applying for years. Cases of migrations where the disavow file was not transferred consistently show a resurgence of problematic links in backlink reports, sometimes accompanied by an unexplained drop in rankings a few weeks after migration.

What's interesting is that Google is finally publicly formalizing what has previously been based on empirical observation. Many practitioners had deduced this necessity through observation, but the lack of official documentation created uncertainty. Mueller clarifies this ambiguity by explicitly confirming the need for a manual transfer.

What nuances should be added to this statement?

The timing of the transfer remains unclear in Mueller's statement. Should the new disavow file be uploaded before setting up redirects, during, or after? Real-world experience suggests doing it as early as possible, ideally as soon as the new Search Console property is verified, but before the redirects begin transferring link juice en masse. [To be verified]

Another point: Mueller talks about "ensuring" correct consideration, but does not mention processing times. A disavow file can take several weeks to be fully integrated by Google. If you migrate without anticipating this delay, you create a vulnerability window where toxic links are active on the new domain.

In what cases does this recommendation not apply?

If you have never used a disavow file on the old domain, this step obviously becomes irrelevant. But be careful: this might be the right time to check if your link profile needs a clean-up before migration.

Some practitioners argue that disavowing has become less critical with improvements in Google Penguin working in real-time. This is partially true: the algorithm now automatically ignores many spam links. However, for edge cases or manual penalties, disavow still remains an essential defensive tool. Neglecting its transfer during a migration poses unnecessary risks.

What should you do during a domain migration?

First step: download the disavow file from your old domain via Search Console before even starting the technical migration. This file can be found in the "Links" section, then "Disavow Links." Keep a local backup copy, dated and archived.

Then, as soon as your new domain is added and verified in Search Console, upload this disavow file to the new property. Don’t wait for the redirects to be in place or for the traffic to switch. The sooner you anticipate, the less you create a vulnerability window during which toxic links could impact the new domain.

What mistakes should you absolutely avoid?

The most common mistake is assuming that Google will automatically link the two domains. Even with perfect 301 redirects and an address change setting in Search Console, the disavow file does not migrate. It is a 100% manual process that has no exceptions.

Another classic pitfall: uploading an incomplete or outdated disavow file. Use the migration as an opportunity to audit your disavow list. Some domains you blacklisted three years ago may no longer exist, while new spam links may have appeared in the meantime. Update your file before transferring it.

How can you check that the transfer worked?

Once the disavow file is uploaded to the new domain, monitor the link report in Search Console for 4 to 6 weeks following the migration. Disavowed links should gradually disappear from the incoming link statistics, or at the very least, be marked as ignored by Google.

Cross-check this verification with a third-party tool like Ahrefs or Majestic to identify any toxic links that might reappear despite the disavow. If you notice that links you thought you had neutralized are still affecting your profile, verify that the file has been uploaded in the correct format and that the syntax is right.

• Download the disavow file from the old domain before any technical actions
• Create and verify the new Search Console property as soon as possible
• Upload the disavow file to the new domain without waiting for the traffic to switch
• Audit and update the list of disavowed links before transfer
• Document the date and time of the transfer in your migration plan
• Monitor the link report for 6 weeks post-migration to validate the consideration