Who writes WP Vetted
WP Vetted articles are written by Alex, a WordPress and WooCommerce developer with more than 14 years of hands-on experience. His background includes agency work for clients in the USA, Europe, and Australia, covering implementation, troubleshooting, performance, integrations, ecommerce, and ongoing maintenance.
WP Vetted covers WordPress, WooCommerce, plugins, performance, security, and the wider ecosystem. Some recommendations come from hands-on work with a product. Others come from current research into documentation, release history, compatibility, pricing, support, security, and adoption. We distinguish between those evidence levels instead of presenting every product as freshly tested.
What “hands-on” means
When we describe a product as hands-on, we mean it has been used in real WordPress or WooCommerce work, not installed for a few minutes solely to add a “tested” badge to an article. Hands-on experience can include implementation, configuration, troubleshooting, upgrades, compatibility work, or operating the plugin on a live site.
We do not claim hands-on experience where we do not have it. A roundup can combine first-hand experience with researched recommendations, and the article should make that distinction clear when it matters.
How researched recommendations are evaluated
A plugin does not need to have been used in a current client project to be considered, but a researched recommendation needs a credible evidence trail. Depending on the product, we look at the following factors:
- Maintenance: recent releases, changelog quality, compatibility updates, and whether development appears active.
- Compatibility: current WordPress and WooCommerce support, PHP requirements, HPOS, Cart and Checkout Blocks, and other relevant platform changes.
- Product fit: whether the plugin solves a real problem without creating unnecessary overlap with the rest of the stack.
- Free-tier quality: whether a free version is useful on its own or mainly exists to advertise an upgrade.
- Pricing and value: license cost, recurring fees, usage limits, required add-ons, and the importance of the problem being solved.
- Security: disclosed vulnerabilities, response to security issues, update availability, and the risk profile of the feature area.
- Support signals: documentation, support activity, public issue patterns, and the vendor’s ability to maintain a business-critical product.
- Adoption: active installations, reviews, ecosystem integration, and real-world usage where those signals are relevant.
Popularity is evidence, not a verdict
Install counts and ratings can be useful, but they do not automatically make a plugin the best choice. A smaller plugin can be better for a specific workflow, while a very popular plugin can still be the wrong fit for a particular server stack, checkout architecture, catalog, or business model.
We evaluate the whole stack, not just the feature list
WordPress plugins do not run in isolation. A caching plugin depends on the hosting stack. A checkout extension has to coexist with payment gateways and shipping logic. A subscription plugin becomes part of a recurring-billing system. Security and backup tools affect infrastructure and recovery.
That is why our recommendations often include conditions such as “best on LiteSpeed,” “best for direct Stripe,” or “best when subscriptions are business-critical.” Context is more useful than declaring one universal winner.
Free and paid products compete on the same problem
We include free, freemium, paid, and SaaS products when they are relevant. A paid product does not rank higher merely because it costs more, and a free product does not rank higher because it is easier to recommend. The question is whether the product is a strong choice for the use case described.
How affiliate links affect our recommendations
Some WP Vetted articles may contain affiliate links. If a reader buys through one of those links, WP Vetted may earn a commission. Affiliate availability does not determine which products are included, which product wins a category, or how alternatives are discussed.
Where affiliate links are used, they should be clearly disclosed and technically marked appropriately. We would rather recommend a product with no affiliate program than move a weaker product up a list because it pays a commission.
How we handle updates
Plugin recommendations age quickly. Prices change, free tiers shrink or expand, compatibility changes, security advisories are published, and products can improve or deteriorate. Articles may therefore show both an original publication date and an updated date when the editorial recommendation or supporting evidence materially changes.
We also link to current vendor documentation and primary sources where they help readers verify time-sensitive claims for themselves.
What readers should expect from WP Vetted
We aim to be selective, specific, and transparent about the basis for a recommendation. We will not manufacture testing claims, treat every popular plugin as a winner, or publish an oversized list simply because more product names create more affiliate-link opportunities.
The standard is simple: a recommendation should help a reader make a better WordPress or WooCommerce decision than they could make from a feature table alone.
You can see this methodology applied in our best WooCommerce plugins in 2026 and best free WooCommerce plugins in 2026 guides.