Google Disavow File Guide

A disavow file tells Google which links to discount for your site. It is a last-resort cleanup tool for clear manipulative links you cannot remove. It is not a routine maintenance chore.

If you are still exploring whether links are a problem, start with a toxic backlink checker triage and the workflow in How to Check for Toxic Backlinks. Only continue here when a narrow, reviewed list is truly necessary.

When a disavow file might be appropriate

Consider disavow only after evidence, not after a scary vendor score.

• You have a manual action for unnatural links, or a clear history of paid schemes you created.
• Removal outreach failed or is impossible for a focused set of manipulative hosts.
• Sample pages show scheme-like patterns such as networks, farms, or injected spam.
• You understand that Google systems often devalue spammy links without owner uploads. See Do Toxic Backlinks Hurt Rankings?.

If the profile is merely messy, pause. Many toxic backlink flags are triage noise. A high spam score is not an automatic upload trigger.

Exact file format requirements

Google documents the format on the disavow links help page. Follow it precisely.

• Encoding: UTF-8 text file.
• One entry per line: Either a full URL or a domain rule.
• Domain syntax: Use domain:example.com to cover an entire domain.
• Comments: Lines starting with # are comments.
• Size limits: File must be under 2MB and under 100,000 lines.

Example structure

A minimal reviewed file might look conceptually like this:

• # Reviewed 2026-09-02: clear spam network samples only
• domain:spammy-example.com
• https://other-example.com/bad-page

Prefer domain: when the entire host is manipulative. Use a specific URL when only one path is the problem and the rest of the site is legitimate.

How to build the list safely

1. 01

   Finish triage first

   Run a referring-domain review and open samples. Do not export every red flag into the disavow file.

2. 02

   Attempt removal where realistic

   Contact webmasters for links you can still take down. Templates help: link removal outreach templates.

3. 03

   Keep only confirmed problem hosts

   Each remaining line should have a written reason. If you cannot explain why a domain belongs, delete it from the draft.

4. 04

   Save as UTF-8 .txt

   Confirm encoding, one entry per line, and that you are under 2MB and 100,000 lines.

5. 05

   Upload in Search Console

   Use the disavow links tool for the correct property, then document the upload date.

How to upload and what to expect

Upload through Google's disavow links tool while signed into the Search Console property that matches the site. Google's help page covers property choice and the warning screens you must acknowledge.

1. Verify you are on the right Search Console property.
2. Open the disavow links tool from Google's documentation entry point.
3. Read the warnings carefully. They exist because misuse can hurt.
4. Upload the UTF-8 text file.
5. Record what you uploaded and why.

Google notes that it can take some time for a disavow file to be processed, often on the order of several weeks, as systems recrawl and reassess links. Do not expect overnight ranking recovery. If rankings improve later, many factors may be involved.

For broader spam context, pair this guide with Google's spam policies, including link spam.

URL versus domain: practical choices

Choose domain: when

• The host exists mainly to sell or manufacture links.
• Multiple paths on the same host point spammy links at you.
• The site is a clear link farm or abandoned spam property.

Choose a single URL when

• A reputable domain has one compromised or scraped page.
• You want to avoid discarding other links from a generally useful host.
• Your evidence is page-specific, not site-wide.

Overusing domain: on mixed-quality hosts is a common way disavow files become harmful. Stay narrow.

Maintenance after upload

• Revisit the file if you remove links successfully and no longer need those entries.
• Replace the file when your reviewed list changes. Uploading a new file replaces the previous disavow list for that property.
• Do not keep appending unverified junk forever.
• Continue normal SEO work: content, technical health, and earned links.

If you are unsure whether a junk-link spike is an attack, read negative SEO attack or noise before expanding the file. For definitions and signal lists, see What Are Toxic Backlinks?.

Checklist before you click upload

Comment lines that future you will thank you for

Comments starting with # do not change how Google reads the rules. They change how your team audits the file months later. Use them.

• Date the review session at the top of the file.
• Name the person or team that approved the list.
• Group comments by pattern, such as expired-domain redirects or leftover paid placements.
• Note which entries came from removal failures versus hosts with no contact path.

Avoid putting secrets in comments. Keep client-sensitive details in your internal ticket, and keep the disavow file limited to technical rationale.

Common formatting mistakes

If your editor rewrites encoding to something other than UTF-8, re-save explicitly. Encoding issues are dull, and they still break uploads.

Property matching and site moves

Upload against the Search Console property that matches the site version you intend to protect. Domain properties and URL-prefix properties can confuse teams during migrations.

• After a domain move, confirm which property should hold the active disavow list.
• Do not assume an old file still applies after a property change without verification.
• Keep an offline copy of the approved list in version control or a ticket attachment.

Google's disavow help article remains the source of truth for tool behavior. This guide restates the documented format limits and the caution that most sites should not use the tool.

What success does not look like

Success is not a dramatic overnight ranking jump after upload. Success is a careful reduction of clear manipulative signals you could not remove, with no collateral damage to legitimate references.

If rankings rise later, many factors may contribute: content updates, demand changes, competitive shifts, or normal volatility. Do not market disavow as a guaranteed recovery lever. That claim would contradict both Google's guidance and this site's editorial stance.

1. Measure whether the risky cluster stopped growing.
2. Confirm you did not disavow brand-valuable hosts by mistake.
3. Keep investing in links and pages you would proudly show a customer.

For first-pass discovery before any file exists, stay with the how to check for toxic backlinks workflow and a toxic backlink checker scan.

Replacing a file without losing the plot

When you upload a new disavow file, it replaces the previous list for that property. That behavior is useful and dangerous. Useful because you can shrink an overgrown list. Dangerous because an incomplete replacement can drop entries you still needed.

• Keep a master reviewed list offline before every upload.
• Diff the new draft against the previous approved version.
• Remove entries only when the link is gone or the original rationale no longer applies.
• Add entries only when new evidence clears the same high bar.

Treat the disavow list like production config. Casual edits create outages of judgment. If two people can upload, require a second reviewer for any expansion beyond a small threshold you define internally.

Bottom line: the Google disavow file is a precise, rarely needed request to ignore specific links. Follow the UTF-8 format and documented limits, keep the list small, and never treat disavow as a default response to toxic labels.