Build a Google Disavow File — Step-by-Step, Safely Submit

Build a Google Disavow File — Step‑by‑Step walks you through a conservative, safety‑first process to identify toxic backlinks, prepare a properly formatted disavow.txt, and submit it in Google Search Console (GSC) so you can start penalty recovery with minimal risk.

Why (and when) you should use the Google Disavow Tool

The Google Disavow Tool is the official way to tell Google you do not want certain inbound links to be considered when assessing your site. Use it only when you have confirmed links are unnatural (part of a link scheme, spammy networks, or purchased links) and you cannot reasonably get them removed via outreach.

Two short callouts:

• Manual action vs algorithmic drop: If you have a manual action for link spam, removals + disavow are part of recovery; if you have an algorithmic ranking drop, disavow may help but is not always required. Follow steps to diagnose manual action vs algo drop.
• Conservative first: Disavow only links you cannot remove and that show clear toxic signals — over‑disavowing risks collateral damage to legitimate links.

Google’s official guidance is explicit: disavow “only if” you believe you have a substantial number of spammy, artificial, or low‑quality links pointing to your site and you can’t get them removed. See Google’s Disavow Links help for syntax and intent: Google Search Central — Disavow links.

Transition: Before you build a file, confirm prerequisites so you don’t accidentally disavow safe links.

Quick checklist — prerequisites before you build a disavow file

1. Export backlinks from primary sources — GSC + at least one third‑party tool (Ahrefs, SEMrush, Majestic) to get a broad set. Keep raw CSVs and timestamps as evidence.
2. Attempt removal outreach — log each removal outreach attempt with date and response; disavow only after outreach fails or is impossible.
3. Confirm property ownership in GSC — you must use the same property (domain or prefix) you want Google to apply the disavow to.
4. Deduplicate and normalize URLs — keep referring page, referring domain, anchor text, and first seen date columns for review.
5. Create a disavow audit trail — maintain a versioned spreadsheet with timestamps, who reviewed, decisions, and the exact disavow.txt used per upload (record keeping / disavow audit trail).
6. Back up current rankings and traffic — export a baseline from your analytics (30/90-day windows) so you can measure recovery.
7. Plan for a conservative scope — set clear decision thresholds (see the compact audit below) to avoid over-disavowing.

Transition: With prerequisites complete, use a compact, risk‑based framework to decide which links to include.

How to decide which links to disavow (a compact risk-based audit)

This is a focused triage you can run quickly — not a full forensic audit. You’ll look for clear toxic signals and apply conservative decision thresholds so you disavow only what’s necessary.

Define key signals (first use definitions): a backlink is a single link from a referring page; a referring domain is the host supplying those backlinks. “Toxic backlinks” are links that show spammy intent or violate Google’s guidelines.

1. Flag obvious spam (high risk)
   • Signals: automated mass directories, scraped content pages, porn/illegal niches linking with unnatural anchor text, clear PBN patterns (identical templates, no traffic).
   • Decision: remove if possible; if no response or uncontactable, disavow at the domain level (domain:example.com).
   • Mini example: A network of 120 links from cheap directory pages with “buy weight loss pills” anchor text — disavow.
2. Suspicious but ambiguous (medium risk)
   • Signals: low‑quality sites with mixed content, low Domain Authority/DR, odd link velocity, or sporadic spammy anchors among otherwise neutral links.
   • Decision threshold: attempt removal outreach. If no reply in 2–4 weeks, disavow at URL level for individual pages you can’t remove; consider domain disavow only if >5 spammy pages per domain.
   • Mini example: One referring domain with 3 pages linking using keyword‑rich anchors and low traffic — outreach first; if ignored, URL‑level disavow.
3. Low-risk or editorial links (low risk)
   • Signals: high‑quality domains, contextual editorial links, social links, forum profiles with one or two links, brand anchors, or links from known publications.
   • Decision: do not disavow. Keep records proving assessment.
4. Paid links and link marketplaces
   • Signals: direct payment admission, link marketplaces, sponsored content without rel attributes, and obvious PBN/paid network fingerprints.
   • Decision: When present, follow a stricter path — export, flag, attempt removal, and disavow remaining paid links. If your exports indicate paid links, run a deeper inspection using our guide to audit paid links and reduce risk.
   • Context: If you find links that came from marketplaces, review 13 backlink red flags in marketplaces to decide if removal or disavowal is appropriate.
   • If links may be from PBNs or marketplaces, see PBNs vs marketplaces: link risk compared to refine your decision.
5. Anchor-text and intent analysis
   • Signals: heavy exact‑match keyword anchors for commercial pages, hidden text links, or repeated unnatural anchors across unrelated domains.
   • Decision: treat repeated spammy anchors as higher risk; disavow referring domains generating the pattern if outreach fails.
