You need the site to do something new: take appointment requests, show a price list, add a cookie banner. You type the job into the search box at Plugins → Add Plugin and get pages of results with similar names, similar star ratings and similar promises. Picking the first one is tempting. On a business website, it is also how a lot of long-running headaches begin.
You can learn how to choose a WordPress plugin well using the information the dashboard and the plugin directory already give you, and how to check a plugin before installing it on a site you depend on. Allow about ten minutes per plugin, which is far less than you will spend removing the wrong one later. It is also the first habit in our complete WordPress guide for owners.
Start with the job, not the plugin
Write down, in one sentence, what you need. “Let customers request an appointment slot and get an email confirming it” is far more useful than “booking plugin”, because it tells you which features matter and which are padding.
Then check two things before you search at all.
- Can WordPress already do it? The block editor now has buttons, columns, tables, galleries, embeds and a Details block for simple accordions. Plenty of older sites still run plugins for jobs that core WordPress handles today.
- Does something you already have do it? SEO plugins often include redirects and breadcrumbs. Form plugins may handle payments or surveys. Page builders bundle tabs, sliders and pop-ups. Using a feature you already own beats adding a second plugin for the same job.
If the answer to both is no, you are ready to compare plugins. Aim for a shortlist of two or three, not a single favourite you fell for in the first minute.
How to choose a WordPress plugin from the search results
Each result in the dashboard shows a card with the star rating, the number of active installations, when the plugin was last updated and a compatibility note such as “Compatible with your version of WordPress” or “Untested with your version of WordPress”. More Details opens the full listing. The same facts, plus reviews and the support forum, are on the plugin’s page in the WordPress.org directory. This is how I read each one.
| Signal | What it tells you | Reassuring | Worth a closer look |
|---|---|---|---|
| Last updated | Whether the developer is still working on it | Updated in recent months | A year or more, unless the plugin is tiny and simple |
| Tested up to | The newest WordPress version the developer has checked | Your current major version | An “Untested” label on a plugin that has not moved for a long time |
| Active installations | How widely it is used, shown as a rounded band | A large base and an established developer | A very small base for anything handling payments or personal data |
| Reviews | Real experiences, good and bad | Recent reviews describing a site like yours | A run of one-star reviews right after an update |
| Support forum | Whether anyone answers questions | Most recent threads answered or resolved | Months of questions with no reply |
| Requires PHP | The minimum server version it needs | At or below what your host runs | Higher than your hosting offers |
No single row decides it. A small plugin that does one display job can go a long time between updates and be perfectly fine. A compatibility label on its own is often harmless too; what that warning does and does not mean is covered in the “not tested with your version” warning explained.
Read reviews for patterns, not stars
An average rating hides more than it shows. Read the most recent reviews first, because a plugin that was excellent three years ago may have changed owners or direction since. Look for reviewers whose sites sound like yours: a small business site, the same page builder, a similar host.
Then look at how the developer replies to complaints. A calm, specific reply that solves the problem is a better sign than a perfect score. Be a little cautious when a plugin’s reviews are all short, all five stars and all posted close together. And give little weight to one-star reviews that only object to the paid version existing; they say nothing about whether the code is any good.
Check the support forum before you need it
On the directory page, the Support section lists recent threads, and the sidebar normally shows how many recent issues were marked resolved. You are not looking for a plugin with no problems. Every popular plugin has some. You are looking for a developer who turns up.
Open two or three threads that sound like problems you might hit. Did someone from the plugin team answer? Was the answer a real fix, or only a suggestion to buy the premium version? For paid plugins, support usually runs through the vendor’s own ticket system, so ask before buying how long support lasts and how you reach it.
Look at who makes it
The listing names the author, and clicking through shows their other plugins. A developer or company with several well-kept plugins and a real website is a safer bet than an unknown account with one plugin added last month. That is not a rule against small developers; plenty of excellent plugins are maintained by one careful person. It is a reason to look harder when the plugin will deal with payments, logins, file uploads or customer details.
Ownership changes too. Popular plugins are sometimes sold to new companies, which may add upsells, change direction or lose interest. A changelog that suddenly fills with marketing features instead of fixes is worth noticing. If a plugin you are considering has clearly gone quiet, read what to do about an abandoned plugin before you build anything on it.
Think about what it will sit next to
A plugin that is fine on its own can still be the wrong fit for your site.
- Two plugins, one job. Two SEO plugins, two caching plugins or two security plugins on the same site tend to get in each other’s way. If the new plugin replaces an old one, plan to remove the old one properly instead of leaving both running.
- Outside services. Some plugins send data to the developer’s servers, load scripts or fonts from elsewhere, or need an account to work. That can be fine, but it affects your privacy notice and cookie consent, and it matters if that service ever closes.
- Weight on every page. Sliders, social feeds and large form builders often add files to every page, not just the one that uses them. If speed matters to you, test a page before and after.
- Lock-in. Page builders, form builders and shortcode-heavy plugins store content in their own format. Leaving them later can mean rebuilding pages, so choose these with more care than a plugin you could swap in an afternoon.
Extra checks for premium plugins
Paid plugins sold outside the directory have no public install count and no review section you can fully rely on, so look for other evidence. A public changelog with regular entries, documentation that matches the current version, a clear refund policy and plain terms for what happens when the licence ends are all good signs. Buy from the developer’s own site or a known marketplace; the reasons are set out in where to download plugins safely. Many paid plugins also have a free edition in the directory, which is a sensible way to try the developer’s work first.
Try it before it touches the live site
Even a well-chosen plugin can clash with your theme or with another plugin. The safest place to try it is a private copy of the site, which is exactly what a staging site is for. With no staging copy, take a fresh backup, install at a quiet time, and check the pages that matter most (home, contact form, checkout) straight afterwards.
If you try a plugin and decide against it, deactivate and delete it the same day. An inactive plugin you have forgotten about is still something that needs updates.
Your checklist before installing
- Write the job in one sentence and confirm neither WordPress nor an existing plugin already does it.
- Shortlist two or three candidates.
- For each one, note last updated, tested up to and required PHP.
- Read the newest reviews and a couple of support threads.
- Look at the developer’s other plugins and website.
- Check for overlap with what is already installed.
- Test the winner on staging, or at least after a backup.
- Delete the ones you tried and rejected.
Choosing well is the first stage in the life of a plugin, and the rest of that life is mapped out in our guide to WordPress plugins.
Frequently asked questions
Is the plugin with the most installs always the safest choice?
Not always. A large user base means bugs are found and reported quickly, and an established team usually fixes them. But popular plugins are also studied closely by attackers, and some are heavy because they try to suit everyone. Treat install numbers as one signal among several, next to update history, support replies and how well the features fit your job.
Can I trust a plugin recommended in a blog post or video?
Use the recommendation as a starting point, then run the same checks yourself. Look at when the article was published, because a plugin praised years ago may since have changed owners or stopped being updated. Many review articles also earn a commission from the plugins they recommend, which does not make them wrong but is worth knowing.
What if no plugin does exactly what I need?
First ask whether a plugin that does most of it would be good enough with a small change to how you work. If the gap really matters, a developer can sometimes add a small snippet to an existing plugin, or build a small custom plugin. That costs more up front but avoids stacking several plugins to imitate one feature.
Should I choose a plugin that also does several other things?
Only if you will use those other things. A plugin bundling many features adds code, settings and update risk for all of them, even the parts you never switch on. A focused plugin that does your one job well is usually easier to live with, and easier to replace later if your needs change.
Down to two candidates and still unsure? A check against your theme and existing plugins before anything goes live is something our WordPress support services can help with.
Next in this series: Where to Download WordPress Plugins Safely
