Disavow file: when to use it and how to build it correctly

The disavow file is a Google Search Console tool that lets you tell the search engine which links to ignore when evaluating your site. Using it without a clear rationale can be just as damaging as not using it at all: this article explains the actual conditions that warrant its use and the process for building the file without errors.

A practical guide to building a disavow file correctly, with criteria for selecting links to disavow and mistakes to avoid.

What the disavow file is and what it actually does

The disavow file is a plain-text document uploaded to Google Search Console to tell Google that certain links should not be factored in when evaluating a site's authority and reputation. It does not remove those links from the index or from the sites that published them: it simply communicates to the search engine that the site owner is distancing themselves from those links.

The tool exists because, under certain circumstances, a site can accumulate backlinks that actively harm it: links from spam networks, hacked sites, aggressive linkbuilding campaigns from the past, or negative SEO attacks. When those links trigger a manual penalty or create a meaningful risk of triggering one, the disavow file is part of the technical response.

It's worth clarifying that Google has significantly improved its ability to automatically ignore low-quality links without any webmaster intervention. The official Google documentation is explicit on this point: the tool is intended for specific cases, not as routine maintenance of a backlink profile.

Disavowing links in bulk without a clear rationale can hurt rankings: if the file includes domains from which the site is receiving real value, that value disappears from Google's perspective.

When it makes sense to use the disavow file

The short answer is: when there is an active manual penalty for unnatural links, or when there is solid evidence that the backlink profile concentrates a significant volume of manipulative links that could trigger an algorithmic penalty. Outside those two situations, the general recommendation is not to intervene.

To determine whether a site is in either of those situations, it's worth carefully reviewing the process of how to audit a site's link profile step by step, since the disavow file only makes sense as the final step of a prior diagnosis — not as a starting point.

Active manual penalty

If Google Search Console shows a notice in the "Manual Actions" section related to artificial or unnatural links, the disavow file is one of the required actions for submitting a reconsideration request. In this case, the process follows a mandatory sequence:

  1. Identify the problematic links using tools such as Ahrefs, Semrush, or the Search Console backlink export itself.
  2. Attempt to remove those links by contacting the webmasters of the linking sites. Only links that genuinely cannot be removed go into the disavow file.
  3. Build the disavow file with the remaining domains or URLs.
  4. Upload it to Google Search Console.
  5. Submit the reconsideration request with documentation of the process.

Skipping the webmaster outreach step and going straight to the disavow file can result in Google rejecting the reconsideration request. The platform expects to see evidence of a genuine effort to clean up the profile.

Algorithmic risk from a history of aggressive campaigns

When a site's history includes linkbuilding campaigns that clearly violate Google's guidelines — private blog networks (PBNs), large-scale link exchange schemes, buying backlinks on penalized sites — and no manual penalty has been received yet, the question is whether it makes sense to use the disavow tool proactively.

The answer depends on the scale of the problem. If the audit reveals that this type of link makes up a significant portion of the total profile (not just a handful), and if algorithm updates related to spam have already impacted the site's traffic, intervention may be reasonable. To understand how those algorithms process link quality signals, it's useful to review how Google updates affect a link strategy.

Negative SEO attack

This is the scenario where a third party points thousands of spammy backlinks at the site in an attempt to damage its rankings. In practice, Google is fairly robust at detecting and neutralizing this type of attack without webmaster intervention — but if the audit confirms an unusual volume of spammy links that appeared in a short period, and there is a correlation with a traffic drop, the disavow file can be part of the response.

How to build the file correctly

The disavow file is a plain-text file (.txt) with a specific format. Google rejects files with formatting errors, so technical precision matters.

File format

Each line in the file contains a URL or a domain. Lines that begin with # are comments and are ignored by Google; using them to document the process is considered good practice.

Basic structure example:

# Disavow file - Site: ejemplo.com
# Date: 2026-05-11
# Reason: spam network links identified in audit

# Full domains (disavows all links from that domain)
domain:sitio-spam.com
domain:red-de-pbn.net

# Individual URLs (when there is only one specific link from a domain)
https://sitio-parcialmente-problematico.com/pagina-spammy/

Domain vs. URL: when to use each

