The disavow file, and Google's own step zero

What the disavow tool is, and the three things it is not

The disavow links tool is a Google Search Console feature that lets a verified site owner upload a plain-text file listing URLs and domains, asking Google to ignore the links from them when assessing that owner's site. It is the only product surface — the only screen or form Google actually ships — that responds to inbound links at all. Search Console itself is Google's free reporting console for site owners, and it is where every check on this page happens.

Three things the tool is not, and all three are misunderstood daily:

• It does not remove anything. The links stay on the web, stay in Google's index, and stay in Search Console's Links report. Google's documentation says so outright: "Disavowed links will continue to be shown in the Links report."
• It is not a report. Nobody at Google reads your file as a complaint about the sites in it. It is an instruction handed to a system, and the system does not answer.
• It is not visible to anyone but you. The file is attached to your property, is not published, and is not shown to the sites you list. Google publishes no statement to that effect, so treat it as an inference from the tool's design rather than a quotation — but there is no mechanism by which anyone else could see it. Practically: listing a competitor's link does not notify them, does not harm them, and does nothing at all to their site. It changes only what Google counts toward yours.

One spelling note that saves a support ticket a week: it is disavow, not disallow. Disallow is a robots.txt directive and has nothing to do with this file.

Google's own warnings, quoted, and Step 0

The disavow documentation — Google's Search Console help article on disavowing backlinks, a living document and the only authoritative description of this file format anywhere — is unusually blunt, and almost nobody who files a disavow file has read it. Verbatim:

Google works very hard to make sure that actions on third-party sites do not negatively affect a website.

This is an advanced feature and should only be used with caution. If used incorrectly, this feature can potentially harm your site's performance in Google Search results.

In most cases, Google can assess which links to trust without additional guidance, so most sites will not need to use this tool.

You should disavow backlinks only if: 1. You have a considerable number of spammy, artificial, or low-quality links pointing to your site, AND 2. The links have caused a manual action, or likely will cause a manual action, on your site.

Read the criteria as Google wrote them. They are joined by AND, not or. A site with no manual action — a penalty applied by a human reviewer at Google, shown to the owner in Search Console — and no realistic prospect of one fails the second test on its face, and is outside the stated use of the tool no matter how ugly the backlink export looks.

Then there is the structure of the page itself, which is the most quotable fact on this subject. Google's instructions do not begin with create your file. The first heading in the procedure is Step 0: Decide if this is necessary, and the sentence about most sites not needing the tool sits inside it. Google numbered the decision not to act as step zero of acting.

John Mueller, a Search Advocate at Google and one of the few named staff who answer public questions about ranking systems, put the same point in one sentence. Mueller, 12 May 2020: "negative SEO is not a reason we have this tool — and I honestly can't recall a situation where a site ever needed to do a disavow for that." Mueller again, 31 January 2023, on the trade built around the file: "That's all made up & irrelevant. These agencies (both those creating, and those disavowing) are just making stuff up, and cashing in from those who don't know better."

When the file is genuinely warranted

Two situations, and both are about links the site is responsible for rather than links pointed at it:

1. An outstanding "Unnatural links to your site" manual action, where a reconsideration request has to show that manipulative links have been dealt with and some of them cannot be removed. The disavow file is the documentary evidence for the second half of that sentence. The review process itself is covered in the guide to manual actions and reconsideration requests, and the file alone never lifts an action.
2. A site that bought links in its own past — its history, not an attack — where the purchases are visible in the profile and the seller will not take them down. Being framed as a link buyer by someone else is a different problem, dealt with on the paid link framing page.

Against a third-party attack the file is defensive theater for the overwhelming majority of sites, and that is not a contrarian position — it is Google's documented one. The mechanism that made hostile links dangerous was retired on 23 September 2016, when Google announced that Penguin had become part of the core algorithm and wrote that "Penguin now devalues spam by adjusting ranking based on spam signals, rather than affecting ranking of the whole site." The December 2022 link spam update extended the same treatment through SpamBrain, Google's machine-learning spam detection system. The tool works as documented; the belief that an ordinary site with a clean Manual actions report needs one is what has been neutralized. If that is your situation, the guide to removing negative SEO links covers what to do instead, which is mostly nothing.

The file format, exactly as Google documents it

Everything in this section is from Google's help article. Third-party format guides drift from the spec because there is no second authoritative source to check them against.

Encoding and file type

• Plain text. Encoding must be UTF-8 or 7-bit ASCII. A file exported from a word processor or a spreadsheet is neither.
• The filename must end in .txt. A .csv or .doc extension fails validation.

Line syntax

• One entry per line. Google's wording: "Specify one URL or domain to disavow per line."
• To disavow a single URL, write the full URL on its own line.
• To disavow an entire domain or subdomain, prefix it with domain: — Google's example is domain:example.com.
• There are no subpaths and no wildcards. Google states: "You cannot disavow an entire subpath, such as example.com/en/." A path entry silently disavows that one exact URL and nothing beneath it. This is the most common format error in circulation, and it fails quietly.
• A line beginning with # is treated as a comment and ignored. Use them. A disavow file with no dated comments is unreadable to whoever inherits it, including you in two years.

Hard limits

• Maximum 2,048 characters per URL.
• Maximum 100,000 lines, counting blank lines and comment lines toward the total.
• Maximum file size 2 MB.

A minimal, correctly formed file

Four lines, in order, each on its own line in the text file:

• # Attack cluster first seen 2026-03-14, exported from the Search Console links report
• # Reviewed against the manual action issued 2026-03-28
• domain:example-spam-network-one.invalid
• https://real-publisher.invalid/a-page-that-cannot-be-removed.html