6. Collateral risk and false positives
   • Trade-off: Disavowing a whole domain is effectively telling Google to ignore every link from that host — this can remove legitimate links too. Prefer URL-level entries when in doubt to minimize collateral damage.
7. Triage scoring (quick method)
   • Assign 0–3 points per signal (spammy anchor +1, low DA +1, no traffic +1, many links from same domain +1). Disavow if score ≥3 after outreach fails.
   • Keep notes in a tracking sheet for each decision (see record keeping below).

Note: For full audits and paid link forensics, see our deeper posts. This compact framework is designed for fast decisions to build a safe disavow file.

Transition: Once you’ve made decisions, export and prepare your master list for the disavow file.

Exporting and preparing your backlink list (GSC + third‑party tools)

Gather complete exports and normalize the data so you can build accurate disavow entries. Use a mix of sources — official GSC plus third‑party exports from Ahrefs, SEMrush, or Majestic to capture different crawl profiles.

1. Export from Google Search Console:
   • In GSC, go to Links > External links > More sample links > Export external links to download a CSV. Include referring page and linking text if available.
   • Save a copy of the exact CSV (timestamped) for the audit trail.
   • Reference: GSC links report.
2. Export from third‑party tools:
   • Download backlink CSVs from Ahrefs, SEMrush, Majestic. These often show additional URLs Google may not list.
   • According to a 2024 industry report from Ahrefs, combining sources improves coverage of referring domains vs using GSC alone; compare exports for overlap and unique domains. See: Ahrefs — How to use disavow.
   • If you find paid links, run the deeper workflow in audit paid links and reduce risk.
3. Combine and deduplicate:
   1. Combine CSVs into a master spreadsheet. Keep columns: source tool, referring URL, referring domain, anchor text, first seen, and notes.
   2. Normalize URLs (lowercase host, strip trailing slashes). Use a formula or script to extract referring domain for domain-level grouping.
   3. Deduplicate by referring URL and then by referring domain to get two lists (URL-level and domain-level).
4. Filter to actionable items:
   • Remove obvious social links, comments with single links, and links from legitimate editorial outlets (unless clearly toxic).
   • Flag domains with many toxic pages — these are candidates for domain-level disavow.
5. Keep provenance columns:
   • For each row, keep a “source export” column to show where the link appeared (GSC, Ahrefs, etc.) and a “review status” (Outreach Sent / No Response / Removed / Disavow Pending).
   • This supports record keeping / disavow audit trail and will be needed if you have to file a Reconsideration Request later.

Tip: You can quickly pull a toxicity shortlist using GSC alone — follow our guide to find toxic links free with GSC for an immediate export.

Transition: With your master list ready, build the disavow.txt exactly to Google’s syntax rules.

Build the disavow file — exact syntax, rules, and examples

Google is strict about the format. Build a plain text disavow.txt file encoded in UTF‑8 and follow these rules from Google Search Central: Disavow links — Google Search Central.

Rules summary:

