Need a plugin? Here is the method we use on our own sites and in client work to narrow down the options without installing the first result.
The Ratings
Start with a Google search for the job the plugin needs to do. If you need an anti-spam plugin, for example, search for “anti-spam plugin”:

Google may show ratings directly in the results, but open the plugin’s WordPress.org page as well. The developer has less control over the reviews there than on their own website. They are still user reviews, so read them critically.
Start with the rating, but also look at how many people left one.


If you have several options, a strong rating backed by plenty of reviews is a useful first filter. We usually become cautious below 4.0, but the number alone is not a verdict. Read the comments and find out what people are actually complaining about.
Sometimes a low rating reflects anger about a major change rather than a broken plugin. The Gutenberg editor shown above is a good example: many early reviews were reactions to WordPress replacing the old editor. That context matters when you judge the score.

And then there are plugins that actually are terrible, and the low rating is there for a reason. So do your due diligence.
Last Updated
This one is easy: when was the plugin last updated?


A plugin that has not been updated for a long time may be abandoned, incompatible with newer WordPress versions, or leave known security problems unpatched. It might still work today, but think twice before making it an important part of your site.
Quick extra checks: Does it list “Tested up to [your WP version]”? Are support threads getting replies?
Read the Reviews
Yes, I know I already mentioned reviews, but this is where a few minutes of research can save hours later. Look for compatibility problems, recurring bugs, and complaints that match your own setup.
Review Sites
Review sites can help you build a shortlist. They often compare several plugins for the same job and explain the main differences.

Why did I put the word “best” into quotes? Because it’s not always true!
Some reviews favor the plugin that pays the best affiliate commission. Others are written by people connected to the product. That does not make every comparison useless, but it does mean you should check who benefits from the recommendation.
Even a biased roundup can still reveal alternatives you did not know existed. Use it to find options, not to make the final decision for you.
You can also add “Reddit” to your search and read what people recommend in relevant discussions. Check the date, because plugin quality and ownership can change.

Prefer Paid
Sometimes it pays to pay for a plugin. A paid license often includes extra features or support, and it gives the developer a reason to keep maintaining the product. Check what the license actually includes, because payment alone guarantees nothing.
In cases where you absolutely REFUSE to pay for a plugin (hey, you don’t have to!) and have a choice between two excellent plugins, it might be a better option to go with the one that comes with a paid option (that offers extra stuff you don’t need).
If one plugin has both free and paid versions while another is entirely free, the first developer may have a stronger financial reason to keep the product alive. It is not a rule, but it is one useful signal.
Since their free plugin does the basic stuff and is a “foot in the door” method to get you to sign up for their paid plugin, they are also more motivated to keep it alive and working efficiently – no one is going to pay for your paid plugin if the free version sucks!
Test It Yourself
If the plugin passes the important checks – solid reviews, recent maintenance, and the features you actually need – test it yourself. Preferably, do that on a staging site before you trust it with the live one.