Last updated: October 17, 2026
Disclosure: some links in this post are affiliate links, marked as sponsored. If you buy through them I may earn a commission at no extra cost to you. I only recommend hosts I have used on real client sites.
Plugins are the fastest way to add features to WordPress, and the fastest way to slow it down, break it, or get it hacked. I build WordPress sites for small business clients with real budgets and average tech skills, so plugin choice matters for years after launch.
I first wrote this checklist in 2017. The core questions held up. What changed is how much security history matters, and how much your host can help.
The core questions
1. Do you really need this feature?
This is still the most important question. If the client won’t use it, or the site works fine without it, it is “extra.” Extras get installed last, and only if there is a well-built option.
2. Is the plugin popular?
The WordPress.org plugin directory shows “Active installations” on every listing. A popular plugin is popular for a reason. It also has a big user base finding bugs across thousands of setups before you do.

3. Is it well maintained?
Popular is not enough. I open the Support tab on WordPress.org and look at how many threads are marked resolved, and how quickly the author replies.

4. When was it last updated?
A plugin that hasn’t been updated in a year or more should be avoided, or used with great caution. WordPress.org now shows a warning when a plugin hasn’t been tested with the latest three major releases. Treat that warning as a red flag on anything important.

5. Who made it?
The person or team behind a plugin is who you depend on for updates, fixes, and support. A company with a paid product and a support team is a safer bet than an abandoned side project.
6. Does it have a clean security record?
This one is new to the list, and it is now near the top for me. Search the plugin name in a vulnerability database like WPScan, Patchstack, or Wordfence Intelligence. One fixed vulnerability is normal. A long pattern of them, or slow fixes, is not.
7. Does it support your PHP version?
The listing shows “Requires PHP.” If your site is still on an old PHP version, update that first. I explain how in changing your PHP version on WP Engine and Pressable.
8. Can you see it before you install it?
Screenshots, a demo, or a video save a lot of time. Often I install a plugin, try to set it up, and get turned off by the interface. Previews help you skip that.
9. Is there a paid version?
A paid tier or license is a good sign the authors will stick around. The price is often low enough that paying just for priority support makes sense.
10. How heavy is it?
Everyone loves a lean plugin, but feature creep is real. A plugin that does one thing very well beats one that does twenty things you don’t need.
11. Do the reviews hold up?
I don’t read individual reviews, but the star rating is useful when the review count is high. Reviews are easy to game one at a time. In aggregate they still say something.

Questions people skip
12. Is there an Automattic option?
Automattic, the company behind WordPress.com, makes a set of plugins (Jetpack is the big one) that may already cover what you need. See their author page in the directory.
13. Could a third-party service do it instead?
Video is the classic example. You can self-host video and add a player plugin, or you can upload to YouTube for free and embed it. No plugin, no extra maintenance, and your video can be found on YouTube.
14. Can your theme do it?
Some plugin features can be rebuilt with the block editor, a block pattern, or a little custom code in a child theme. Don’t cram PHP into functions.php without thinking it through, but don’t install a plugin for one button either. The theme handbook is the place to start.
15. Does your host allow it?
Managed hosts block some plugins that duplicate their own features or cause performance problems, like caching and backup plugins. WP Engine publishes a disallowed plugins list. Check before you build a feature around one.
Keeping plugins updated after launch
Choosing well is half the job. The other half is updating. Turn on auto-updates for plugins you trust, and test bigger updates on a staging site first. If you’d rather not babysit updates, WP Engine’s Smart Plugin Manager runs them for you and rolls back if a visual check fails. On Pressable, staging is included on every plan, and I show how to use it in Pressable staging sites.
Tired of plugin updates breaking things? WP Engine’s Smart Plugin Manager updates plugins on a schedule and rolls back automatically when something looks wrong.
FAQ
How many plugins is too many for WordPress?
There is no magic number. Ten badly built plugins can do more damage than forty well built ones. Remove anything you don’t use and watch for plugins that load scripts on every page.
How can I tell if a WordPress plugin is safe?
Check that it was updated recently, has many active installs, has resolved support threads, and has no pattern of unpatched issues in a vulnerability database like WPScan or Patchstack.
Should I use a plugin that hasn’t been updated in a year?
Avoid it for anything important. WordPress.org shows a warning when a plugin hasn’t been tested with the last three major WordPress releases.
Are premium plugins better than free ones?
Not automatically, but a paid version usually means the developers have a reason to keep updating and supporting it.
Why won’t my managed host let me install a plugin?
Hosts like WP Engine block plugins that duplicate built-in features, like caching and backups, or that cause performance or security problems. Check the host’s disallowed plugins list.
Related posts
- WordPress Security Best Practices: My 2012 List, Updated for 2026
- WP Engine Smart Plugin Manager: What It Does and Whether It’s Worth It
- Pressable Staging Sites: How to Create One and Push It Live
- How to Change Your PHP Version on WP Engine and Pressable
- How to Speed Up WordPress: Fixes That Start With Your Host
- Should You Use a Google Analytics Plugin for WordPress? (Updated for GA4)