Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Explainers · Explainer

What Is the WordPress Plugin Review Process?

Short answer

The WordPress plugin review process is the human check that every new plugin passes before it appears in the WordPress.org Plugin Directory. A volunteer reviewer reads the submitted code, checks it against the Detailed Plugin Guidelines, and either approves it or emails the author a list of fixes. After approval, each later release also passes a 6-hour automated security check before it reaches sites through updates.

Key takeaways

  • Every new plugin is read by a human reviewer before it can join the WordPress.org Plugin Directory.
  • Reviewers check security, licensing, privacy, naming, and whether the plugin follows the Detailed Plugin Guidelines.
  • A plugin is approved, moved to pending with a fix list, or rejected after 3 months without a reply.
  • Since June 5, every plugin release waits 6 hours while automated checks scan it for security risk.
  • In 2025 the Plugins Team reviewed 12,713 plugins and approved 5,415 of the 7,882 that followed the process.

What is the WordPress plugin review process?

The WordPress plugin review process is the check a new plugin passes before it joins the WordPress.org Plugin Directory.

It has two parts. First, a human reviewer reads the submitted code and checks it against the Detailed Plugin Guidelines. Second, after approval, later releases pass an automated security check before they reach sites.

The Detailed Plugin Guidelines state that the directory aims to give all WordPress users a safe place to download plugins. That goal shapes every step below.

Who reviews WordPress plugins?

Volunteer reviewers on the WordPress.org Plugins Team review new plugins.

The team was first called the Plugin Review Team. Make WordPress Plugins notes that it proposed the name Plugins Team to reflect work beyond new submissions, such as support, security reports, and directory tools.

Reviewers are volunteers, not paid staff of a single company. They use shared tools, checklists, and an internal scanner to spot likely issues, then confirm each one by reading the code.

What happens first when you submit a plugin?

You upload a ZIP file, receive an automated email, and join the review queue.

The Plugin Developer FAQ says the file must be a ZIP under 10 MB, in the normal WordPress plugin format. It also says you get an automated email confirming receipt, and your plugin is added to the review queue.

The FAQ adds that placeholders and plugins that are not ready to use are not accepted. Submit only a complete plugin that you can install and run.

What are the stages of a plugin review?

A review follows five steps: vet the author, read the code, approve it, or send it back for fixes.

The Performing Reviews handbook page lists the steps in this order. First, the author is vetted to check for current guideline violations. Second, the plugin is downloaded and reviewed for subject matter, security, and quality.

StageWhat happensWho acts
1. VettingReviewer checks the author and past submissionsReviewer
2. Code reviewReviewer downloads the ZIP and reads the filesReviewer
3. ApprovalPlugin is approved if no issues are foundReviewer
4. PendingPlugin moves to pending and the author gets a fix list by emailReviewer
5. Reply cycleAuthor replies with corrected code, and the cycle repeats until approvalAuthor

Third, the plugin is approved or moved to pending. Fourth, an email explains what to correct. Fifth, the author replies with corrected code, and the plugin is approved or the email cycle continues.

The handbook states the goal plainly: look for as much that is wrong as possible, identify it clearly, and tell the developer. That is why a review email often lists several issues of the same type.

What do reviewers check in the code?

Reviewers check security, licensing, privacy, naming, and whether the plugin does what its readme claims.

The Review Checklist starts with the name and subject matter, then the ZIP download, then a check of all files for guideline violations. It also asks reviewers to test in a secure setting and to email the developer from HelpScout with any issues found.

Key checks from that list include:

  • 100% adherence to the Detailed Plugin Guidelines and full support for the current version of WordPress.
  • A GPLv2 or later, or GPL-compatible, license, declared in the readme and plugin header.
  • No PHP or JavaScript errors, and no errors when run with WP_DEBUG set to true.
  • Validation, sanitization, and escaping of all data that is processed or saved.
  • A unique prefix for everything the plugin defines, such as options, functions, and constants.
  • Support for PHP 7.0.0 and up, or graceful failure if a newer version is required, as of November 2026.

Reviewers also check that third-party services are disclosed in the readme, with links to their terms and privacy policy. If a plugin collects user data, collection must be opt-in only, with the option disabled by default.

What rules cause most rejections or delays?

Security flaws, locked features, hidden code, and misleading claims cause most rejections or delays.

The Detailed Plugin Guidelines say all code, data, and images in the directory must use a GPL or GPL-compatible license. They also say code must stay human-readable, so obfuscation and unclear names such as $z12sdf813d are not permitted.

Plugins may not lock features behind payment or disable them after a trial period or quota. Paid services are allowed, but all code inside the free plugin must stay fully available.

Other common blocks include:

  • Contacting outside servers without explicit, authorized consent from the user.
  • Serving updates, or installing plugins and themes, from servers other than WordPress.org.
  • Including a theme, or including another plugin wholesale, instead of requiring it.
  • Using a trademark or another product name as the first term of a plugin slug.
  • Reproducing a WordPress core feature without a clear improvement, such as a plugin that only embeds YouTube videos.

The Review Checklist also lists types that are generally not permitted. Examples are black hat SEO plugins, plugins that promise you will earn thousands of dollars, and plugins that let users paste raw JavaScript, CSS, HTML, or PHP without sanitization.

How long does a plugin review take?

A small, clean plugin should be approved within 14 days of its initial review.

The Plugin Developer FAQ gives that 14-day figure for a small plugin with correct code. It also says the team aims to reply to all reviews within 10 business days.

If a review is not complete after 3 months, the submission is rejected to keep the queue workable. The FAQ says the review stays open, so the author can still reply and continue.

