How to Submit Your WordPress Plugin to the Plugin Directory
- Prepare Your WordPress Plugin
- Validate with Plugin Check
- Submit to WordPress.org
- Handle Support & Bug Reports
- Update and Version Control
- FAQ
1. Prepare Your WordPress Plugin
If you’re developing a WordPress plugin, especially one that enhances SEO or content editing like our ozwebexpert/faq block, the first step is to structure it correctly.
Your plugin must include the following:
plugin-name.php— with header inforeadme.txt— in WP.org format- Assets (CSS, JS) loaded only where needed
- No external API calls or data collection
/*
Plugin Name: OZ FAQ Block
Plugin URI: https://ozwebexpert.com/
Description: Gutenberg block with JSON-LD FAQ schema support.
Version: 1.0
Author: Grigory Frolov
*/
2. Validate with Plugin Check
Before submitting, test your plugin with the following tools:
- Plugin Check — validates coding standards
- PHP Compatibility Checker
- Manual testing with different WP versions and themes
3. Submit to WordPress.org
Once validated, go to the Submit Plugin page and fill out the form. You’ll need a .zip or a public repository URL (GitHub allowed).
After approval, you’ll receive access to a Subversion (SVN) repo. Structure it like so:
/trunk/
plugin.php
index.js
style.css
/tags/1.0/
[same files as trunk]
4. Handle Support & Bug Reports
Once your plugin is live, users may report issues. Here’s how to stay on top of it:
- Monitor the Support tab on your plugin’s WP.org page
- Add a
GitHub Issuesor contact link in yourreadme.txt - Respond professionally — you’re building reputation as a plugin developer
5. Update and Version Control
To release a new version:
- Update the version number in the plugin file and
readme.txt - Commit changes to
/trunk/ - Copy trunk to a new
/tags/1.x/folder
This ensures all users get the update through their WP admin dashboard.
FAQ
What is a WordPress plugin?
A WordPress plugin is a package of code that extends WordPress functionality without modifying core files. Plugins can add new features, blocks, integrations, or admin tools.
Do I need coding skills to publish a plugin?
Yes, at least basic PHP, JS, and WordPress functions. Tools like the Plugin Boilerplate or WP Scripts help speed up development.
What are best practices for WordPress plugin development?
Follow WP coding standards, avoid hardcoding paths, enqueue scripts and styles conditionally, escape and sanitise all inputs/outputs, and maintain backward compatibility. Use hooks and filters to integrate cleanly with the core.
What is the difference between trunk and tags in plugin SVN?
/trunk is your working directory, while /tags/ holds frozen versions for public release (e.g. 1.0, 1.1, etc.).
How is a custom plugin different from off-the-shelf plugins?
Custom plugins are tailored to your exact needs and often integrate tightly with your theme or business workflow. Off-the-shelf plugins are general-purpose and might include bloat or unwanted features.
Can I make money with a WordPress plugin?
Yes. You can offer a free version via WordPress.org and upsell a Pro version via your own site.