Restore / Research / Disavow Tool
§ 23 · Disavow Tool Reference

Google Disavow tool. Format specification plus the post-Penguin-4.0 operational role.

Required for manual actions for unnatural links plus the documented removal outreach. Largely redundant under Penguin 4.0 real-time discounting for algorithmic suspicion. The diagnostic comes first; the disavow follows the routing decision.

DISAVOW TOOL, HOW IT WORKS

Four facts about the Disavow tool that govern the routing.

The disavow operates downstream of the diagnostic. Algorithmic post-Penguin-4.0 cases need the acquisition-source identification rather than the disavow. Manual-action cases need the disavow plus the outreach plus the reconsideration request. Cases arriving at <a class="prose-link" href="/">penalty removal for SEO</a> with a link-profile shape route here.

  1. 01

    The Disavow tool was launched October 16, 2012.

    Google released the tool five months after the <span class="cite">Penguin 1.0 / 2012-04-24</span> launch, in response to operators needing a way to disclaim manipulative inbound links they could not get removed at source. The original use case was pre-Penguin-4.0 algorithmic suspicion plus manual action remediation. The tool itself has not changed in shape since launch.

  2. 02

    File format is strict and silent on rejection.

    The file ships as <span class="cite">UTF-8 or 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 must validate. Google does not return a parse-error notification.

  3. 03

    Penguin 4.0 reshaped the disavow's operational role.

    Since <span class="cite">Penguin 4.0 / 2016-09-23</span>, the algorithm zero-weights manipulative links at the URL level in real time rather than demoting the site. Submitting a disavow file for suspected algorithmic post-2016 cases is largely redundant; the links are already discounted. The tool retains operational necessity for explicit manual actions for unnatural links and edge cases where automated discounting appears incomplete.

  4. 04

    Outreach evidence is what the reconsideration request needs.

    Google explicitly states blindly adding all backlinks to a disavow file without removal outreach will lead to reconsideration request rejection. The remediation requires documented, good-faith link-removal outreach first (response rates of <span class="cite">5 to 15 percent</span>, successful removal <span class="cite">3 to 8 percent</span>), then the disavow file as the catch-all for links the outreach could not remove, then the reconsideration request with the outreach evidence package.

DISAVOW WORKFLOW

Four phases. Audit profile in. Reconsideration-ready evidence package out.

  1. PHASE 01 AUDIT

    Categorize the inbound-link profile.

    We pull the full link profile from Ahrefs and Majestic, deduplicate at the domain level, and categorize each referring domain against the unnatural-link policy. The audit output is a labeled list: keep / remove-via-outreach / disavow.

    • Pull full referring-domain set
    • Deduplicate at the registrable domain level
    • Categorize keep / remove / disavow per domain
    • Cross-check anchor-text distribution
    • Identify high-velocity acquisition windows
  2. PHASE 02 OUTREACH

    Document the removal effort.

    For the remove-via-outreach set, the request goes out via documented contact addresses with date-stamped records of every send and reply. Response rates run five to fifteen percent. Successful removal lands in the three-to-eight percent range. Google does not require a high success rate; it requires the documented attempt.

    • Identify contact addresses per domain
    • Send removal requests with date-stamped records
    • Track responses and non-responses
    • Archive the evidence package for reconsideration
  3. PHASE 03 COMPILE

    Author the disavow file to specification.

    The file ships as UTF-8 plain text, one URL per line, with the domain: prefix where the whole referring domain has to go. We validate line count, byte size, and per-URL character count before upload. Format errors cause silent failure on Google's side.

    • Use UTF-8 / 7-bit ASCII text encoding
    • Apply domain: prefix per registrable domain
    • Verify under 100,000 lines and 2MB
    • Verify each URL under 2,048 characters
    • Add comments via # for operator audit trail
  4. PHASE 04 SUBMIT

    Upload and route to reconsideration.

    The disavow file is uploaded to Search Console at the property level. For manual actions for unnatural links, the reconsideration request is authored to the three-element structure with the outreach evidence package attached. Algorithmic post-Penguin-4.0 cases skip the reconsideration step; the upload itself signals the disclaim.

    • Upload to Search Console disavow tool
    • Verify file accepted (no parse errors logged)
    • Author reconsideration (manual-action cases only)
    • Attach outreach evidence package
