A WordPress plugin audit is a review of every installed add-on that adds features to your site. To remove unused plugins safely, back up the full site, deactivate one plugin, test key functions, then delete it if nothing breaks. Work through one plugin at a time. That pace makes it easy to link any problem to the last change and reverse it.
Table of Contents
- Which plugins do you still need?
- How do you back up before changes?
- How do you test before you delete?
- When should inactive plugins go?
- What does Delete leave behind?
Which plugins do you still need?
Start from the Plugins screen. WordPress.org Documentation explains in its Plugins screen guide that the screen handles activation, deactivation, updating and deletion.
The same source points to Tools > Site Health to flag plugins that need an update or removal. Mark likely candidates before you change anything. Look for inactive plugins, duplicate tools, and features you already retired:.
- Inactive plugins with no clear future use
- Two plugins doing the same job, such as two form builders
- Tools for retired features, such as an old slider or popup
How do you back up before changes?
Make a restorable backup before you remove anything. Developer.WordPress.org Advanced Administration Handbook advises in its backup handbook that a backup must cover both site parts, files plus database.
The handbook also advises regular backups and a fresh backup before any upgrade or disruptive change. Confirm you can restore from that backup. Remove plugins only after the backup is stored where you can reach it.
How do you test before you delete?
Deactivate one candidate and leave it installed. WordPress.com Support recommends testing in its deactivation and deletion guide.
After deactivation, check key pages, forms, checkout, menus and widgets on a staging copy. Delete only after nothing breaks. Keep the inactive period short so a disabled plugin does not sit for weeks:.
- Deactivate one plugin
- Test forms, checkout, menus, and mobile layout
- Delete if clean, or reactivate if needed
When should inactive plugins go?
Treat long-term inactive plugins as cleanup targets. The Developer.WordPress.org reference for WP_Site_Health::get_test_plugin_version() warns you should remove inactive plugins because they tempt attackers even when switched off.
Watch for abandoned plugins too. The DreamHost blog defines an abandoned plugin as one the developer no longer maintains, flagged when untested across the latest three major releases. Such plugins can turn incompatible, vulnerable and eventually closed.
What does Delete leave behind?
WordPress.org Documentation notes in its plugin management guide that deletion is for inactive plugins and removes plugin files. The same guide warns that settings, database tables or shortcodes may remain.
Open the plugin's uninstall notes before you delete. Remove leftover settings or tables only as directed. Check old posts for dead shortcodes and replace them with current blocks.




