Build and submit a valid disavow file to Google for a site with a manual action or suspected unnatural-links problem
domain: support.google.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Exhaust manual link-removal outreach first — Google's guidance treats disavow as a last resort, not a first step, for links you can't get taken down
Format the file as UTF-8 or 7-bit ASCII plain text with one URL or domain per line
To disavow an entire domain rather than a single URL, prefix the line with domain: (e.g. domain:example.com); note that a subpath like example.com/section/ cannot be disavowed, only full domains or individual URLs
Add optional # comment lines to document why each entry was included, for your own audit trail
Keep the file under the 100,000-line and 2MB size limits, and upload it via the Disavow Links tool scoped to the correct property
Expect a multi-week delay before Google recrawls and incorporates the disavowal into its link evaluation, and re-check Search Console for manual action status after that window
Known gotchas
Uploading a new disavow file replaces the previous one entirely rather than merging with it, so always download and re-include prior entries before adding new ones
Disavowing broadly or unnecessarily can suppress legitimate link equity; Google explicitly warns most sites never need this tool
Processing time is measured in weeks tied to Google's normal recrawl cycle, so disavow is not a fix for time-sensitive manual action deadlines
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?