Should you re-upload your disavow file after migrating to HTTPS?

Why doesn’t the disavow file automatically transfer during an HTTPS migration?

The answer lies in the architecture of Search Console. Each property (HTTP vs HTTPS) is treated as a separate entity within the tool. The disavow file is attached to a specific property, not the root domain.

When you migrate from http://example.com to https://example.com, Google technically views this as two different sites. Therefore, the disavow file uploaded for the HTTP version does not automatically apply to the HTTPS version, even if the content is the same and 301 redirects are in place.

What happens if we forget this step?

The toxic backlinks you had disavowed become active again. Google starts considering them in its PageRank and authority calculations. If your link profile included aggressive spam or farm links, you risk a drop in your rankings.

The HTTPS migration is often seen as a technical operation on the server side. However, from an SEO perspective, it involves a series of actions within Search Console to ensure the continuity of the parameters. The disavow file is just one element among others (geotargeting, URL parameters, de-indexing specific pages).

Does this rule apply to all types of migrations?

The logic is the same for any creation of a new property in Search Console. Whether you are changing protocols, migrating domains, switching to a subdomain or vice versa: as soon as a new property is created, the disavow file must be manually re-uploaded.

Google does not offer a function for duplicating or inheriting parameters between properties. This is a limitation of the interface that may seem outdated, but reflects Google's intention to treat each URL as a unique entity.

• The disavow file is linked to a Search Console property, not the domain
• During an HTTPS migration, create the new property and re-upload the disavow file
• Forgetting this step reactivates previously neutralized toxic backlinks
• The same logic applies to domain migrations or URL structure changes
• No automatic inheritance mechanism exists in Search Console

Is this statement consistent with on-the-ground observations?

Absolutely. I have seen dozens of HTTPS migrations where the ranking declined a few weeks after the switch, for no apparent reason. The audit consistently revealed that the disavow file had not been re-uploaded. Toxic backlinks, disavowed for years, were becoming active again.

What is surprising is that Google has never automated this step. The Search Console interface could offer a transfer option when adding a new property. The fact that it remains a manual process in 2025 suggests that Google views the disavow as a sensitive action requiring human validation.

What nuances should we add to this recommendation?

First point: if you have never uploaded a disavow file, this step obviously does not concern you. However, check whether a predecessor or an external agency did it without your knowledge. Download the current file from the HTTP property before migration to keep a record.

Second nuance: the processing time. Once the file is re-uploaded to the HTTPS property, Google takes several weeks to reprocess the entire link profile. It is not instant. If you notice fluctuations in the days following the migration, it is normal and likely related to the protocol change itself, not the disavow. [To check]: Google has never provided a specific timeline for reprocessing a disavow file after re-upload.

In what cases does this rule not apply?

If you use a domain property in Search Console, the disavow file theoretically applies to all variants (HTTP, HTTPS, www, non-www). But beware: domain properties require DNS verification and are not available for all types of sites.

In practice, most SEO sites still work with URL-prefix properties, where Mueller's rule fully applies. If you have any doubts, re-upload the disavow file to the new HTTPS property: there is no risk in duplicating the operation.

What should you do concretely before an HTTPS migration?

First, download the current disavow file from the HTTP property in Search Console. Tools > Disavow Links > Download List. Keep this file locally: it's your backup. If you have never uploaded a disavow, this step confirms that there is nothing to transfer.

Next, create the new HTTPS property in Search Console before the switch if possible. Verify it using your preferred method (DNS, HTML file, Google Analytics). Once the property is validated, immediately upload the disavow file. This allows Google to start processing it with the first crawls after migration.

What mistakes should be avoided during and after the migration?

A common error: switching to HTTPS, checking that the 301 redirects work, and considering the work done. Aspects related to Search Console are often overlooked. The disavow file is just one example among others: also make sure to check geotargeting settings, address changes, and any ongoing manual actions.

Another pitfall: uploading an outdated disavow file. If you did a cleanup of toxic links several years ago, ensure that the list is still relevant. Some disavowed domains may have been acquired and now offer legitimate content. A quick audit with Ahrefs or Majestic can confirm that the listed domains are still problematic.

How can you verify that the disavow file is active on the HTTPS version?

Go back to Search Console > Tools > Disavow Links. If the file appears and shows the date of your last upload, that's a good sign. But be cautious: the interface does not explicitly confirm that the file is processed. Google does not provide any indicators of progress or validation.

Monitor your rankings for sensitive queries in the weeks following the migration. An unexplained drop may signal that toxic backlinks are becoming active again. If you notice a decline, first check that the disavow file has indeed been re-uploaded. This type of diagnosis can be complex to conduct alone, especially on sites with an extensive link profile. Consulting a specialized SEO agency can provide tailored support, including regular link audits and structured post-migration monitoring.

• Download the disavow file from the HTTP property before migration
• Create and verify the new HTTPS property in Search Console
• Re-upload the disavow file to the HTTPS property as soon as it is validated
• Ensure that other Search Console parameters are also transferred
• Monitor rankings in the 4-6 weeks post-migration
• Document the operation to avoid forgetting during future migrations