A Paramus law firm called us last March. Their site had been throwing 500 errors for two days. The culprit: a slider plugin they’d run since 2017. Last update: 2021. Last support reply: 2022. Author profile: inactive 18 months. PHP 8.2 landed on their host and the plugin’s deprecated calls took the site down. Recovery cost: $1,800 in our time plus four days of zero lead intake — call it $11,000 in lost pipeline. The fix would’ve been free six months earlier.
Every WordPress site we audit has at least one plugin that’s already dying. Most owners can’t tell. The plugin still “works” — until a PHP update, a core update, or a hosting migration kicks the legs out. The signs are loud months in advance if you know what to look for.
Red flag 1: last update older than 6 months
Open your WordPress dashboard, go to Plugins, and scan the “Last Updated” column. Anything past 6 months gets a yellow flag. Past 12 months is red. Past 24 months is a fire. Active, maintained plugins ship at minimum a quarterly update — usually monthly. A six-month gap means the developer has either lost interest or lost the ability to maintain it. Either way, the next compatibility crunch is going to break you, not them.
The exception: utility plugins with tiny scope (one shortcode, one filter) that genuinely don’t need updates. Those are rare. If the plugin touches the editor, the database, or the frontend, it needs ongoing maintenance, period.
Red flag 2: active install count dropping
Visit the plugin’s page at wordpress.org/plugins. Look at “Active installations.” Anything under 1,000 is risky for production. Under 500 is risky for any site that earns revenue. But the absolute number matters less than the trend. The plugin page used to show install trend graphs publicly — Google “[plugin name] wordpress.org active installations” and you’ll often find archive captures. If the count was 50,000 two years ago and 8,000 today, users are fleeing. They know something you don’t.
Red flag 3: support forum graveyard
On the same plugin page, click “Support.” Look at the most recent threads. Two questions to answer:
- Is the author responding? If the last 10 threads have no author reply, the plugin is functionally abandoned even if it occasionally gets a version bump.
- Are the bugs being fixed or just acknowledged? “Thanks for reporting, we’ll look into it” replies from 2023 that never went anywhere are abandonment in slow motion.
- Are paying customers complaining? Premium plugins with angry threads about unrefunded purchases mean the business behind the plugin has collapsed.
- How long do unresolved threads sit? A healthy plugin has most threads resolved within 14 days. A dying one has months-old threads still unanswered.
- Are recent threads about PHP/WP version compatibility? That’s the canary. When users start reporting “fatal error after WP 6.x update” and the author goes silent, you’re 60-90 days from disaster.
Red flag 4: author profile abandoned
Click the author’s name on the plugin page. Look at their profile. When did they last post? Last commit? Last reply to anything? An author with no activity for 18+ months across all their plugins is gone — moved jobs, lost interest, sold the portfolio to someone who hasn’t shown up yet. Sometimes you’ll find a forum post where the author quietly says “I no longer have time to maintain this.” Treat that as the plugin’s death certificate.
The audit: 20 minutes, every quarter
Open your plugin list in a spreadsheet. For each plugin, fill four columns: last update date, active installs, last support reply, author last seen. Color each cell green/yellow/red. Any plugin with two reds or three yellows goes on the replacement shortlist. Then check the WordPress Plugin Directory for actively-maintained alternatives in the same category. Most categories have at least one strong, well-supported option — usually with better UX and a lower performance footprint than the dying plugin you’ve been running for years.
Replace before you have to. Migrating during a working week costs hours. Migrating during a Saturday-night outage costs days plus reputation.
How AJD handles this
Every site on our maintenance plan gets a quarterly plugin-health audit. We score each plugin on the four flags above and produce a replacement queue ranked by risk. We test the replacement in a staging environment, migrate settings and data, and ship the swap on a low-traffic window. The audit runs about 45 minutes per site. Catching one dying plugin before it takes the site down pays for years of audits.
Whether you work with us or not, open your plugin list today and check the “last updated” column. Any plugin past 12 months is a ticking clock. Replacement is cheap. Recovery from a dead plugin taking down your site on a Tuesday afternoon is not.