• File must be a plain .txt file (no .doc, .rtf). Use UTF‑8 encoding to avoid character issues (set in your editor).
• One entry per line. For domain-level disavows, prefix with domain: (e.g., domain:badexample.com).
• For URL-level disavows, enter the full URL (e.g., http://badexample.com/cheap-links.html).
• Comments begin with # and are ignored by Google; use them for your audit trail (include date/version info).
• Maximum file size is 2MB (plain text). Keep it concise; group by domain when appropriate.

Annotated sample disavow.txt (showing several lines):

# Disavow list for example.com
# Version: 2026-06-05
# Source: GSC export 2026-05-28; outreach attempted 2026-05-30
domain:spammydirectory.com
http://badexample.com/paid-link-page.html
# Below domain had multiple spam pages; disavow entire domain after failed outreach
domain:buy-links-network.net

Explanation of entries:

• # — Comments. Use them to timestamp and note the reason for inclusion (this aids record keeping).
• domain:spammydirectory.com — Domain-level disavow removes all links from that host.
• http://badexample.com/paid-link-page.html — URL-level disavow for a specific page.

File encoding and common pitfalls:

• Always save as UTF‑8; non‑UTF‑8 files may be rejected. In Notepad, choose “UTF‑8” when saving; in macOS TextEdit, export as plain text UTF‑8.
• Do not include other characters (BOM headers) that can corrupt the file.
• Check for stray whitespace and Windows line endings — keep it simple.

Transition: When you’ve verified syntax, decide domain vs URL strategy carefully.

Advanced disavow strategies — domain vs URL, when to disavow whole domains

Strategy	When to use	Pros	Cons
URL-level disavow	Individual spammy pages on otherwise decent domains	Minimizes collateral damage; targeted	Requires many entries if site has many spam pages
Domain-level disavow	Hosts with systemic spam, clear link network behavior, or multiple toxic pages	Covers all current and future links from that host	May remove legitimate editorial links; higher false positive risk
Subdomain-level consideration	When spam is limited to a subdomain (e.g., blog.spam.com)	More precise than domain disavow if subdomain is the problem	Requires careful host parsing

Guidance bullets:

• Prefer URL-level disavows when the domain has mixed signals (some good pages, some spam).
• Use domain-level only when the domain is overwhelmingly spammy or part of a clear network.
• For guest posts and links you control, consider alternative de‑risking such as adding rel=”sponsored” instead of disavowing; see de-risk old guest posts with rel=sponsored.
• Document the reason for each domain disavow in your audit trail to support a future Reconsideration Request if needed.

Transition: Now you’re ready to submit the file within Google Search Console.

Step-by-step: submit your disavow file in Google Search Console

Before you upload, ensure you’re using the correct GSC property (domain property recommended where possible). The following numbered steps map directly to the required HowTo actions.

1. Open the Disavow Links page for your site: visit the Disavow Tool (requires sign-in to the Google account that owns the GSC property). Use the official page: Google Disavow links tool.
2. Select the correct property: Confirm the property shown in the top-left matches the site you’re working on (domain vs URL-prefix). If it’s wrong, switch properties in GSC first.
3. Click “Upload disavow file”: choose your prepared plain text UTF‑8 file (disavow.txt).
4. Confirm upload: Google will warn that disavowing is serious. Proceed only if you’ve followed the audit and outreach steps. You’ll see a confirmation message after a successful upload.
5. Record the upload: save a copy of the exact file you uploaded in your tracking spreadsheet, and note the date/time and account used (record keeping / disavow audit trail).
6. Re-uploading or editing: to change the list, upload a new file — Google uses the latest file exactly as submitted. Keep versioned backups.

Transition: After upload, monitoring is essential. Expect deferred processing and plan your recovery timeline.

After submission — monitoring, expected timelines, and recovery playbook

What to expect after you upload a disavow file:

• Processing: Google processes disavow files when it recrawls the linking pages and reindexes links; there is no fixed SLA. Empirical reports vary — SEMrush and Ahrefs note most changes appear within a few weeks to a few months depending on site size and crawl frequency.
• Disavow does not remove links from the web — it tells Google not to consider them for ranking purposes.
• If you have a manual action for link spam, submit a Reconsideration Request only after documenting removals and disavowals (see our reconsideration request template for link spam).

Typical monitoring checklist (30/60/90 day playbook):

1. 30 days — Verify upload success in GSC and check that no new inbound spikes appear. Continue outreach for remaining links. Update the spreadsheet log (record keeping).
2. 60 days — Look for initial ranking improvements for priority pages; compare to baseline analytics. Use third‑party tools to monitor referring domain changes.
3. 90 days — Expect clearer ranking signals and recovery trends if disavow and removals addressed the main link issues. If not, re-evaluate your list and escalation options (additional removals, broader disavow, or manual action support).

Monitoring tools and signals:

• GSC Links report for new incoming links and to confirm problem links are still present (remember disavow won’t delete them).
• Analytics (traffic and conversions), rank trackers, and third‑party backlink crawlers (Ahrefs/SEMrush) to compare changes.
• Maintain the spreadsheet and day/time stamped notes — this is critical for evidence if a manual action persists and you must file a reconsideration request.

Transition: If something goes wrong, here are common mistakes and how to troubleshoot or roll back.

Common mistakes, troubleshooting, and “what to do if things go wrong”

1. Wrong syntax / bad encoding
   • Troubleshoot: If Google rejects the file or upload fails, re-save as plain UTF‑8 text and remove unusual characters. Use a basic editor (Notepad, VS Code, TextEdit plain text).
2. Over‑disavowing (accidental domain disavow)
   • Troubleshoot: Review your audit trail and remove the domain entry from a new file upload immediately. Upload the corrected file; Google will adopt the new file. Note: recovery may take time as Google reprocesses links.
3. Missing important links
   • Troubleshoot: Keep a master spreadsheet and re-run exports to find missing referring domains. Re-upload an updated disavow.txt with added lines as needed.
4. No traffic recovery
   • Troubleshoot: Verify if the issue is a manual action. Check GSC Manual Actions report. If a manual action exists, follow the removal + disavow workflow and then submit a reconsideration request using our reconsideration request template for link spam.
5. Accidental file corruption or size issues
   • Troubleshoot: Keep files under 2MB plain text. If your list is large, group by domain and prioritize highest-risk hosts first.
6. Rollback guidance
   • To undo a mistake, upload a corrected disavow.txt without the problematic entries. Preserve older versions in your audit trail. Expect reprocessing timelines as pages are recrawled.

Transition: To help you act quickly, we’ve prepared downloadable templates and a sample audit entry you can reuse.

Templates, downloads, and record-keeping (sample files)

Download and adapt these files; they are formatted for immediate use.

• Sample disavow.txt — Plain text template with comment headers and example domain/URL lines. Save as UTF‑8 and edit before upload.
• Removal outreach/email template — A short, polite template for webmasters with fields for URL, reason, and deadline.
• Disavow tracking spreadsheet — Columns: source, referring URL, referring domain, outreach status, date, reviewer, disavow decision. Example row included in sheet.

Example record entry (from the tracking spreadsheet):

RefDomain: spammydirectory.com | RefURL: http://spammydirectory.com/listing123 | Source: Ahrefs 2026-05-20 | Outreach: 2026-05-22 (no response) | Decision: domain disavow | FileVer: 2026-06-05

Transition: Finish with a concise checklist and next steps that tie this action into your broader recovery plan.

Final checklist and next steps (links to further reading)

Before you close this task, run this final checklist and consider broader recovery steps.

1. Confirm the uploaded file is the correct version and saved in your audit trail.
2. Continue removal outreach for any remaining domains; log outcomes.
3. Monitor GSC and analytics for 30/60/90 days and update your recovery notes.
4. If a manual action exists after removals and disavow, prepare a Reconsideration Request (use our reconsideration request template for link spam).
5. For a full framework that ties disavow actions into an end-to-end recovery plan, see The Complete Beginner’s Guide to Link Risk & Penalty Recovery.

Next actions (prioritized):

1. Upload final UTF‑8 disavow.txt and archive a copy in your records.
2. Continue outreach for top 20 domains by impact and re-evaluate after 30 days.
3. Track performance changes and be prepared to adjust the disavow list conservatively.

Transition: A short anonymized case example shows typical results from a conservative workflow.

Anonymized case example (realistic walkthrough)

Labelled hypothetical (anonymized): Site A — mid‑size e-commerce site experiencing a 42% drop in non‑brand traffic over 3 months. After diagnosis, team found ~2,400 suspect backlinks from networks and marketplaces.

Actions taken:

• Exported GSC + Ahrefs lists, deduplicated, prioritized highest‑risk domains (120 domains).
• Sent removal outreach to top 80 domains (tracked in the spreadsheet); 12 removals completed, 68 no response.
• Built a conservative disavow.txt: 68 domain: entries + 18 URL entries (for remaining high‑risk pages). Uploaded on 2026-06-05.

Results (anonymized realistic numbers):

• 30 days: minor ranking stabilization; branded traffic steady.
• 60 days: organic non‑brand traffic regained 28% of prior losses; priority product pages moved back to Page 1 for three mid‑commercial queries.
• 90 days: total non‑brand traffic recovered ~80% compared to pre‑drop baseline.

Note: This case is anonymized and simplified for illustration; actual results vary based on site, link age, and Google’s recrawl schedule.

Transition: Frequently asked questions follow for quick reference.

Frequently Asked Questions

What is a disavow file and when should I use it?

A disavow file is a plain-text list telling Google which backlinks to ignore. Use it when you have many unnatural or spammy backlinks you cannot remove via outreach, or when instructed as part of manual action recovery; it does not remove links from the web, it only asks Google to ignore them.

Should I remove backlinks or disavow them — what’s the difference?

Removal outreach asks webmasters to delete links from their sites; disavow tells Google to ignore links you can’t get removed. Always attempt removals first; disavow only remaining problematic links to avoid discarding valuable editorial links.

How do I create a disavow file from my Google Search Console export?

Export GSC links (CSV), deduplicate and flag toxic URLs/domains in a spreadsheet, then save a plain-text UTF‑8 file with one entry per line (URL or domain:example.com). Include # comments for versioning and date, then upload in the Disavow Tool.

How do I submit a disavow file in Google Search Console?

Go to the Google Disavow links tool while signed into the GSC account owning the property, select the correct property, upload your UTF‑8 .txt file, confirm the upload, and save a copy of the uploaded file in your records.

How long does it take for Google to process a disavow and see ranking changes?

Processing depends on when Google re-crawls linking pages; changes often appear between weeks and a few months. According to industry tool reports, early signals can show in 30–90 days, but timelines vary by site and crawl frequency.

My disavow upload failed — what common mistakes should I check first?

Check file format (plain .txt), encoding (UTF‑8), syntax (one line per entry, domain: prefix for domains), file size (<2MB), and remove any BOM or special characters. Re-save in a simple editor and re-upload.

Will disavowing links hurt my site’s rankings if I make a mistake?

Yes — incorrectly disavowing legitimate domains can remove beneficial links and hurt rankings. Keep a versioned audit trail and re-upload a corrected file to restore links; recovery requires Google to reprocess the links, which can take time.

Do I need to file a reconsideration request after disavowing links?

Only if you have a manual action reported in GSC. After removals and disavow, prepare documentation and submit a reconsideration request; use a template and include evidence of outreach and the disavow file.