Clean up plugins and apps with a dependency checklist

Extension cleanup is a small change-management project. Identify the business purpose and dependencies before removing anything.

1. Build the inventory

Record each plugin or app, its owner, licence and function. Include code injected manually or through a tag manager.

2. Identify overlap

Look for duplicated functionality and features that no longer support a current business need. Confirm with the people who use the site.

3. Test removal away from production

Use staging or a theme copy, keep a backup and follow the vendor’s instructions. Check for residual code and data that needs preserving.

4. Measure and document

Compare the relevant workflow and performance before and after. Save a record of what changed so future maintenance has a reliable starting point.

When to ask for help

Stop if the change affects a critical workflow, requires access you do not have or produces a result you cannot explain. Keep the original evidence and a restorable backup. A short, well-defined repair request is easier to review than a series of speculative changes.

Related repair: request a scope review. Choose your platform on the request form; availability and price are confirmed before payment.