Is it really necessary to transfer your disavow file when migrating to a new domain?

Why doesn't the disavow file automatically follow the domain?

The Search Console treats each domain property as a separate entity. When you migrate from old-domain.com to new-domain.com, Google does not automatically link the two properties, even with perfectly configured 301 redirects.

The disavow file is stored at the level of the Search Console property, not at the site level itself. This technical architecture explains why the disavow action does not migrate along with the content. Google sees you as creating a new web presence, independent of the old one.

Which links are affected by this transfer?

All the toxic backlinks you had disavowed on the old domain can, theoretically, point to the new one through redirects. If a spammy link pointed to old-domain.com/page and you redirect to new-domain.com/page, that link becomes active for the new domain.

The problem arises especially with artificial link networks, low-quality directories, or over-optimized anchors that you had neutralized. Without the transfer of the disavow file, these negative signals become visible to the Penguin algorithm and may trigger algorithmic penalties.

How does Google handle disavowals during the transition?

During the period when both domains coexist (old with redirects + new active), Google crawls both properties. Disavows from the old domain remain active only for that property. But as soon as Googlebot follows a 301 redirect and indexes the new URL, the disavow no longer applies.

This transition creates a window of vulnerability where toxic links can impact your ranking. The duration depends on how quickly Google recrawls and reindexes your pages on the new domain. For an average site, expect between 2 and 8 weeks for complete migration.

• The disavow file is linked to the Search Console property, not the DNS domain or the site's content
• No automatic transfer exists, even with a declared address change in the Search Console
• 301 redirects transfer PageRank and authority, but not manual disavow actions
• A site migrated without transferring the disavow file is exposed to the same toxic links as before the initial cleanup
• The risk window runs from the detection of redirects until the full reindexing of the new domain

Is this recommendation consistent with real-world observations?

Yes, and it is actually a frequent source of post-migration traffic drops. We regularly observe sites losing 15 to 30% visibility in the weeks following a migration, without any apparent technical cause. Analysis often reveals that the disavow file was not transferred.

What's surprising is that Google still doesn't offer an automatic mechanism for this operation. The address change tool in Search Console should logically include this option. Its absence suggests either a technical limitation or a desire to force SEOs to reconsider their disavow policy with each migration.

What nuances should be added to this guideline?

Not all sites need to transfer a disavow file. If you have never disavowed links, this step is obviously unnecessary. But beware: absence of an active file does not mean absence of toxic links. A migration is the perfect time to audit your backlink profile.

A second point: do not blindly transfer an old disavow file without auditing it. Links disavowed 3-4 years ago may have become inactive (expired domains, 404 pages). Download your current file, cross-check with a recent crawl of backlinks, and clean it up before submitting on the new domain. [To verify]: Google has never communicated about the number of still-active domains in average disavow files, but experience often shows 20-40% dead links.

In what cases does this operation become critical?

If your site has historically suffered from a Penguin penalty or a manual action for artificial links, transferring the disavow file is non-negotiable. Without it, you risk seeing the penalty replicate on the new domain within 4 to 12 weeks post-migration.

Another critical case: sites that have previously used black hat techniques (PBNs, massive exchanges, over-optimized exact anchors). Even if these practices are dated, the links remain in Google's index for years. A migration without disavowal is like starting with the same algorithmic burden.

What actions should be taken before migration?

Export your current disavow file from the old Search Console property (Security and manual actions > Disavow tool). This text file contains the list of domains and URLs that you have disavowed. Simultaneously download a complete export of your current backlinks via Search Console or a third-party tool (Ahrefs, Majestic, Semrush).

Cross-reference both sources to identify disavowed links that still point to your site. Use a backlink crawler to check their current HTTP status. Remove from the disavow file domains that return 404, expired domains, or links that have since become nofollow. This cleaning prevents unnecessarily polluting your new profile.

How to execute the transfer right after going live?

As soon as your new domain is active and the 301 redirects are in place, add the new property in Search Console. Do not delay: the window between crawling the redirects and transferring the disavow file is your period of maximum vulnerability.

Upload the cleaned disavow file via the disavow tool of the new property. Google indicates that processing typically takes a few days to a few weeks. During this time, monitor your positions on strategic queries with a daily rank tracker. A sharp drop in the first 15 days may signal an impact from toxic links.

What mistakes to avoid during this operation?

Do not delete the old Search Console property immediately after migration. Keep it for at least 6 months to monitor residual redirects and ensure that Google has properly migrated the majority of the crawl budget. Some backlinks still point to the old domain months after migration.

Another common mistake: transferring the disavow file but forgetting to monitor new toxic backlinks acquired during migration. Spammers sometimes target new domains with negative SEO campaigns. Set weekly alerts on your new backlinks to quickly detect any anomalies.

• Export the disavow file from the old Search Console property before migration
• Audit and clean the file: remove expired domains and dead links
• Create the new Search Console property as soon as the new domain goes live
• Upload the cleaned disavow file on the new property within 48 hours after migration
• Monitor daily positions during the first 30 days post-migration
• Keep the old Search Console property active for at least 6 months