Why is your Disavow file constantly rejected by Google?

What makes a Disavow file valid in Google's eyes?

Google mandates a strictly textual format for Disavow files. Nothing fancy: .txt extension only, preferably UTF-8 or ASCII encoding. Google's parser can only read three types of lines: comments (preceded by a #), complete domains (domain:example.com format), and absolute URLs.

Any attempt to submit a formatted document (.doc, .docx, .xls, .xlsx) results in immediate rejection. The system doesn't even try to convert or interpret it: it rejects the file right upon upload. The result? No links are disavowed, and if this file accompanies a reconsideration request for a manual penalty, that request fails.

Why doesn’t Google accept other formats?

The technical reason is simple: Google processes millions of Disavow files daily, submitted by webmasters worldwide. Allowing multiple formats would require parsers capable of handling Word (with its different versions, macros, encodings), Excel (with its multiple sheets, formulas, merged cells), PDF, CSV with variable separators.

Plain text eliminates any ambiguity. A .txt file contains only characters, without hidden metadata or complex structure. The parser can read it line by line, identify patterns (domain:, http://, #), and apply rules without the risk of misinterpretation. It is a choice of durability and scalability.

What are the concrete consequences of an incorrect format?

A rejected file does not always generate an explicit error message in Search Console. Sometimes, the interface simply displays “0 disavowed domains or URLs,” which can be misleading. The webmaster believes they have submitted their file, whereas in reality nothing has been processed.

If this submission occurs as part of a reconsideration request after a manual penalty (Penguin or link spam), Google considers that the cleanup efforts are incomplete. The request is denied, and the site remains penalized. In some cases, this can delay the lifting of sanctions by several weeks or even months, while the webmaster identifies the error and resubmits correctly.

• Accepted format: plain text file (.txt), UTF-8 or ASCII encoding
• Valid lines: comments (#), domains (domain:), absolute URLs (http:// or https://)
• Silent rejection: an incorrect file may not display an explicit error, creating a false impression of validation
• Impact on reconsideration: a poorly formatted Disavow blocks manual penalty lifting
• No automatic conversion: Google never attempts to extract content from a Word/Excel file

Is this text format requirement consistent with observed practices in the field?

Absolutely. Fifteen years of practical experience confirm that Google makes no exceptions regarding this matter. Cases of .doc or .xlsx files being “accepted” do not exist. The parser is unyielding: plain text or nothing.

What still surprises some practitioners is the absence of a clear error message in all cases. Search Console should ideally display “Invalid file format” or “Unsupported extension.” Instead, the interface sometimes just shows a zero counter, which masks the real issue. We've seen clients convinced they disavowed 200 domains, while their Excel file was never read.

What nuances should be added to this rule?

The main nuance concerns the file encoding. Google recommends UTF-8, but also accepts ASCII. However, exotic encodings (Windows-1252, ISO-8859-1 with poorly interpreted accented characters) can cause silent parsing errors. A poorly encoded line is simply ignored, without notification.

Another point is the maximum file size. Google imposes a limit of 100,000 lines and 2 MB. Beyond that, the file is truncated or rejected. If you disavow tens of thousands of domains (extreme cases of massive negative SEO), you must prioritize the most toxic domains and ensure the file remains below this threshold. [To be confirmed]: Google does not publish statistics on rejection rates related to size, but empirical tests show that 2 MB is the strict limit.

When does this rule cause practical issues?

The real problem arises when non-technical teams manage the Disavow. A project manager receives a list of toxic backlinks in an Excel spreadsheet shared by the agency or analytical tool. They open it, add a few domains, and… upload it directly in .xlsx to Search Console. Guaranteed rejection.

Another tricky case: files created in “rich” text editors (WordPad, TextEdit in RTF mode). The extension may sometimes be .txt, but the content includes invisible formatting tags. Google rejects those too. The only safe solution remains Notepad (Windows), TextEdit in plain text mode (Mac), or an editor like Sublime Text, VS Code, Atom.

How can you create a compliant Disavow file for sure?

Open a plain text editor (Notepad, TextEdit in text mode, Sublime Text). Never Word, never Excel. Add your comments starting each line with #, then list your domains or URLs. Use the domain: format to disavow an entire site, complete URL (http:// or https://) to disavow a specific page.

Save the file with the .txt extension. Check the encoding: UTF-8 without BOM (Byte Order Mark) is the safest. On Windows, Notepad has offered “UTF-8” by default since recent versions. On Mac, TextEdit allows you to select “Unicode (UTF-8)” in the saving options. Once saved, open the file with another editor to confirm that no strange characters appear.

What mistakes should you absolutely avoid when submitting?

The first mistake: uploading a .csv or .xls file thinking “it’s almost text”. No. Google’s parser only reads .txt. The second mistake: using relative URLs (/page.html instead of https://example.com/page.html). Google ignores them. The third mistake: forgetting the domain: prefix before a domain name. Without this prefix, Google tries to interpret the line as a URL, and if it doesn't start with http, it's rejected.

A frequent mistake is also mixing protocols. If you disavow http://example.com/page and the toxic link points to https://example.com/page, the disavowal doesn’t work. When in doubt, use domain:example.com to cover all variations (http, https, www, subdomains).

How can you check that the file has been properly accounted for?

After uploading in Search Console (Disavow Links section), check the Disavow dashboard. Google displays the number of disavowed domains and URLs. If these numbers match your file, that’s a good sign. If they are zero while you have listed 50 domains, it means the file has been rejected or misparsed.

Google does not process the file instantly. Expect a few days to a few weeks for disavowed links to be ignored in the PageRank calculation and link profile. Monitor link reports in Search Console: disavowed domains should gradually disappear from the graph, or at least be marked as “ignored.”

• Open a plain text editor (Notepad, TextEdit, Sublime Text)
• Use only the format domain:example.com or https://example.com/page.html
• Save as .txt with UTF-8 encoding without BOM
• Check that the file does not exceed 100,000 lines or 2 MB
• Verify in Search Console that the number of disavowed domains/URLs corresponds
• Wait 2 to 4 weeks to observe the impact in link reports