Launch guidePlugins and integrations
How to launch a WordPress plugin
The WordPress.org plugin directory is a real search engine for site owners, and it's built from your readme.txt. Submission gets a human code review that can take up to 14 business days, then you ship through SVN. The directory's guidelines shape your business model: no trialware, no tracking without opt-in, no credit links without permission. Many plugins run a free directory version plus a paid add-on sold on their own site.
Updated · platform facts checked against the official docs linked below
At a glance
Where people find WordPress plugins
- WordPress.org plugin directory: Searched from inside every WordPress admin; readme.txt drives it.
- WordPress communities: Facebook groups, forums and subreddits for WordPress builders and site owners.
- Your own site: Docs and a pro version page that can rank for task searches.
- WordPress newsletters and blogs: Several cover new plugins; pitch with a clear use case.
Assets to prepare
| Asset | Spec or guidance |
|---|---|
| readme.txt | Header: Contributors, Tags, Requires at least, Tested up to, Requires PHP, Stable tag, License; sections for Description, Installation, FAQ, Screenshots, Changelog.[2] |
| Short description | No more than 150 characters, no markup.[2] |
| Banner | 772×250 and 1544×500 (retina), JPG or PNG, max 4 MB, in the SVN /assets folder.[3] |
| Icon | 128×128 and 256×256; PNG, JPG, GIF or SVG (SVG needs a PNG fallback), max 1 MB.[3] |
| Screenshots | screenshot-1.png, screenshot-2.png… in /assets, captions from readme.txt, max 10 MB each.[3] |
Store and listing rules
What the platform itself says, with a link to the page we checked.
- Plugins are reviewed within 14 business days once queued; approval gives you SVN access.[1]
- No trialware: functionality can't be locked behind payments, trials or quotas in the directory version.[4]
- No tracking without consent, and no external links or credits on the public site without the user's explicit opt-in.[4]
- Code must be human-readable (no obfuscation) and GPL-compatible; the plugin must be complete at submission (no name reserving).[4]
- "Tested up to" must be a version you actually tested; "Stable tag" points at the SVN tag of the latest stable release.[2]
A 4-week launch timeline
Week 1 · four weeks out
- Review the 18 guidelines against your plugin, especially trialware and tracking.
- Write readme.txt with a 150-character short description.
- Register on WordPress.org with an email you check; allowlist plugins@wordpress.org.
Week 2 · three weeks out
- Submit the finished plugin zip.
- Make the banner, icon and screenshots.
- Build the pro version page on your own site if you'll sell add-ons.
Week 3 · two weeks out
- Answer reviewer emails quickly; each round adds time.
- Write docs for the top three tasks.
- Prepare posts for WordPress communities.
Week 4 · launch week
- After approval, commit to SVN trunk, tag the release, and upload
/assets. - Check the listing renders banner, icon and screenshots.
- Line up a few users to leave honest reviews once they've used it.
- After approval, commit to SVN trunk, tag the release, and upload
Launch-day checklist
- Confirm the plugin installs from inside a fresh WordPress admin search.
- Post in WordPress communities with a short video of the setup.
- Launch the plugin's site on LaunchRanked.
- Watch the support forum on WordPress.org and reply within the day.
After launch: SEO steps
Launch boards reset; search pages don't. These steps keep people finding you after launch week.
- Write "how to {task} in WordPress" tutorials that use the plugin.
- Keep "Tested up to" current with each WordPress release; outdated plugins lose trust.
- Don't stuff readme tags or add affiliate spam; guideline 12 forbids it.
- Answer support forum threads; they're public and indexed.
Common mistakes
- Locking features in the free version, which breaks the no-trialware rule.
- Adding a "Powered by" link on the front end without opt-in.
- Assets in
trunk/assetsinstead of the top-level/assetsfolder. - Submitting an unfinished plugin to reserve the name.
Templates for this launch
- Directory listing descriptionWrite directory and launch-site listings once: a 60-character tagline, a 160-character short description and a long version, with a filled example.
- Changelog entryA changelog entry template grouped by Added, Changed, Fixed and Removed, written for users rather than commit logs, with a filled example.
- Release notesRelease notes for a notable launch or version: what's new, why it matters, how to use it, upgrade steps and known issues, with a filled example.
- Testimonial request emailAn email that asks happy customers for a testimonial with three easy questions, clear permission, and an option to review a draft, with a filled example.
FAQ
How long does WordPress.org plugin review take?
Once queued, the team says it reviews code within 14 business days. Replying fast to their emails keeps it moving.
What size is a WordPress plugin banner?
772×250, plus 1544×500 for high-DPI screens, in the top-level assets folder of your SVN repo.
Can I sell a pro version?
Yes, sold from your own site. The directory version can't be trialware: no locked features, trials or quotas.
How long can the short description be?
No more than 150 characters, with no markup.
Sources
- WordPress Plugin Handbook: Planning, submitting and maintaining plugins
- WordPress.org: Sample plugin readme.txt
- WordPress Plugin Handbook: Plugin assets
- WordPress Plugin Handbook: Detailed plugin guidelines
Checked . Platforms change their rules; open the source before you rely on a number.
Related launch guides
- How to launch a Shopify appShopify app launch guide: App Store requirements, 1200×1200 icon and 1600×900 screenshots, billing and session-token rules, review, and revenue share.
- How to launch a Webflow templateLaunch a Webflow template: become an approved creator, meet the quality rubric, name it well, get through review and market it beyond the Marketplace.
- How to launch an open-source projectLaunch an open-source project: README and repo setup, GitHub topics and social preview, Show HN rules, awesome lists, and docs that rank on Google.
- How to launch a Figma pluginFigma plugin launch guide: Community review, 128×128 icon and 1920×1080 cover, network access rules, paid plugins and where designers look.