Quick answer
To review a WordPress plugin nobody remembers installing, record its name, version and stated purpose, then look for pages, forms or settings that depend on it. Test removal on a staging copy, keep a backup, and retire it in stages. Do not delete first and ask later.
- Ask staff and past suppliers what the plugin was for, and record its stated purpose from its listing.
- Test deactivation on a staging copy first, then on the live site only with a backup in place.
- If you cannot tell what it does, leave it active and ask your maintainer, then record the decision.
A plugin that nobody remembers installing may still power something important. Before removing it, check its purpose, dependencies and evidence of use, then retire it in stages. This article is for WordPress site owners and maintainers. It is written for wordpress site owners and maintainers and ends with the decision, owner and next step to record.
An illustrative scenario
This is a hypothetical example, not a Web Design Davao client case.
Situation. A plugin has no documented owner and may still support a business-critical workflow.
What happens. A team finds a plugin nobody remembers. It records its stated purpose, discovers that a contact form uses it, tests removal on a staging copy and replaces the function before retiring it with a backup in place.
Background
WordPress plugins add features but also add code that must be kept up to date, and unused ones can become a risk. When nobody remembers a plugin, resist deleting it straight away because something may depend on it, such as a form, a redirect or a scheduled job. Find out what it does from its listing and settings, look for evidence of use, test removing it on a copy of the site and keep a backup before changing the live one. The decision is then recorded, not remembered.
Purpose and dependency audit
Record the plugin’s name, version and stated purpose from its listing. Use the plugin and stated purpose fields. Ask staff and past suppliers what it was for.
Usage evidence
Look for evidence of use: pages, forms or settings that depend on it. Use the dependency and usage evidence fields. Test on a staging copy where you can, and never delete first and ask later.
Staged retirement
Retire in stages: deactivate on staging, test, then deactivate on the live site with a backup in place. Use the test result and retirement decision fields. Keep a record.
Plugin ownership register
Use this at the point described above. The workflow owner completes it and a named reviewer checks it. A completed row shows that the information, owner and next step are recorded; it does not prove the outcome. Keep it somewhere the team can edit, and keep it free of passwords, tokens and real client records.
Blank copy
| Plugin | Stated purpose | Dependency | Usage evidence | Test result | Retirement decision |
|---|---|---|---|---|---|
Illustrative completed row (hypothetical)
| Plugin | Stated purpose | Dependency | Usage evidence | Test result | Retirement decision |
|---|---|---|---|---|---|
| Plugin X (illustrative) | Form handling, per its listing | Contact page form | Submissions logged | Staging test passed | Replace, then retire after backup |
Working through the completed row
In the row, the plugin’s listed purpose is form handling, the contact page form depends on it, submissions are logged, the staging test passed and the decision is to replace then retire after a backup.
Common mistakes
- Deleting first.
- Not testing on a copy.
- Not recording the decision.
Questions to settle before you rely on it
- What does the plugin do and what relies on it?
- Is there evidence it is used?
- Have you tested removal on a copy?
How you know it is complete
The register is complete when each plugin has a purpose, dependency, evidence, test result and decision. Record who reviewed it and the date.
Where you may not have the answer
You cannot tell what it does. Leave it active and ask your maintainer. The handoff, not a guess, is the correct next step.
Your next action
List every plugin and mark those with no documented owner.
Ask Web Design Davao to review this workflow and scope the website or marketing support required. Website maintenance & security arrangements are agreed individually; nothing here assumes a particular service, role or timing is already available.
Published data
Published data: Patchstack reported that 96% of the vulnerabilities it found in the WordPress ecosystem in 2024 were in plugins (State of WordPress Security in 2025), and that 46% of vulnerabilities disclosed in 2025 had no patch available at disclosure (State of WordPress Security in 2026). These are ecosystem figures, not a statement about any one site.
How Web Design Davao works
- Enquiries are generally answered within four hours during support hours (Monday to Friday, business hours), with after-hours help for emergency requests. Scope is agreed individually.
- Preventative website maintenance includes keeping plugins up to date and reviewing website code for known vulnerabilities. This reduces exposure to attack; it does not guarantee a site cannot be compromised. See website updates and uptime monitoring.
Frequently asked questions
Is it safe to delete a plugin nobody remembers?
Not straight away. Something may depend on it, such as a form, a redirect or a scheduled job. Find its purpose, look for evidence of use, test removal on a copy of the site and keep a backup before changing the live site.
How do I find out what a plugin does?
Check its listing and settings for the stated purpose, then look for pages, forms or settings that depend on it. Ask staff and past suppliers what it was for. If you still cannot tell, leave it active and ask your maintainer.
How should I retire an unused plugin?
Retire it in stages: deactivate it on staging, test, then deactivate on the live site with a backup in place. Record the test result and decision in a plugin ownership register, along with who reviewed it and the date.