Enter a plugin slug to find out whether it is still maintained, and if it is not, what to move to instead. Every alternative it suggests is checked against the WordPress.org directory before you see it, so nothing on the list is itself dead.
- WordPress does not tell you when a plugin you have installed is abandoned or removed from the directory. It keeps working and keeps saying nothing.
- A plugin closed for a security issue is the urgent case: the vulnerability is public, and no patch is ever coming.
- Abandoned is different from closed. Plenty of two-year-old plugins still work fine; the risk is that nobody is watching them.
- Suggested replacements here are verified live against WordPress.org, because well-known plugins get closed too.
- Deactivating is reversible, deleting often is not. Export settings and content before you remove anything.
How to tell if a WordPress plugin is abandoned
WordPress has no built-in warning for this. A plugin can be untouched for five years, or pulled from the directory entirely, and your dashboard will look exactly the same as it did the day you installed it.
The signals live on the plugin’s WordPress.org page, and they are worth learning to read:
- Last updated. Over a year is worth checking. Over two years, assume nobody is maintaining it unless the plugin is genuinely finished and tiny.
- Tested up to. If it lags the current WordPress release by two or more major versions, the author has stopped testing against new releases.
- Support forum. Unanswered threads going back months is the clearest human signal there is.
- A closure notice. The page says the plugin has been closed, when, and often why. This is the one that needs same-day attention.
To check everything running on a site at once rather than one slug at a time, use the WordPress plugin detector, which scans a URL and flags the whole list.
Closed, abandoned and stale are not the same problem
Treating all three as equally urgent leads to either panic or paralysis. They deserve different responses.
Closed for a security issue is the serious one. WordPress.org removed it because something was wrong and it was not fixed. The vulnerability details are frequently public, the plugin is frozen at its last version, and no update will ever arrive. Replace it, and treat that as this week’s job rather than this quarter’s.
Closed at the author’s request is much less alarming. Developers retire plugins for ordinary reasons: they sold it, they moved on, they folded it into something else. The code is no less safe than it was yesterday. You still want a migration plan, but there is no fire.
Abandoned but still listed means the plugin works and nobody is watching it. A small, self-contained plugin can go years without an update and be perfectly fine. A plugin that touches user input, handles payments, or exposes an endpoint is a different matter, because those are the ones where an unnoticed vulnerability actually costs you something.
That distinction is really about surface area. Ask what the plugin can reach. A plugin that adds an icon to your menu is not the same risk as one that processes forms, even if both last shipped in 2022.
Why the suggestions get verified
Asking any AI for plugin alternatives produces a confident list of well-known names. The problem is that well-known plugins get closed too, and a model working from memory has no idea which ones.
This came up while building the tool. Looking for a replacement for a closed membership plugin, the obvious suggestion was Paid Memberships Pro, a large and reputable name. Checking it against the WordPress.org API showed it had itself been closed in October 2024. Subscribe to Comments Reloaded, another obvious pick in a different category, was closed in April 2026.
So every suggestion this tool produces is looked up against WordPress.org before it reaches you. Anything found closed is dropped from the results and listed separately as rejected, so you can see the check happened rather than taking our word for it.
Swapping a plugin without breaking the site
The order matters more than the speed. Most plugin migrations that go wrong went wrong at step one.
- Take a full backup first. Files and database, downloaded somewhere off the server. Everything below is recoverable if you have this and nothing is if you do not.
- Export the old plugin’s settings and data while it is still active. Many plugins offer an export; once you deactivate, that screen disappears with it.
- Install the replacement alongside the old one and configure it before switching anything over. Running both briefly is usually fine, though avoid it with two caching or two security plugins.
- Find every shortcode, block and template tag the old plugin provided. This is the step people skip, and it is why pages come back blank. Search your content for the old shortcode name before you deactivate.
- Deactivate, do not delete. Check the site properly, then leave it deactivated for a week. Deleting usually drops the plugin’s database tables and options with it.
- Delete once you are confident, since a deactivated plugin still sits on disk and still needs to be kept in mind.
If something breaks mid-migration, the fastest way to find out what is to work through our guide to diagnosing WordPress plugin conflicts. If the site goes white entirely, the white screen of death has the recovery steps, and you can paste the error into our error log explainer to find out which plugin caused it.
Frequently Asked Questions
Where do I find a plugin’s slug?
It is the last part of the plugin’s WordPress.org URL. For wordpress.org/plugins/wp-super-cache/ the slug is wp-super-cache. It is also the folder name inside wp-content/plugins, which is the easier place to look if you have file access and the plugin has been removed from the directory.
Do I have to replace an abandoned plugin straight away?
Not always, and pretending otherwise leads to a lot of pointless migrations. If it was closed for a security issue, yes, act now. If it is simply old, judge it on what the plugin can reach: something handling forms, payments, file uploads or user accounts deserves urgency, while a small display plugin that has worked for three years usually does not. What you should not do is forget about it, since the risk only ever increases.
Will I lose my content when I switch plugins?
Content stored as posts or pages stays put, because it lives in WordPress rather than in the plugin. What you can lose is anything the plugin kept in its own tables or options: settings, form entries, custom fields, gallery arrangements, membership records. Deactivating rarely removes data, but deleting frequently does. Export first, deactivate rather than delete, and give it a week before removing anything.
The tool suggested a premium plugin. Why no verification badge?
Commercial plugins are not in the WordPress.org directory, so there is nothing to verify against. That is not a mark against them, it just means the automatic check cannot apply and you should look at the vendor’s own changelog for update activity.
Related: scan a whole site with the plugin and theme detector, or read our picks for the best WordPress plugins.
Browse all our free WordPress tools, all free and none of them asking for an email address.
