Disavow File Builder

What Is a Disavow File?

A disavow file is a plain text file submitted to Google through Search Console's Disavow Links tool, instructing Google to ignore specific backlinks when evaluating your site's ranking signals. It is used when a site has acquired links that may be harming its search performance: either through a manual link penalty, an algorithmic signal from low-quality link patterns, or as a precautionary measure following a link audit that identified potentially toxic referring domains.

Google introduced the Disavow Links tool in 2012 following a period of aggressive link scheme penalties. The tool allows site owners to signal which links they do not endorse and would like Google to discount, without needing to wait for each link to be removed at its source. Removal requests can take weeks or months to be processed, and some sites hosting toxic links are unresponsive entirely. The disavow file provides an alternative that works for any link regardless of whether the source site cooperates with a removal request.

Google's own guidance on the disavow tool, available in their Search Console Help documentation, notes that the tool is an advanced feature and that most sites do not need to use it. It should be used only when there is evidence that specific links are causing or are likely to cause harm, not as a routine measure for removing any low-quality link. The original announcement from Google's Search team provides further context on when the tool is appropriate.

How to Use the Disavow File Builder

1. Collect your list of domains and URLs to disavow. These come from your link audit, your SEO tool's toxic link report, or a manual review of referring domains flagged as spam, PBN, or link scheme sources.
2. Paste the list into the input box, one entry per line. You can paste plain domain names (example.com), domains with protocol (https://example.com), or full URLs (https://example.com/page/link/).
3. Add an optional case reference note in the note field. This is embedded as a comment in the file and is useful for record-keeping when managing multiple disavow submissions across clients or audits.
4. Review the summary cards showing how many entries were classified as domain-level, URL-level, or invalid.
5. Check the generated file preview on the right to verify the format looks correct before downloading.
6. Click Download to save the disavow.txt file. Upload it through Search Console: Search Console, then Legacy tools and reports, then Disavow links.

Domain-Level vs URL-Level Disavow: When to Use Each

The choice between disavowing an entire domain or just specific URLs from that domain is one of the most important decisions in a disavow campaign:

Domain-level disavow is the most common approach for toxic link removal because most toxic links come from sites where all content is low quality rather than from a single problematic page on an otherwise legitimate domain. URL-level disavow is appropriate when a site has placed a paid link or a keyword-stuffed footer link on specific pages, but has editorial content on other pages that you would not want to disavow.

Who Uses the Disavow File Builder

SEO consultants managing penalty recovery

SEO consultants use the disavow file builder after completing a link audit for a penalised site. Once the toxic domains have been identified and confirmed, the builder converts the list into a correctly formatted file in seconds. The alternative is manually writing each domain: prefix by hand, which introduces formatting errors that cause Google to reject individual lines without clear feedback. The builder eliminates this risk by handling the formatting automatically and providing a visual preview before download.

In-house SEO managers running proactive link hygiene

In-house SEO managers use the builder as part of a routine link hygiene programme. Quarterly link audits identify a rolling set of toxic or low-quality referring domains that have appeared since the last review. Rather than maintaining a manual disavow file and editing it with each new batch, the builder allows them to generate a clean, dated file for each submission cycle, with a case reference note that makes the submission identifiable in the Search Console submission history.

New SEO agencies inheriting penalised clients

Agencies taking on a new client with an existing manual action or ranking suppression from link-related issues use the builder to process the toxic link list identified during the initial audit. The speed of file generation allows the agency to submit the disavow as part of the first deliverable, beginning the recovery process quickly while the longer-term content and link building strategy is being planned. The file's comment header documents which agency submitted the disavow and on what date, which is valuable for ongoing record-keeping.

Website owners managing negative SEO attacks

Website owners who identify a negative SEO attack, where a competitor or malicious actor is pointing spam links at their site, use the disavow builder to quickly generate a disavow file for the attacking domains as soon as they are identified. Speed matters in a negative SEO scenario: the sooner the disavow is submitted, the shorter the window during which the attacking links can influence algorithm evaluation. The builder's paste-and-download workflow is the fastest path from a domain list to a submitted file.

When to Use the Disavow Tool

Use the disavow tool when there is a confirmed manual action for unnatural links, when there is strong evidence that specific links are suppressing rankings through algorithmic signals, or when a site has a very high proportion of toxic links following a historical aggressive link building campaign that is now causing problems. Also use it as a precautionary measure when inheriting a site with a clearly problematic link profile, even if no manual action has been received, to reduce the risk of future penalty exposure.

Do not use the disavow tool for links that are merely low quality but not harmful, for links from legitimate sites in unrelated niches, or for links you did not build yourself unless you have evidence they are causing harm. Disavowing too aggressively removes links that may be providing neutral or mildly positive signals, which can reduce the diversity of the link profile without producing any ranking benefit.

Coordinating Disavow Campaigns Across Multiple Properties

When managing disavow programmes across multiple Google Search Console properties, maintaining a consistent process for each property prevents the cross-contamination of disavow files and ensures that each property file reflects only its own link profile. A common operational mistake is submitting a disavow file prepared for one property to a different property, which instructs Google to ignore links that may be legitimate for the second site. Labelling each downloaded file with the property name and date, and maintaining a separate master domain list per property, eliminates this risk.

For sites with multiple regional or language properties such as country-specific subdomains or separate domains, a toxic link targeting the international domain may not affect the country-specific properties, and vice versa. Run separate link audits and maintain separate disavow files for each property. The disavow file builder case reference note field is useful here: entering the property domain and date in the note field embeds the property identifier in the file header, making it immediately identifiable when reviewing submission history in Search Console.

After submitting a disavow file, record the submission in a log that includes the submission date, the number of domains and URLs included, the triggering reason, and any linked reconsideration request reference. This log becomes the audit trail for future reviews and is particularly important when an agency relationship ends and a new agency takes over. Handing over a well-documented disavow history ensures continuity: the incoming agency knows which domains have already been disavowed, when, and why, avoiding both duplicate submission and the risk of inadvertently submitting a new file that omits entries from a previous submission.

Common Disavow File Mistakes to Avoid

Submitting a disavow file without first attempting link removal requests is a mistake Google's own guidance cautions against. The disavow tool is intended as a last resort for links that cannot be removed, not a first step. Document removal request attempts before submitting the file, as this documentation may be required as part of a reconsideration request if a manual action is involved. A standard removal request workflow involves identifying contact email addresses for each toxic domain, sending a templated removal request, and recording the response or non-response with timestamps before proceeding to disavow.

Using URL-level disavow for sites that are entirely spam wastes disavow file lines and leaves other links from the same domain active. If an entire site is a link farm or PBN, disavow at the domain level to cover all existing and any future links from that domain. URL-level entries should be reserved for specific problematic pages on sites where other pages are legitimate.

Forgetting to re-submit the disavow file when adding new entries is a common operational error. Google does not accumulate disavow submissions: each new submission replaces the previous one. If you submitted a file in January and want to add new domains in April, you must upload a new file that contains both the original entries and the new additions. The disavow file builder generates a fresh file each time; maintain your running list of disavow entries and paste the full current list each time you generate a new submission.

Maintaining a Disavow File Over Time

A disavow file is a living document that should be updated as new toxic links are discovered and as older disavowed links are confirmed removed. The most practical approach is to maintain a master list of all domains and URLs ever disavowed, stored in a spreadsheet with the date each entry was added and any removal request outcome. When a new submission is needed, paste the full master list into the disavow file builder to generate a complete file, rather than trying to update the raw text file manually.

Keeping dated copies of every disavow file submitted, alongside a record of the submission date and the triggering reason, creates an audit trail that is valuable if a manual action reconsideration request is needed. Google's reviewers for reconsideration requests look for evidence of a systematic approach to link quality management, not just a one-time file submission. A dated history of submissions shows that link quality is actively monitored rather than reactively addressed.

When a site is sold or transferred to a new owner, handing over the disavow file history along with the Search Console access is important. The new owner needs to know which links have been disavowed, when, and why, to continue maintaining the file correctly and to avoid inadvertently removing old disavow entries in a new submission. Include the disavow file history in any SEO audit document prepared as part of a site acquisition due diligence process.