This page turns a list of domains and URLs into a disavow file. It normalises each line, rejects anything malformed, removes repeats and writes the plain-text file that Search Console accepts, with optional header comments explaining what the entries mean.
It is a formatter with a review step, not a link audit. It cannot tell you which links are unnatural, and it should not be used to disavow everything a tool has marked as low quality. Most sites never need a disavow file at all.
When a disavow file is appropriate
Google's guidance is narrow. You should disavow links only if you have a considerable number of spammy, artificial or low-quality links pointing at your site, and those links have caused a manual action or are likely to cause one. In most cases Google says it can assess which links to trust without additional help, so most sites will not need the tool.
The first step is removal. Contact the site, ask for the link to be taken down, and keep a record. Disavow is for links you cannot remove. Google also warns that the feature is advanced and can harm a site if used incorrectly, which is why the output here asks for a second review before upload.
What Google's format requires
The rules below come from Google's disavow documentation and are enforced by Search Console when you upload, not by this page.
| Rule | Requirement |
|---|---|
| Entries | One URL or domain per line |
| Domain entries | Prefix with domain:, as in domain:example.com |
| Subpaths | Not supported; you cannot disavow example.com/en/ as a path |
| Encoding | UTF-8 or 7-bit ASCII, file name ending in .txt |
| Length | Maximum 2,048 characters per URL |
| Size | Maximum 100,000 lines and 2 MB, including blank and comment lines |
| Comments | Lines starting with # are ignored |
| Replacing | A new upload replaces the existing list for that property |
| Timing | Changes can take a few weeks to appear as Google recrawls |
| Property type | The tool does not support Domain properties |
The Domain property point is the one that stops people late. If the site you are working on is verified as a Domain property, Search Console's disavow page does not apply to it, and a perfectly valid file has nowhere to go. Check the property type before you build the list.
What the generator does to each line
Blank lines and comments are dropped. Any line containing a space is rejected. A line starting with domain: is validated as a domain and written back in the same form. A line starting with http:// or https:// is checked as a URL, has any fragment removed, and can have a leading www. stripped if that option is on.
A bare domain such as spammy.example becomes a domain: entry. A bare domain with a path, such as spammy.example/page, is rejected, because it is neither a domain nor a full URL. Add the scheme if you mean one page.
Duplicates are removed after normalisation, so two lines that differ only by a fragment collapse into one. The optional all-domains mode takes every accepted URL and reduces it to its host, which is useful when a whole site is the problem and risky when one page is.
A worked example
Ten lines were pasted with the header switched on. The result was five entries, one duplicate and three rejected lines. The file looked like this:
| Line in disavow.txt | Kind |
|---|---|
domain:spammy-directory.example | Domain |
https://spammy-directory.example/tools/seo | URL |
http://duplicate.example/page | URL |
https://duplicate.example/page | URL |
domain:bad-network.example | Domain |
The duplicate came from a second copy of the spammy-directory URL with #comments on the end. The fragment was removed, which left the same address, so the second line was counted and dropped. The two duplicate.example lines stayed separate because one is http and the other https; the generator does not decide which scheme you meant.
Three lines were rejected and listed with a reason: low-quality.example/guest-post because a bare domain with a path is not a valid entry, has space.example because of the space, and not_a_domain because of the underscore.
low-quality.example/guest-post is usually a matter of adding the scheme. Do that before upload, not after.Domain or URL?
A URL entry covers that address. A domain entry covers every URL on the host and its subdomains, including pages you have never seen. Prefer a URL when one page is the problem, because a domain entry can disavow good links too.
Google does not support disavowing a subpath. If ten pages under /offers/ are the problem, list them individually as URLs or disavow the host, and accept the trade-off.
The all-domains mode makes this decision for you. In the second test, three lines became two domain entries: domain:one.example and domain:two.example. The third line, three.example/path, was rejected because it had no scheme, so the mode never saw it. That shrinks the file even though the two remaining entries look complete, which is another reason to read the rejected list.
Review before upload
Open the file and compare every entry with the link report it came from. Remove anything you cannot tie to a specific unnatural link. A domain entry can cover pages you have never reviewed, and there is no undo for a bad upload, only a replacement file.
Search Console validates the file on upload. If there are errors, the old list stays in place and you can fix the new one and try again. If the upload succeeds, give it weeks rather than days.
Keep a copy of each uploaded version with the date and the property it went to. If you later replace it, you will want to know what changed. The link prospect builder is for finding new links; this page is for the last resort when old ones cannot be removed.