The choice between disavowing an entire domain or a specific URL has significant implications:

  • Use domain: when the domain is clearly spam, has no legitimate content, or when it has multiple pages pointing to the site with suspicious anchor text variations.
  • Use a specific URL when the domain is generally trustworthy but has one particular page with a problematic link (for example, a low-quality directory page within a site that is legitimate in other contexts).

In most large-scale cleanup situations, working with domain: is preferable because it's more efficient and reduces the risk of leaving pages from the same domain outside the disavow's scope.

What not to include in the file

This is where the most errors occur. The following should not be included in the disavow file:

  • Low-authority domains that are simply irrelevant to the niche but are not active spam.
  • Links from sites with weak metrics but no clear signals of manipulation.
  • The site's own domain or its own subdomains.
  • Domains from which the site receives real traffic, even if their metrics are modest.
  • Competitor domains that link naturally (even if that's not desired).

Before including a domain, it's worth running through the analysis of concrete risk signals. The article on how to identify unreliable sites for a link campaign details the criteria that distinguish a questionable site from one that is simply weak.

Tools for building the candidate list

The process of identifying links that are candidates for the disavow file requires cross-referencing data from multiple sources:

  • Google Search Console: export the links report. It's the most direct source, though not exhaustive.
  • Ahrefs / Semrush: allow filtering backlinks by quality metrics (Domain Rating, toxicity score, anchor text, link acquisition velocity). Useful for prioritizing manual review.
  • Manual review: no automated tool replaces a visual inspection of the linking sites. A high toxicity score is a warning signal, not an automatic verdict.

According to the Ahrefs guide on the disavow tool, a considerable proportion of the "toxic backlinks" flagged by automated tools do not represent real risk — which reinforces the need for manual review before building the file.

Common mistakes when using the disavow file

Beyond the mistake of including legitimate domains, there are other problematic patterns that come up frequently:

Uploading the file without documenting the process

If the disavow file is uploaded as part of a reconsideration request for a manual penalty, Google expects the accompanying message to describe what was done: which sites were contacted, when, with what outcome, and which ones ended up in the file because the link could not be removed by other means. A disavow file without context is not sufficient.

Uploading the file and never revisiting it

The disavow file is not a one-time process. If the backlink profile continues to grow with links of questionable origin, the file needs to be updated. Conversely, if domains that were in the file have improved in quality or were included by mistake, they should be removed in later versions of the file.

Confusing the disavow with a solution to algorithmic penalties

Algorithmic penalties — such as those triggered by spam updates — do not have a manual reconsideration process. The disavow file can help clean up the profile so the algorithm sees it more favorably in the next update cycle, but there is no guarantee of immediate recovery and no formal appeals channel. How those penalties work is explained in detail in the article on manual and algorithmic link penalties in Google.

Using it as routine maintenance

Some voices in the industry recommend reviewing and updating the disavow file quarterly as backlink profile hygiene. This practice is not supported by Google's official documentation and can create more risks than benefits if executed without a clear rationale. The tool is designed for situations of concrete, demonstrated risk — not for systematic preventive maintenance.

How to upload the file to Google Search Console

Once the file is built and reviewed, the upload process is straightforward:

  1. Log in to Google Search Console with the account that has verified access to the property.
  2. Go to the link disavow tool: https://search.google.com/search-console/disavow-links
  3. Select the correct property (verify that it is the exact URL of the site, since Search Console handles separate properties for versions with and without www, and for http and https).
  4. Upload the .txt file. Google confirms the upload and shows how many lines it processed.

Google takes weeks to process the file's contents and reflect its effects on crawling and indexing. There is no confirmation panel indicating "this domain has been ignored": the effect is observed over time through the evolution of the profile and, in the case of a manual penalty, through the response to the reconsideration request.

If the disavow file ever needs to be removed — for example, if it was uploaded with serious errors or if it's determined that it wasn't appropriate to use it — the same tool allows it to be downloaded, modified, or deleted. Deleting the entire file means Google will once again factor in all the links that were previously disavowed.

Process summary

The disavow file is a targeted intervention tool, not a standard component of every backlink strategy. Its use is appropriate when there is an active manual penalty that includes artificial links, or when a rigorous audit reveals a pattern of genuine risk — not merely low metrics — across a significant portion of the backlink profile.