Content dependencies
Find blocks and shortcodes in posts, templates, reusable content, builder metadata, and widget options.
Dependency analysis / Built by Pixeldust
See what could break—and what could be left behind—before removing a WordPress plugin.
Know what breaks before you click Delete.
The problem
Removing a plugin can erase blocks, disable shortcodes, stop scheduled jobs, break endpoints, orphan data, or leave behind tables and settings. This tool scans for those dependencies and cleanup risks before any change is made.
What it does
Six practical capabilities, organized around the one job this plugin is meant to do.
Find blocks and shortcodes in posts, templates, reusable content, builder metadata, and widget options.
Check post types, taxonomies, cron events, scheduled jobs, REST routes, AJAX actions, and active-code references.
Inspect options, transients, metadata, roles, uploads, custom tables, and uninstall-cleanup attribution.
A 1–10 score and red, yellow, and green rules prevent a serious finding from being buried.
Explain what could be affected, what remains, what to do, and how confident the scanner is.
Use bounded phases, batching, cancellation, locks, expiry, and verified state persistence.
How it works
Select an installed plugin you are considering removing.
Inspect content, runtime registrations, stored data, dependencies, and local source evidence.
Prioritize findings and convert them into an honest overall impact range.
Review the evidence, plan cleanup or migration, and make the removal decision yourself.
The boundary
Database queries and local source reads are read-only. Administrator permissions, nonces, plugin allowlists, canonical paths, and hard scan limits protect the process. Incomplete coverage is reported instead of being disguised as reassurance.