Selection from backlink reports
Send selected records from Backlink Checker or Referring Domains into the disavow list without recreating source domains or URLs manually.
Backlink Disavow File Management
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.
TL;DR
Too Long; Didn't Read
Show summary Hide summary
TL;DR
Too Long; Didn't Read
What is Screpy Disavow Management?
Screpy Disavow Management is a project-only list for domains or source URLs selected after backlink investigation. It stores the chosen scope, optional decision note, and disavowed date, then exports the current list as a Google-formatted text file without choosing links or submitting the file for you.
Decide whether disavow is necessary
- Google describes disavow as an advanced feature that most websites do not need and warns that incorrect use can harm search performance.
- Investigate the live source, link pattern, ownership history, and any manual action before adding an entry.
- Try to remove links you intentionally built or controlled before using disavow for links that cannot be removed.
Add controlled project entries
- Select records from Backlink Checker or Referring Domains only when the analyzed target matches a project you control.
- Choose domain scope for every link from a source or URL scope for one exact source page.
- Save an optional note with the selected entries so the reason remains visible during final review.
Review the exact export list
- Compare total, domain, and URL counts before downloading the file.
- Review type, value, note, and disavowed date, with sorting by type, value, or date.
- Delete an entry with confirmation when it no longer belongs in the local export list.
Export and submit manually
- Screpy normalizes selected values and exports domains with the domain: prefix and source pages as full URLs.
- The dated .txt download is prepared for manual review; Screpy does not upload it to Google.
- Reconcile the export with any existing Google list before uploading because a new upload replaces the property’s previous list.
Investigate the link before building the list.
Start in Backlink Checker or Referring Domains. Review the source page, anchor, target, link attributes, dates, state, and wider pattern before selecting anything for disavow.
Learn more about evidence first- Open the live source and target pages
- Keep scores as review signals only
- Select records only for an owned project
Choose a domain or one source URL.
Move selected records into the project list as domain-level or URL-level entries. Add an optional note at selection time to preserve the reason for the decision.
- Domain-wide source scope
- Exact source-page scope
- Optional decision note
Review every entry before export.
Compare total, domain, and URL counts, sort the table by the field relevant to the review, and remove entries that no longer belong in the file.
- Type, value, note, and date
- Sortable review table
- Confirmed entry removal
Download the file; keep submission under your control.
Export the current project list as a dated .txt file with Google-compatible domain and URL lines. Review it against any existing property list, then upload it manually only when the evidence supports the action.
- Google-compatible domain: syntax
- Dated project file name
- No automatic Google submission
A controlled disavow file workflow
Move only reviewed records into an owned project list, keep the intended scope visible, and export the exact domain and URL lines you have approved.
Domain-level scope
Store a normalized source domain when the evidence supports asking Google to ignore links from the whole domain.
URL-level scope
Store one validated source-page URL when the concern is specific and the rest of the referring domain should remain outside the list.
Owned-project guard
Add entries only when the analyzed target matches a project you control; competitor research cannot populate the disavow list.
Decision notes
Attach an optional note when selected records are added so reviewers can see the stated reason before export.
List counts and sorting
Compare total, domain, and URL counts and sort the table by type, value, or disavowed date during final review.
Confirmed entry removal
Delete a domain or URL from the local export list through a confirmation dialog when the decision changes.
Dated .txt export
Download the current project list with domain: entries and full source URLs in a file named with the project domain and export date.
Move from link evidence to a controlled export.
Confirm the need, investigate the links, choose the narrowest justified scope, review the complete replacement list, and keep the final Google action manual.
- 01
Confirm that the problem warrants disavow
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.
- 02
Investigate and try removal first
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.
- 03
Choose the narrowest justified scope
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.
- 04
Review the complete replacement list
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.
- 05
Export, upload manually, and record the date
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.
Use a disavow list only for a defensible link problem.
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.
Support a manual-action cleanup
Organize links that remain after a documented removal effort when Google has reported unnatural inbound links and the evidence supports a reconsideration workflow.
- Manual-action context
- Removal evidence
- Final reviewed list
Address a known historical link scheme
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.
- Known campaign history
- Domain or URL scope
- Decision note
Hand off decisions between teams
Keep the selected value, scope, note, and disavowed date visible when responsibility moves between an internal team, consultant, or agency before the next export.
- Visible scope
- Stored reason
- Dated entry
Review an inherited disavow process
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.
- Existing-file check
- Ownership change
- Complete replacement review
Keep this advanced action inside its real limits.
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.
Most websites do not need this tool
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.
No metric proves that a link is harmful
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.
Screpy does not remove links or submit files
The list and export are preparation tools. Publishers control source-page removal, and a verified property owner controls the final Google upload or cancellation.
Google changes are cumulative and not immediate
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.
Choose the link workflow that matches the decision.
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
Learn how to manage disavow links
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.
Related SEO guides
Learn the concepts behind this workflow and apply them with practical SEO guidance.
SEO
What SEO Alerts Should You Monitor Before Traffic Drops
SEO alerts to track in GA4 and Search Console: indexing and crawl errors, ranking volatility, Core Web Vitals shifts, plus security or manual actions.
Read article GEO
How AI Improves Backlink Analysis for Smarter SEO Strategy
Learn how AI improves backlink analysis by identifying quality links, evaluating authority, auditing profiles, and shaping smarter SEO strategies.
Read article SEO
Backlinks and SEO: What are They and How to Get Them?
Learn what backlinks are, why they matter for SEO, and how authority, relevance, anchor text, and trustworthy sites shape link value.
Read article GEO
How Do You Monitor Brand Mentions in ChatGPT?
Monitor brand mentions in ChatGPT with a repeatable prompt set, tracking citation sources, competitor share of voice, sentiment, and response trends over time.
Read articleBacklink disavow decisions, files, and safeguards.
Understand when Google recommends this advanced action, how Screpy prepares the list, and what remains under the property owner’s control.
What does a backlink disavow file do?
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.
When does Google recommend using the disavow tool?
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.
Does Screpy automatically decide which links to disavow?
No. Screpy stores only the domain or URL records a user selects after reviewing Backlink Checker or Referring Domains. The website owner or SEO professional remains responsible for the evidence and final decision.
Should I disavow every backlink with a high spam score?
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.
Should I add a whole domain or one URL?
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.
How are entries added to Screpy?
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.
What does the Screpy export contain?
The dated .txt file contains normalized domain entries prefixed with domain: and full source-page URL entries. The file represents the project list at the time of export.
Does Screpy submit the disavow file to Google?
No. Screpy prepares the current project list for download. A verified property owner must review and upload the file manually with Google’s Disavow Links tool.
What if Google already has a disavow file for the property?
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.
Does deleting an entry in Screpy cancel an earlier Google disavow?
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.
Investigate first. Export only what you can defend.
Keep domain and URL decisions tied to live evidence, review the complete list before replacement, and leave the sensitive external upload under the property owner’s control.