What is disavow?

Disavowing a link does not delete it from the web. The link still sits on the source site, still shows up in the Search Console "Links" report and stays visible to every third-party tool. The only thing that changes is the signal the search engine receives: Google treats those URLs or domains as if they did not point at your site for ranking purposes.

Three things are regularly confused with it. It is not the nofollow attribute, which applies to links leaving your own pages. It is not a reconsideration request, which is the procedure for asking that a manual action be lifted. And it is not a general cleanup button: Google states that in most cases it can judge for itself which links to trust, so most sites will not need to use the tool.

The official documentation narrows its use to two conditions that must hold at the same time. First, a considerable number of spammy, artificial or low-quality links must point at the site. Second, those links must have caused a manual action, or be very likely to cause one. Outside that scenario, the help page itself warns that this is an advanced feature and that using it incorrectly can harm the site's performance in Google Search.

The procedure has three parts: prepare the file, upload it to the right property and wait for reprocessing.

The file is plain text with one URL or one domain per line. To disavow an entire domain including its subdomains, prefix it with domain:. Lines starting with a hash are comments and Google ignores them, which makes them useful for recording the date and the reason behind each block. Subfolders cannot be disavowed: a line such as example.com/en/ does not cover that branch of the site.

# 2026-08-18 paid link trail
http://spam-one.example/page.html
http://spam-one.example/other.html

# format: domain:<domain>
domain:link-farm.example

The technical requirements are strict: UTF-8 or 7-bit ASCII encoding, a file name ending in .txt, a maximum of 2048 characters per URL, a maximum of 100,000 lines including comments and blank lines, and a maximum file size of 2 MB.

You upload it from the tool's own page after selecting the property. Each property holds a single list and the new one replaces the previous one completely, so the file you upload today must also contain everything you want to keep disavowed. Only verified owners may upload it. The tool does not support Domain properties, only URL-prefix properties, which is why a site running http and https needs one list in each. Google takes several weeks to incorporate the list, because it depends on recrawling and reprocessing the affected pages. To reverse it there is a button that cancels every disavowal on the property, with the same waiting period.

The decision that rests on this tool is not "do I have bad links?" but "do I have a manual action for links, or concrete reasons to expect one?". That question is answered by the manual actions report in Search Console, not by the toxicity score of a commercial tool. If the report is clean and traffic has dropped, the cause usually lies elsewhere, and uploading a disavow list will not fix it.

The cost of getting it wrong is lopsided. Google explained that its systems neutralize the impact of artificial links at scale, so disavowing links the search engine already discarded produces nothing measurable. If instead a domain that was sending you genuine links ends up on the list, that signal is lost, and it stays lost for the weeks a corrected file needs before it is processed again. That imbalance explains why the tool lives at its own address, outside the regular Search Console reports.

For an agency or an in-house team there is also documentary value. When removing the links at the source has failed, the disavow file records the attempt to repair a contaminated link profile, and that history is submitted with the reconsideration request.

• Check the manual actions report in Search Console first. With no manual action and no well-founded suspicion that one is coming, do not upload any list.
• Try to get the links removed at the source before disavowing them, and keep the dates, the emails you sent and the replies. That record is exactly what gets attached to a reconsideration request later.
• Open every candidate domain by hand before including it. Check whether the link exists, the context it sits in, and whether that site could send you visitors or customers.
• Start with individual URLs and reserve the domain: prefix for cases where the whole site is artificial, such as link farms or blog networks built for ranking.
• Comment every block of the file with the date and the reason. A comment costs one line and stops anyone a year from now wondering why a domain is in there.
• Keep the current list versioned in the project repository. Since each upload replaces the previous one, losing the file means losing the entire disavow state.

• Uploading a "toxicity" tool export without filtering it. Those scores are third-party models, not Google signals, and they drag in healthy domains that were giving you real links.
• Writing paths or subfolders. A line such as example.com/blog/ disavows nothing, because the file only accepts full URLs or domains with the domain: prefix.
• Uploading the list to the wrong property, or only to the http version of the site instead of the https one. Every URL-prefix property carries its own list.
• Adding only what is new. Because the file replaces the previous one, uploading a short list reactivates every link that does not appear in it.
• Reaching for disavow as a reaction to a traffic drop with no manual action involved. It is the fastest way to switch off good links and still be left without an explanation for the drop.