Do not resubmit the same plugin while a review is open. The FAQ says to reply to the original email thread instead, so the history stays in one place.

What happens after a plugin is approved?

Approval gives the plugin a Subversion repository, a public directory page, and a permanent slug.

The Detailed Plugin Guidelines say all plugins are examined before approval, which is why a ZIP file is required. Names cannot be reserved for future use, and an approved name that is not used may be given to another developer.

The Subversion repository is a release repository, not a development one. Every commit regenerates the downloadable ZIP files, so only code ready for release should be pushed there.

Users are only alerted to updates when the plugin version is increased. The trunk readme file must always reflect the current version of the plugin.

What happens to updates after a plugin is live?

Every release now waits 6 hours while automated checks scan it, and high-risk releases are blocked.

Make WordPress Plugins says that since June 5, every plugin and theme release goes through a cooldown before it is sent through the WordPress.org update API. The cooldown period is currently 6 hours, as of November 2026.

During that time, several AI models and Jetpack Scan analyze the changes. Their results are cross-checked and combined into a security score, where a higher score means higher potential risk.

Releases with a high risk score are blocked automatically, and all plugin committers receive an email with the findings. A high score does not prove bad intent, because an accidental flaw can score as high as intentional malware.

The fastest way to clear a block is to fix the reported issues and publish a new release. When the new release scores below the blocking threshold, it continues through the normal cooldown process.

That system caught a real case on July 28. Make WordPress Plugins says a backdoor was committed to a release of a plugin with around 20,000 active installations.

The automated review gave it a high security score, and the version was never sent through the update API. The plugin was closed for downloads 26 minutes after the Plugins Team was notified by Wordfence.

How busy is the review team?

The team reviewed 12,713 plugins in 2025, a 40.6% rise on 2024.

The 2025 year summary from Make WordPress Plugins reports that total. It also says 38.7% of the plugins reviewed received no reply from their authors.

Out of 7,882 plugins that followed the review process, 5,415 were approved. That is 69.5% of those plugins, up from 63.4% in 2024.

The same summary says the team carried out over 58,000 reviews in 2025, up 52.2%, because most plugins need more than one review. It also says reviewers found 59,137 issues, up 15.1% on the year before.

How can you check a plugin before you install it?

Check its directory page for last update, tested version, reviews, and any closure notice.

A plugin that passed review is not a promise that it stays safe or maintained. Review covers the code at submission time, and later releases pass the automated check described above, but authors can still stop updating a plugin.

Use these checks on the plugin page on wordpress.org:

  • Last updated date and version history, to see if the author still ships fixes.
  • Tested up to version, to see if it lists a recent WordPress release.
  • Number of active installs and recent reviews, to see how other site owners rate it.
  • Support forum activity, to see if questions get answers.

If a plugin shows a closure notice, read our guide on what happens when a plugin is closed on WordPress.org before you keep using it.

For help spotting stale plugins, see how to find abandoned WordPress plugins.

You can also run Plugin Check before you submit your own plugin. The WordPress Developer Resources page says it runs most of the checks used for new submissions and flags violations around internationalization, accessibility, performance, and security.

What mistakes should you avoid?

Do not submit early, hide code, or go silent after a reviewer emails you.

First, run Plugin Check and fix its findings before you submit. The handbook for free vs premium WordPress plugins explains why the free version in the directory must stay complete, even when a paid version exists elsewhere.

Second, reply to every review email with corrected code attached, and fix every instance of each issue, not only the lines quoted. The review cycle repeats until the code is right.

Third, keep your contact details on WordPress.org up to date. The Detailed Plugin Guidelines say auto-replies and emails that route to a support system are not permitted, because they stop humans from answering in good time.

Fourth, do not treat approval as a one-time pass. Keep the readme current, raise the version number for each release, and fix security reports fast. If a plugin is found to have a security issue, the guidelines say it will be closed until the situation is resolved.

Frequently asked questions

Does every WordPress plugin go through a review?

Every new plugin submitted to the WordPress.org Plugin Directory goes through a human review before it is listed. Plugins sold outside the directory do not go through that review, so check the seller, the code, and the update history yourself before you install one.

How long should I wait before I ask about my submission?

Wait for the review email first. The Plugin Developer FAQ says the team aims to reply within 10 business days, and a small, clean plugin should be approved within 14 days of its initial review. Reply to the original email thread if you need to add information.

Can I resubmit my plugin if it was rejected?

Do not resubmit the same plugin while a review is open. Reply to the original review email with corrected code instead. If a submission is rejected after 3 months without a reply, the review stays open, so you can still respond and continue the process.

Does approval mean a plugin is safe forever?

No. Approval means the code passed review at that time. Later releases pass a 6-hour automated security check, and a plugin can still gain a flaw or be abandoned. Check the last update date, tested version, and support activity before you install or keep any plugin.

What should I do if a plugin release is blocked?

Read the findings in the email sent to plugin committers, fix each reported issue, and publish a new release. A fixed release that scores below the blocking threshold continues through the normal cooldown. Publishing a fix is usually faster than waiting for a manual appeal.

Sources

  1. Detailed Plugin Guidelines WordPress Developer Resources
  2. Performing Reviews Make WordPress Plugins
  3. Review Checklist Make WordPress Plugins
  4. Plugin Developer FAQ WordPress Developer Resources
  5. A Year in the Plugins Team - 2025 Make WordPress Plugins
  6. Helper Plugins WordPress Developer Resources
  7. Make WordPress Plugins Make WordPress Plugins
  8. PHP Manual PHP Group

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test