How to Submit a Plugin to the WordPress Plugin Directory: A Step-by-Step Guide

Recent Trends in the Plugin Directory

The WordPress Plugin Directory has seen a steady increase in submission volume over the past several years. The directory now hosts over 60,000 plugins, with thousands more submitted annually. Recent changes to the review process emphasize security hardening and compliance with updated WordPress coding standards. The plugin review team has also shortened the average initial review window, though the total time from submission to approval can still vary from a few days to several weeks depending on plugin complexity and back-and-forth communication.

Background and Submission Prerequisites

To submit a plugin to the official directory, developers must first agree to the GNU General Public License (GPL) or a compatible license. The directory is open to any developer who builds a plugin that is not a duplicate of existing functionality and that follows WordPress best practices. Before submitting, it is strongly recommended that a developer:

• Host the plugin in a public version-controlled repository (e.g., GitHub, GitLab, or Bitbucket).
• Include a clear readme.txt file with proper Stable tag and changelog.
• Verify that the plugin passes the WordPress Coding Standards checks using tools like PHP_CodeSniffer.
• Test the plugin with the latest stable version of WordPress and with common PHP versions (7.4 or higher).
• Check that the plugin does not perform any actions that require elevated user roles without explicit permission.

User and Developer Concerns

Submitters often report uncertainty around the review timeline and the specific criteria that will trigger a rejection. Common concerns include:

• Review delay: While initial reviews are faster than in previous years, resubmissions after a rejection can add several days to the process.
• Security audits: Plugins that make direct database calls without prepared statements, or that collect user data without a privacy notice, are likely to be flagged.
• Naming conflicts: The directory does not allow name squatting; a plugin whose title and description do not match its functionality may be rejected.
• External assets: Any third-party libraries or assets bundled with the plugin must be compatible with the GPL and properly attributed.

Likely Impact of the Current Review Process

The current submission and review system has several observable effects on the plugin ecosystem:

• Higher quality floor: Plugins that pass review tend to have fewer basic security flaws, which reduces the incidence of simple exploits across the directory.
• Longer time to market: Developers working on time-sensitive projects may need to factor in a review delay of one to three weeks, particularly for plugins that require multiple revisions.
• Community trust: The structured review process reassures site owners that listed plugins have been checked for common vector vulnerabilities, reinforcing the directory as the primary channel for downloading plugins.

What to Watch Next

Several developments are worth monitoring for anyone submitting to or maintaining plugins in the directory:

• Automated pre-screening tools: The WordPress.org team may introduce expanded automated checks that catch style and security issues before a human reviewer ever sees the submission.
• Plugin health guidelines: Updated documentation around data handling and GDPR/CCPA compliance is expected to be formalized in the review guidelines within the next year.
• Integration with block editor standards: As the Block Editor becomes the default editing experience, plugins that extend the editor may face additional checks regarding block registration and API usage.
• Changes to support requirements: There is ongoing discussion about requiring active support replies within a certain time window for existing plugins, which could affect how long a plugin remains listed.

Developers who stay current with the official Plugin Developer Handbook and the WordPress Coding Standards reduce their risk of rejection and streamline the submission process significantly.