The reserved .invalid suffix is used above deliberately, because template domains get copied into live files by people working at two in the morning.

Where the tool lives, and how upload actually behaves

• It is not in the Search Console navigation. The tool is reached directly at search.google.com/search-console/disavow-links, or through the link in the help article. Its absence from the menu is deliberate: it is not a routine maintenance screen.
• Upload replaces, wholesale. There is exactly one list per property, and Google's wording is that "uploading a new list for a property will replace any existing list for that property." There is no merge and no append. Upload a five-line file over a nine-thousand-line file and the nine thousand entries are gone.
• There is no download. Google documents no way to retrieve a list you previously uploaded. Losing your local copy means losing the file's contents permanently. Keep the master in version control on your own machine and treat the tool as a submission endpoint, not as storage.
• A bad file changes nothing. Google's documented behavior on a validation failure is that "if errors exist, the old list remains unchanged." The failure mode to watch is not noticing.
• To withdraw everything, select the property and use Cancel Disavowals, which removes the list for that property.
• Property scope is narrow, and the tool does not support Domain properties. Google says the list "applies only to the specific property to which you uploaded it, plus any child properties." An owner who has only ever verified a Domain property has to add a URL-prefix property before they can use the tool at all, and a site served on several hostnames may need more than one file. This surprises people who have used Search Console for a decade.
• There is no status indicator. No active flag, no count, no history, no confirmation in any report. The only record of what is disavowed is your own copy.

On timeline — the interval between an action and its observable effect, which on this subject is nearly always longer than people expect — Google publishes exactly one figure for this tool: "It can take a few weeks for Google to incorporate your list into the index." That describes incorporation, not any ranking consequence, and Google publishes nothing at all about the second. Nothing visible happens on the day you upload.

The failure mode that does real damage: bulk domain-level disavowal

This deserves its own section because the tools that generate disavow files default to exactly this behavior. A backlink auditor exports every referring domain, scores each one with a proprietary toxicity number that no search engine publishes or endorses, and offers to write a file with domain: in front of everything above a threshold. The output is a list of hundreds or thousands of domains, disavowed at domain level, on a vendor heuristic.

Why that is worse than doing nothing:

• The domain: prefix is blunt by design. One bad link on a large legitimate domain — a hacked page on a university site, a spam comment under a major publisher's article, a scraper subdirectory on a hosting provider — takes the whole domain with it, including the genuine link you already have from it and any you might earn later.
• It is reversible in the file, not in effect. You can re-upload without the entry, but Google publishes no timeline for a disavowed domain's links being counted again, and no confirmation that they are. The only published figure is the few weeks for incorporation.
• It discards your own history. Old links from marginal directories are frequently the oldest links a small site has. They may be worth little. They are not worth negative.
• It fails Google's stated criteria on its face. The criteria require a manual action or the realistic prospect of one. A threshold score is not a manual action, and no vendor's score is calibrated against Google's behavior because Google's behavior is not published.
• It compounds. Because upload replaces, an auditor who regenerates the file monthly from a fresh export produces a list that grows and is never read line by line again.

The discipline that avoids all of it fits in one sentence: disavow only links you can name a reason for, one line at a time, with a dated comment saying why. If the file is too long to review by hand, it is too long to be correct. Use domain: for a domain that exists to host spam and has no other content — the throwaway hosts described on the link farm inclusion and private blog network pages qualify. Use a URL line for one bad page on a real site.

The inherited file nobody remembers uploading

Because there is no download and no status indicator, a disavow file can sit on a property for years without anyone knowing it exists. On any site that has changed agency, developer or owner, this is worth ruling out before anything else is attributed to an algorithm.

1. Ask, in writing, whether a disavow file was ever uploaded, and for the copy. Ask the previous agency, the previous consultant and the previous owner separately; the file outlives the relationship that produced it.
2. Do not use the Links report to check. Disavowed links still appear there. The report is evidence of nothing either way, and reading it as confirmation is a common wasted afternoon.
3. Reconstruct the intended list from your own evidence — dated exports and named reasons — rather than from a fresh tool export, which will simply reproduce the original mistake.
4. Upload the corrected file, remembering that it replaces everything.
5. Or withdraw it entirely with Cancel Disavowals. That is the right move when an inherited file cannot be justified line by line and no manual action is outstanding.
6. Then wait. A few weeks is the only published figure, and it describes incorporation rather than any change you can measure.

An unexplained flat profile on a site with a long history and a previous agency is a reason to suspect one exists.

What the file has nothing to do with

The disavow file is a private instruction to a search engine. It creates no legal relationship with the sites listed, is not a publication about them, and cannot defame anyone because nobody else reads it. It also provides no remedy against anyone: it is not a complaint, not a report, and not a step toward one.

It does nothing whatever for problems that are not link problems. A hacked site, injected content, scraped pages, a malware flag, a review attack or a Business Profile hijack are all untouched by it, and filing one for any of those is an afternoon spent on the wrong instrument. Bing operates its own separate disavow feature with its own rules; a Google file has no effect there and vice versa, and I have not verified Bing's current documentation, so take that as the limit of what I will say about it.

Two claims about the file circulate widely and are unsourced folklore: that a disavow file wastes crawl budget, and that filing one signals distrust to Google. Google has published nothing of the kind. So has speculation that the tool will be retired — its removal from the main navigation and years of staff commentary discouraging its use have produced a persistent rumor, but Google has announced no such plan, and a rumor is not a fact you should plan a property around.

Frequently asked questions