Most WordPress site owners never think about the plugin review queue. Why would you?
You search the directory, compare a few screenshots, maybe skim reviews, and install the tool that solves the problem in front of you. That is the normal workflow. It is also exactly why this matters.
Earlier this month, the WordPress Plugins Team put out a public call for more reviewers and sponsors. The headline number jumped out at me: plugin submissions are now exceeding 500 per week. That is a dramatic rise from the roughly 100 to 150 weekly submissions the team was seeing in earlier years.
If you run a WordPress site, that is not just inside-baseball community news. It is a signal about how much pressure is building under one of the most important trust layers in WordPress.
Why the review queue is your problem too
The goal is not to turn every site owner into a plugin reviewer. The goal is to understand that the plugin directory is not magic. It is a living system run by people, processes, and tools.
When that system is healthy, you get a few benefits quietly:
- Better baseline trust in what shows up in the directory
- Clearer standards for plugin authors
- Faster responses when edge cases or violations appear
- More consistent quality before a plugin ever reaches your shortlist
When that system is stretched, everything gets a little noisier. New plugins can take longer to appear. Reviewers have to prioritize harder. Plugin authors may feel pressure to ship elsewhere first. And site owners get one more reason to slow down and evaluate carefully.
That does not mean the directory is suddenly unsafe. It means the invisible work behind it deserves more attention than it usually gets.
WordPress is trying to scale this responsibly
To WordPress’s credit, this is not a story about ignoring the problem. It is a story about admitting the scale has changed.
In the team’s post, Francisco Torres explains that the current pace is breaking records almost weekly and that the team needs more people and more sponsor-backed time to keep up. The same post also points to the practical work already happening around Plugin Check, internal tools, and stronger processes to help maintain standards at scale.
That matters. A lot.
WordPress has always done well when it treats boring infrastructure as a first-class part of the product. Review workflows, security checks, contributor training, and sponsor support are not glamorous. They are also the reason a huge ecosystem can stay useful without collapsing into chaos.
What site owners should do differently right now
Here’s the practical angle. If plugin volume is rising faster than review capacity, site owners should tighten up their own selection habits.
1. Stop treating “in the directory” as the only trust signal
Being listed in the official directory still matters. I keep coming back to that. It is a meaningful signal. But it should not be your only one.
Look at:
- How recently the plugin was updated
- Whether the support forum shows active responses
- Whether the company or author has a visible track record
- Whether the plugin has clear documentation and changelogs
2. Prefer boring, well-supported choices for critical features
If the plugin touches checkout, backups, redirects, SEO, forms, memberships, or security, boring is good. You do not need the newest shiny thing in those categories. You need the tool that will still be standing six months from now.
3. Audit your plugin stack more often
As the plugin ecosystem grows, it gets easier to accumulate overlap. Two SEO helpers. Three optimization tools. A form plugin plus an add-on that duplicates half its features. A small quarterly audit can remove a surprising amount of risk and clutter.
4. Watch the teams that protect the ecosystem
You do not need to live in Make WordPress, but it is smart to keep one eye on the community teams that quietly shape plugin quality. The Plugins Team, the Performance Team, and the broader contributor ecosystem often tell you where the stress points are before they show up on your own site.
This is also a good sign, oddly enough
There is another way to read the 500-plus-submissions number: people still want to build on WordPress.
That is easy to miss when ecosystem conversations get too cynical. But a plugin directory that is growing this fast is also evidence of energy. New products, new experiments, new business models, new use cases. WordPress does not have a relevance problem here. It has a scale problem.
And scale problems are usually better than stagnation problems… as long as the infrastructure keeps up.
The takeaway
If you run a WordPress site, the plugin review backlog is not just a developer issue. It is part of the trust system your site depends on.
The good news is that WordPress is naming the problem clearly, building better tooling, and asking for help in public. That is the kind of behavior I want to see from an open ecosystem.
For site owners, the move is simple: choose more carefully, audit more regularly, and pay a little more attention to the quiet teams keeping the directory solid.
That may not be flashy, but it is useful. And in WordPress, useful tends to age well.