Move selected records from Backlink Checker or Referring Domains into a project-only review list. Choose domain or URL scope, save a note, review or remove entries, and export a dated Google-formatted .txt file for manual upload.
Keep investigated sources in one project list before preparing a Google file. Screpy records your decisions; it does not identify harmful links or recommend disavow from a score alone.
disavow.txtReviewdomain:example.org
https://example.net/linksThe entry refers to the website linking to you, not the destination on your own site. Choose the scope that the evidence supports before adding the selected sources.
disavow.txtReviewdomain:example.org
https://example.net/linksSave the reasoning when you add entries so another reviewer can understand the decision. A note can describe the known campaign, removal attempt or evidence behind the selected scope.
disavow.txtReviewdomain:example.org
https://example.net/linksNotes
Use the project list to inspect what the next download will contain. Compare entry types and reasons before treating the file as ready for the property owner.
disavow.txtReviewdomain:example.org
https://example.net/linksRemove an entry when a reviewed source should no longer appear in the local list. The confirmation gives you a final chance to check the exact value before deletion.
Review
example.comUse the main Export button for the complete project list in a UTF-8 .txt file. The dashboard filename contains the project domain and export date, helping you identify the file you actually reviewed.
Connect an authorized workflow to the same project list for review, additions, deletion and export. Access remains project-scoped and subject to the project's backlink eligibility.
/projectsJSON{
"data": [
{ "domain": "example.com" }
]
}Ask an AI assistant to review saved disavow entries, notes and whole-list domain/URL counts for an authorized, backlink-eligible project. MCP additions or deletions require explicit confirmation; text exports are paginated resources, and Google upload remains manual.
Confirm the need, investigate the links, choose the narrowest justified scope, review the complete replacement list, and keep the final Google action manual.
Check Google Search Console for a link-related manual action or credible evidence of a large artificial-link problem. Do not start from a third-party score or an unfamiliar domain alone.
Review source pages, anchors, targets, link attributes, dates, and patterns in Backlink Checker or Referring Domains. Try to remove links you intentionally built or control when possible.
Select the whole source domain only when the evidence applies broadly. Otherwise select the exact source URL and add a note that explains the decision.
Check every local entry and reconcile it with any list already stored by Google. A new Google upload replaces the property’s previous list instead of appending to it.
Download the dated .txt file, inspect its domain and URL lines, and let a verified property owner complete the external upload. Keep the submitted version because Google may need weeks to recrawl and reprocess links.
The workflow is most useful when the link history and remediation goal are known—not as a recurring response to every unfamiliar backlink or third-party score.
Organize links that remain after a documented removal effort when Google has reported unnatural inbound links and the evidence supports a reconsideration workflow.
Record domain or URL decisions for paid, exchanged, automated, or otherwise controlled links from an earlier campaign when those links cannot be removed from the web.
Keep the selected value, scope, note, and disavowed date visible when responsibility moves between an internal team, consultant, or agency before the next export.
Compare the Screpy list with the property’s current Google file before replacing anything, especially after a site acquisition, platform migration, or SEO ownership change.
Screpy helps prepare and review the list. It does not decide that a link is harmful, remove links from the web, change an uploaded Google list, or make processing immediate.
Google describes disavow as an advanced feature for a considerable artificial-link problem tied to a manual action or likely manual action, not routine backlink maintenance.
Spam and authority scores can help prioritize investigation, but they do not replace source-page evidence, ownership history, link context, or Google’s manual-action information.
The list and export are preparation tools. Publishers control source-page removal, and a verified property owner controls the final Google upload or cancellation.
A replacement upload must include every entry that should remain. Google says processing can take several weeks while it recrawls and reprocesses the affected pages.
Inspect exact placements first, group sources when the domain pattern matters, and enter Disavow Management only after the evidence supports an owned-project action.
Review source pages, anchors, targets, attributes, dates, states, and metrics before selecting domain or URL records.
Group available links by source website, compare domain-level patterns, and open the records behind a source.
Store reviewed project domains or URLs with notes, remove entries, and download the current Google-formatted text file.
Screpy documentation
Use the Screpy guide to investigate links first, choose domain or URL scope, review the project list, and prepare a manual Google upload only when justified.
Learn the concepts behind this workflow and apply them with practical SEO guidance.
Explore 20 link building strategies, prospect checks, outreach examples, and a worked campaign. Measure useful placements and avoid risky shortcuts.
Read articleLearn how parasite SEO works, compare publishing arrangements, and assess Google's current policy, ownership risks, and measurable business results.
Read articleCompare website crawls with MCP using saved snapshots. Review real metric changes, match page details, and verify fixes without overstating SEO results.
Read articleLearn where ChatGPT text watermarking applies, how textGrain works, what detectors can establish, and what editors should record before publishing.
Read articleUnderstand when Google recommends this advanced action, how Screpy prepares the list, and what remains under the property owner’s control.
Select backlinks or referring domains while analyzing a project you control, choose domain or URL scope where available, and add an optional note. Competitor-domain research cannot populate the project’s disavow list.
A disavow file asks Google not to take selected inbound links into account when evaluating a website. Google treats it as an advanced action for specific link-related problems, not a routine cleanup step.
No. Screpy prepares a download; the verified property owner reviews and uploads it manually. Google's Disavow Links tool requires an appropriate URL-prefix property and does not support Domain properties.
No. A third-party score is a review signal, not proof that Google considers a link harmful. Check the live source, relevance, placement, anchor, target, ownership history, broader pattern, and any manual action before making a decision.
Download and review the existing Google list before uploading a replacement. Google says a new upload replaces the property’s previous list rather than appending to it, so the final file must preserve every entry that should remain active.
The dated .txt contains the current project list as domain: lines and full source URLs. Before uploading, check Google's limits: 2 MB per file, 100,000 lines including comments and blank lines, and 2,048 characters per URL. A Screpy download is not proof that Google has accepted the file.
Use domain scope only when the evidence supports excluding links from the entire source domain. Use URL scope when the concern is limited to one exact source page and the rest of the domain should remain outside the list.
Google says most sites do not need it. Its guidance says to consider disavow when a considerable number of spammy, artificial, or low-quality links point to the site and those links have caused, or are likely to cause, a manual action. Links you control should be removed first when possible.
No. You choose the domain or URL entries after investigating the evidence. Add reviewed report selections in the dashboard or use authorized API/MCP actions; MCP changes require explicit confirmation. Neither method determines that a link is harmful or uploads the list to Google.
No. Deleting an entry removes it from Screpy’s next local export only. To change a list already uploaded to Google, prepare and upload the complete replacement list for that property. Google says reprocessing can take several weeks.
