Check this page with an assistantOpens a chat asking it to summarise this article and name the evidence behind each claim.

Claude opens with the prompt on your clipboard: Anthropic does not support prefilled prompts on the web, and we would rather copy it than ship a button that drops it.

Classify the Situation Before Taking Action

Observed situationBest next stepDisavow?
Random scraper, spam, or invented referrer linksRecord if useful; investigate only if a pattern has provenanceUsually no
Competitor or rank-tracker decline with no manual actionDiagnose pages, queries, demand, and technical changesNot by default
Historical paid network or scaled placement campaignStop it, inventory placements, and seek removal or qualificationPotentially
Manual action for unnatural links to the siteRemediate broadly, document work, and request reconsiderationOften for remnants
Paid or user-generated outbound links on your siteAdd the correct rel value and govern future publishingNot applicable

A traffic drop after a broad ranking change is not evidence that backlinks caused it. Use the core update recovery field note to segment the loss before changing link signals. Also rule out migrations, indexing directives, redirects, seasonality, and SERP changes.

Fix the Source of the Risk Before Editing a File

A disavow file does not make an ongoing scheme safe. End purchases, automated campaigns, required followed links, and ungoverned agency work first. Build a working inventory with the linking URL and domain, target page, anchor, placement type, date, owner, compensation, outreach status, and evidence.

  1. Export known links and combine them with contracts and campaign records.
  2. Cluster by campaign, vendor, domain network, target, and anchor pattern.
  3. Sample the live pages; do not classify solely from a metric.
  4. Ask site owners to remove the link or qualify compensated placements.
  5. Save outreach dates, responses, removed examples, and unresolved domains.
  6. Review the unresolved set against the manual-action threshold.

Google’s manual-action guidance expects a good-faith cleanup. Blindly disavowing every backlink without trying to remove links you arranged may not be enough for reconsideration. Your record should explain what created the problem and why it will not recur.

Use the Disavow Format Conservatively

The file is plain text encoded as UTF-8 or 7-bit ASCII, with one URL or domain instruction per line. Prefix a whole-domain instruction with domain:. Lines beginning with # are comments for your own documentation. Google currently limits the file to 100,000 lines and 2 MB.

# Legacy paid placement campaign; removal requested 2026-07-02
https://spam.example/old-paid-post.html
domain:network.example

Prefer the narrowest defensible scope. A URL instruction is useful for an isolated placement; a domain instruction is appropriate when the whole domain or network pattern is artificial. Do not disavow a reputable publication because one page looks irrelevant.

Uploading replaces the current file. Download the existing version, reconcile it with the new inventory, and secure a second review. Changes can take weeks to be reflected as Google recrawls and reprocesses affected pages, and recovery is not guaranteed.

Handle a Manual Action as an Evidence-Based Remediation

Read the exact Manual Actions report and inspect its examples. The examples illustrate the issue but may not enumerate every affected link. Expand from them to the originating campaigns, templates, and vendors rather than fixing only the listed rows.

A reconsideration request should be concise and accountable: explain the cause, how the risky links were found, which were removed or qualified, which could not be removed and were disavowed, and what governance changed. Attach or reference a clear cleanup record. Wait for the decision instead of repeatedly replacing the file without new evidence.

Monitor the Cleanup Without Rebuilding a Toxicity Queue

Keep the remediation inventory as an incident record, not a monthly reason to classify every new domain. Monitor the Manual Actions report, the status of removal requests, vendor compliance, and whether compensated placements are qualified. Search Console’s Links report can show broad patterns, but its sampled rows should not be treated as a complete before-and-after count.

Track search performance at the affected page and query level while acknowledging that link reprocessing takes time and other ranking systems continue to change. Do not promise an exact recovery date or attribute every movement to the file. The durable success metric is that the manipulative practice stopped, unresolved risk was handled proportionately, and future contracts prevent recurrence.

Questions About Link Spam and Disavow Files

Should I disavow every spammy-looking backlink?

No. Google says most sites do not need the disavow tool. Use it only when there is a considerable number of spammy, artificial, or low-quality links and those links have caused, or are likely to cause, a manual action. A strange domain or declining metric alone does not meet that threshold.

Can disavowing links recover a site after a core update?

Do not assume the two events are related. First check Search Console for a manual action and diagnose the affected pages, queries, competitors, and site changes. A broad disavow file can remove useful signals and will not repair content, technical, or product problems.

Do paid links always violate Google’s policies?

Paid placements are allowed, but links in advertisements, sponsorships, affiliate arrangements, and other compensated placements should be qualified. Google prefers rel=sponsored, while nofollow remains acceptable.

Does uploading a new disavow file add to the old one?

No. A new upload replaces the property’s existing file. Download and review the current file first, preserve still-valid entries, and have a second reviewer verify the complete replacement before submission.

Primary Sources Reviewed

SearchHandled Editorial TeamPublished Apr 28, 2026 · Last reviewed Apr 28, 2026. Every factual claim is checked against the linked primary sources; corrections can be submitted through our contact page.