Restore / Manual Actions / Link Disavow Unnatural-Links Remediation Link Disavow Service. We file the disavow only after the outreach round Google's review team needs to see.
The disavow file is UTF-8 .txt with the domain: prefix and one URL per line, capped at 100,000 lines and 2MB. We compile it only after documented removal outreach because Google rejects reconsideration requests where the disavow ran without the outreach evidence behind it.
Four facts about the disavow that govern the file shape.
The disavow is the specification-grade artifact the reconsideration request needs. Manual-action cases reach this service through <a class="prose-link" href="/manual-action-removal/">the manual-action removal service</a> and <a class="prose-link" href="/penguin-recovery/">Penguin demotion recovery</a>. The <a class="prose-link" href="/">SEO Penalty Removal</a> path that diagnoses as unnatural-links manual action routes here.
- 01
The disavow file format is specified.
<span class="cite">UTF-8 / 7-bit ASCII .txt</span>, maximum <span class="cite">100,000 lines</span>, <span class="cite">2MB</span>, <span class="cite">2,048 characters per URL</span>. One URL per line. The <span class="cite">domain:</span> prefix disavows the whole referring domain. Comments via <span class="cite">#</span>. Format errors cause silent failure. The file has to validate before submission.
- 02
Outreach evidence is the load-bearing input.
Google explicitly states blindly adding all backlinks to a disavow file without removal outreach will lead to rejection of the reconsideration request. We run the outreach round first, document it per-contact-address, and ship the disavow with the evidence package attached.
- 03
Post-Penguin-4.0 algorithmic disavow is largely redundant.
Since <span class="cite">Penguin 4.0 / 2016-09-23</span>, the algorithm zero-weights manipulative links at the URL level in real time. The disavow file applies to manual actions for <span class="cite">unnatural-links-to-site</span> and edge cases. Submitting one reflexively for any traffic loss is the common mistake.
- 04
Per-URL evidence is what the review team reads.
The reconsideration request that ships with the disavow names the exact issue, the specific steps taken, and the outcome documentation. We catalog every affected referring domain, the outreach attempted to each, and the response received. Sparse evidence is the second-most-common rejection cause after partial remediation.
Four phases. The outreach round runs before the file gets compiled.
-
Read the link profile against the manual-action notification.
We pull the Search Console Manual Actions report and confirm the category is <span class="cite">unnatural-links-to-site</span> or <span class="cite">unnatural-links-from-site</span>. We export the link profile from Ahrefs and Majestic, classify by acquisition pattern, and identify the referring domains that drove the manipulative signal.
- Manual Actions report screenshot (category confirmation)
- Ahrefs + Majestic link export (full inbound profile)
- Acquisition-pattern classification per referring domain
- Contact-address discovery per referring domain
-
Document the removal request per referring domain.
We send the removal-request email to every identified contact address, log the date sent, and capture the response. The response rate runs 5 to 15 percent, with 3 to 8 percent landing in actual removal. The review team reads the documented attempt rather than the success rate.
- Per-domain removal request email sent
- Date-stamped log of every outreach attempt
- Per-contact-address response capture
- Documented refusal or no-response per remaining link
-
Author the disavow file against the Google specification.
The file is UTF-8 .txt, one URL per line, `domain:` prefix where the whole referring domain has to go, comments via `#`. We validate against the maximum 100,000 lines and 2MB ceiling. Format errors cause silent failure; the file has to parse cleanly or it does no work.
- UTF-8 .txt encoding verified
- domain: prefix on root-level disavows
- Comment lines documenting outreach attempt per block
- File size and line-count validation against spec
-
Ship the disavow with the reconsideration request.
The disavow uploads through the Search Console Disavow tool. The reconsideration request authored to the three-element structure (exact issue, specific steps, outcome documentation) carries the outreach evidence package as attachments. We verify full Googlebot accessibility before submission.
- Disavow file upload through Search Console
- Reconsideration request authored (issue + steps + outcome)
- Outreach evidence package attached
- Full Googlebot accessibility verified
Disavow done against the specification. Restore versus reflexive disavow submission.
- Pre-disavow link-removal outreach
- Documented per referring domain. Date-stamped contact log. Per-address response captured.
- Disavow file format compliance
- UTF-8 .txt, domain: prefix, ≤100,000 lines, ≤2MB, ≤2,048 chars per URL.
- Reconsideration request structure
- exact-issue + steps + outcome per Google's review-team specification. Per-URL evidence attached.
- Post-Penguin-4.0 redundancy distinction
- Algorithmic Penguin demotion routes to Penguin demotion recovery. Disavow reserved for manual actions and edge cases.
- Googlebot accessibility verification
- Affected pages confirmed accessible. No noindex, no paywall during review.
- Pre-disavow link-removal outreach
- Skipped. The file gets uploaded and the reconsideration request gets rejected on missing outreach evidence.
- Disavow file format compliance
- Format errors common. Silent failures on encoding, line length, or line count.
- Reconsideration request structure
- Vague rebuilding language. Partial remediation cited. Common rejection cause.
- Post-Penguin-4.0 redundancy distinction
- Disavow shipped reflexively for any traffic loss. Wrong remediation for algorithmic demotion.
- Googlebot accessibility verification
- Accessibility unverified. Review stalled when crawler cannot verify the fix.
Outreach response rates run 5 to 15 percent on contact attempts, with 3 to 8 percent landing in actual removal.
What operators ask before the disavow ships.
- 01.
Do I still need a disavow file after Penguin 4.0?
For manual actions flagged as unnatural-links-to-site or unnatural-links-from-site, yes. For algorithmic suspicion post-2016-09-23, almost never. Penguin 4.0 zero-weights manipulative links at the URL level in real time. The file applies to the explicit manual-action surface and to edge cases where automated discounting appears incomplete.
- 02.
What is the disavow file specification?
UTF-8 / 7-bit ASCII .txt, one URL per line, maximum 100,000 lines, maximum 2MB, maximum 2,048 characters per URL. The domain: prefix disavows the whole referring domain. Comments via #. The file has to validate cleanly; format errors fail silently.
- 03.
Why is outreach evidence required when the disavow does the work?
Google's policy is explicit: blindly adding all backlinks to a disavow file without removal outreach will lead to reconsideration-request rejection. The review team is reading the documented attempt as evidence of good-faith remediation. The disavow is the catch-all for unremovable links; the outreach is what shows the attempt to remove them was real.
- 04.
What response rate does removal outreach actually get?
5 to 15 percent response rate on the email round. 3 to 8 percent successful removal. Google's review team does not require a high success rate. They require the documented attempt. The evidence package shows when outreach went out, to which contact addresses, and what came back.
- 05.
What if my disavow file was already submitted without outreach?
That is the most common rejection cause on Penguin-class manual actions. Google explicitly states blindly adding backlinks to a disavow file without outreach will lead to rejection. The remediation: run the outreach now, document it per referring domain, then resubmit the reconsideration request with the evidence package attached. Operators arriving with a rejected refile-only-disavow attempt are the standard intake shape for the seo penalty removal company workflow on the unnatural-links category.
- 06.
Where does the disavow service fit relative to Manual Action Removal?
The manual-action removal service is the parent workflow. The disavow service is the specific component that handles the file authoring plus the outreach round. The reconsideration request authoring runs on the same evidence package via authoring the reconsideration request.
If the Search Console Manual Actions report flags unnatural links, book the diagnostic.
We audit the link profile against the named-update calendar, run the documented removal outreach round, compile the disavow against the Google specification, and author the reconsideration request to the three-element structure. The evidence package ships with the file.