Should you really upload your disavow list only on the current domain?

Why is this clarification important for site migrations?

During a domain migration, the question of managing toxic links systematically arises. Many SEO practitioners wonder if they should maintain separate disavow lists for each version of the domain (old and new).

Google settles it: if your 301 redirects are properly in place, the search engine automatically transfers all signals — including link disavowals. You therefore only manage a single file on the current domain.

How does Google transfer link signals between domains?

The process relies on permanent redirects. When Googlebot crawls a URL redirected via 301, it consolidates the signals from the old URL to the new one. This includes PageRank, authority, anchor text… and disavowals.

This consolidation explains why maintaining multiple disavow lists would be redundant. The search engine no longer actively crawls the old domain once the migration is processed — it therefore has no reason to consult a disavow file uploaded there.

What are the key takeaways?

• A single disavow file to manage on the Search Console property of the current domain.
• Properly configured 301 redirects are the essential condition for signal transfer.
• Google requires no manual action on old Search Console properties after migration.
• This rule applies to both complete migrations and redesigns with domain changes.
• Disavowal remains a last resort tool — Google recommends prioritizing manual cleanup when possible.

Is this statement consistent with real-world observations?

In practice, yes. SEOs who have migrated domains with active disavow lists notice that disavowed toxic backlinks don't haunt the new domain. Google handles the transfer well.

However — and here's where it gets tricky — the official documentation doesn't specify how long this transfer takes. Is it instantaneous? Must you wait for Google to recrawl all old URLs? [Needs verification] on sites with millions of pages.

In what cases might this rule show its limitations?

First case: partial migrations. If you only redirect part of the site and maintain the old domain active on certain sections, the question becomes more complex. Google says nothing about this hybrid scenario.

Second case: sites that suffered massive negative attacks just before or during the migration. If thousands of spam links point to the old domain, does the disavow uploaded on the new domain block them retroactively? Logic says yes, but no concrete data from Google.

Should you preemptively disavow before a migration?

Let's be honest: many SEOs upload a disavow list "just in case" before migrating, even though Google says it's unnecessary. This is a defensive approach that makes sense on sites with a questionable link profile.

The problem? Google never explicitly confirms that the disavowal is taken into account instantly. If you migrate the day after uploading, does the transfer include a disavowal not yet processed? [Needs verification] — no official answer on this.

What should you do concretely during a domain migration?

First step: audit your link profile on the old domain before the migration. Identify toxic backlinks, spammy ones, or those from link networks. Use standard tools (Search Console, Ahrefs, Majestic, SEMrush) to detect anomalies.

If you already have an active disavow list on the old domain, don't worry. Once the migration is complete and 301 redirects are in place, upload this same list (updated if necessary) to the new Search Console property. Google will handle the rest.

What errors should you absolutely avoid?

Classic mistake: uploading a disavow list on the old domain after the migration, thinking you'll "secure" the old URLs. It's pointless. Google no longer actively crawls a redirected domain — your file will never be taken into account.

Another trap: removing 301 redirects too soon. Some hosting providers or web agencies advise removing them after 6 months to "lighten the server load." Bad idea. Without redirects, Google loses the connection between old and new domain — and your disavow list no longer covers backlinks pointing to the old URLs.

How can you verify that everything is working correctly?

• Verify that all 301 redirects are in place and point to the correct URLs on the new domain (manual testing + Screaming Frog crawl).
• Add the new domain to Search Console and verify ownership via DNS or HTML file.
• Upload the disavow list only on the new domain via Google's official tool.
• Monitor the evolution of your link profile in Search Console for 3 to 6 months post-migration to detect any toxic links that might reappear.
• Verify that old URLs generate no 404 errors (except those intentionally removed).
• Keep 301 redirects active for at least 12 months — ideally, permanently.