It is that time again. All of your hard work is ready to see the light, and the WordPress.org plugin directory is where millions of site owners will find it. Here is the path we follow.

1. Get the plugin ready

  • Use a unique plugin name and a unique prefix for functions, classes and options.
  • License the plugin under the GPL (or a compatible license).
  • Sanitize input, validate data and escape output everywhere.
  • Never load unneeded remote code or track users without clear opt-in.

2. Write a proper readme.txt

The readme.txt file powers your plugin page. Include the plugin name, contributors, tags, Requires at least, Tested up to, Stable tag, a short description, installation steps, an FAQ and a changelog.

3. Test with the Plugin Check tool

Run the official Plugin Check plugin on your site. Fix every error and review the warnings before you submit.

4. Submit for review

Zip the plugin and upload it through the Add Your Plugin page on WordPress.org while logged in. A volunteer reviewer will email you. Reply to every point they raise, then upload a corrected zip if asked.

5. Commit your code with SVN

After approval you get an SVN repository. Check it out, copy your plugin into trunk, tag the release, and commit.

svn checkout https://plugins.svn.wordpress.org/your-plugin-slug svn-repo
cd svn-repo
cp -R /path/to/your/plugin/* trunk/
svn add trunk/* --force
svn copy trunk tags/1.0.0
svn commit -m "Release 1.0.0"
Remember: the Stable tag in readme.txt must match the version folder in tags, or visitors will download the wrong release.

6. Add banners and icons

Put your banner and icon images in the assets folder next to trunk (not inside it). They make the plugin page look professional.

7. Keep it healthy

Answer support threads, test each new WordPress release, and keep your changelog current. Updated, well-maintained plugins earn trust and installs.

Need help building or publishing a plugin? Talk to our team.