Impact Check helps WordPress maintainers reduce uncertainty before deactivating a plugin. Select one active plugin and run a conservative, read-only scan for stored content using shortcodes or server-registered blocks attributable to that plugin.
The report shows:
- Matching content title, type, and status.
- Exact shortcode tags and block names with occurrence counts.
- Native Edit and View links when the current user has permission.
- Attribution and scan coverage so limitations remain visible.
Impact Check is designed for agencies, freelancers, and technical site owners working on inherited or plugin-heavy sites. It uses the active WordPress runtime registries and local content, which lets it start from the plugin rather than requiring you to know a shortcode or block name first.
Important limitations
An empty report does not prove that a plugin is unused or safe to deactivate. The scan does not inspect plugin data, settings, widgets, hooks, templates, client-only blocks, custom tables, metadata, files, network-active plugins, themes, mu-plugins, or remote integrations. Oversized or otherwise skipped content makes a scan incomplete.
The plugin never deactivates plugins, changes content, or makes a deactivation recommendation. Use a backup or staging site and your normal change-control process before modifying a production site.
Privacy and external services
Impact Check runs locally on your WordPress site. It has no telemetry, tracking, external service, account requirement, cookies, browser storage, or outbound network request. Results exist only for the current page session, and the plugin creates no options, metadata, custom tables, files, or logs.