Toxic links and disavow

A toxicity review scores backlink rows you have already fetched against a fixed rubric, then lets you build a Google-format disavow file. RankMeFast never submits that file.

<!-- docs-truth: metric=toxicity_reviews; unit=one-review-up-to-1000-stored-rows; cache-hits=count; refund=provider-failure-zero-retained; cadence=on-demand; estimates=rubric-observation -->

How rows are banded

The rubric toxicity-rubric-v1 reads the provider spam score on each stored backlink row and places it in a clean, watch, or toxic band. Broken-link and nofollow signals adjust the band.

The rubric is deterministic: the same stored rows and the same spam scores always produce the same bands, and every band is shown with the evidence it was derived from.

What the review costs

One review snapshots at most 1,000 rows you have already fetched and pays for at most 100 fresh domain spam scores. A site with no stored backlink rows must load its backlink list first.

An optional AI rationale explains a flagged row by citing that stored row, or abstains. If the provider step fails, nothing is retained and the unit is returned.

Building a disavow file

The builder lets you include or exclude each row and choose domain or URL scope, then exports a plain Google-format .txt file. Excluded rows never reach the export.

RankMeFast exports the file for your own review and submission to Google. It has no connection to your Search Console disavow tool and never uploads on your behalf.

Honest limits

A band is a rubric observation about a link. It is never a prediction of a Google penalty, a manual action, or a ranking change.

AI may annotate a row the rubric already flagged, but it can never add a domain the rubric did not flag. Every domain in the export traces back to a stored row.

For units and plan limits, see Pricing.

Before acting, compare this guide with the stored evidence and status shown in RankMeFast.

Back to the docs index