2 MB
FILE SIZE LIMIT
UTF-8 / 7-bit ASCII .txt
100K
LINE MAXIMUM
One URL per line
2,048
CHAR PER URL
Per-URL character ceiling
3-8%
OUTREACH REMOVAL
Documented success rate
DIAGNOSTIC SPEC-SHEET

Disavow role before September 23, 2016 versus after.

Disavow before Penguin 4.0
Pre-2016-09-23
Algorithmic role
Operationally required for suspected algorithmic Penguin demotion. Recovery waited for the next data refresh.
Manual action role
Required for unnatural-links manual actions plus the documented removal outreach.
Recovery window
Months. Waited for the next Penguin data refresh (Penguin 2.0 / 2013-05-22, Penguin 3.0 / 2014-10-05).
URL-level versus sitewide
Sitewide or directory-level demotion applied at threshold breach.
Operator decision
Audit profile, run outreach, compile disavow, submit, wait for the next refresh.
Disavow before Penguin 4.0
Pre-2016-09-23
Algorithmic role
Operationally required for suspected algorithmic Penguin demotion. Recovery waited for the next data refresh.
Manual action role
Required for unnatural-links manual actions plus the documented removal outreach.
Recovery window
Months. Waited for the next Penguin data refresh (Penguin 2.0 / 2013-05-22, Penguin 3.0 / 2014-10-05).
URL-level versus sitewide
Sitewide or directory-level demotion applied at threshold breach.
Operator decision
Audit profile, run outreach, compile disavow, submit, wait for the next refresh.

Specification grounded against Google Search Central documentation plus the dated Penguin rollout history.

DISAVOW QUESTIONS

What operators ask before compiling the file.

  1. 01.

    Should I submit a disavow file if my traffic dropped on a Penguin signal?

    Since Penguin 4.0 / 2016-09-23, the algorithm zero-weights manipulative links at the URL level in real time. For suspected algorithmic post-2016 cases, the disavow is largely redundant; the links are already discounted. The exception is an explicit manual action for unnatural links in the Search Console Manual Actions report, where the disavow is part of the reconsideration evidence package.

  2. 02.

    What is the exact disavow file format?

    UTF-8 or 7-bit ASCII .txt. Maximum 100,000 lines, 2MB, 2,048 characters per URL. One URL per line. The domain: prefix disavows the whole referring domain (use it where every URL on the domain is manipulative). Comments via #. Format errors cause silent failure on Google's side; the file must validate.

  3. 03.

    How long does Google take to process a disavow upload?

    Upload acceptance is immediate (the file appears in Search Console). The actual ranking effect lands at recrawl across the disavowed URLs, which runs over weeks to months depending on crawl frequency. For manual-action cases the disavow does not directly resolve the action; the reconsideration request does, with the disavow file and outreach evidence attached.

  4. 04.

    Why does Google reject reconsideration requests submitted with a disavow but no outreach?

    Google explicitly states blindly adding all backlinks to a disavow file without attempting removal outreach will lead to rejection. The reconsideration team requires the documented attempt: when outreach went out, to which contact addresses, what came back. The evidence package shows the work rather than the result. Outreach without disavow is also incomplete; both elements ship together. The seo penalty removal company diagnostic runs the audit before either element is compiled, so the evidence package matches the categorized profile.

  5. 05.

    Can I disavow a whole domain or only specific URLs?

    Both. Single URLs go on their own line. Whole-domain disavow uses the domain: prefix (domain:example.com). The whole-domain form is the operational default for clearly manipulative referring domains where every URL is part of the same scheme. Single-URL form is reserved for cases where the domain is mixed and only specific pages should disclaim.

If your Search Console flagged unnatural links to your site or your link profile carries acquisition patterns you need read, book the diagnostic.

We audit the inbound-link profile, run the documented removal outreach, compile the disavow file to specification, and author the reconsideration request to the three-element structure with the outreach evidence package attached.

BOOK A DIAGNOSTIC

Four fields. We respond inside one business day with a few questions to make sure we can help, before either of us spends time on a call.

We use what you submit to qualify, then respond by email. No newsletter signup.