Submitting to WordPress.org

You'll need:

• A completed build with a downloaded ZIP (not all builds are suitable — see readiness review below)
• A free WordPress.org account
• SVN installed on your computer (or a GUI client like TortoiseSVN)
• A plugin that is genuinely useful and original — reviewers reject clones, placeholder plugins, and plugins that simply wrap third-party APIs without adding value

Open your project (Dashboard → Details) and click Submission Center. Run the Readiness Review — this calls a specialist AI agent that checks your plugin against the most common WordPress.org rejection criteria:

• All external HTTP calls properly documented and user-disclosed
• Correct plugin file header (Plugin Name, Description, Version, Author, License)
• No call-home on activation without user consent
• Proper capability checks on all admin-only actions
• Nonce verification on all form submissions
• No data storage without a clear privacy disclosure
• No trademark or brand-name violations in the plugin slug

Issues are colour-coded: Errors must be fixed before submitting; Warnings are things reviewers may ask about but won't necessarily reject for.

From the Project Details page, open the Readme tab. The AI has already generated a readme.txt in WordPress.org format. Review it carefully:

• Short description — must be under 150 characters and describe what the plugin actually does (no marketing language)
• Tested up to — update this to the latest WordPress version you've tested on
• Tags — 1–5 tags from the approved tag list
• Privacy section — required if your plugin stores data or calls external services
• Screenshots — highly recommended; link to files you'll upload to the assets/ folder on SVN

Use the Ask AI to improve button to request specific edits — e.g. "Rewrite the short description to be more specific" or "Add a FAQ about data storage". Once you're happy, click Approve Readme.

In the Submission Center, click Download Submission Package. This is a WP.org-ready ZIP — the same files as your plugin ZIP but reorganised for SVN trunk:

• your-plugin-slug/
•   your-plugin-slug.php (bootstrap)
•   readme.txt
•   includes/ …
•   uninstall.php

Separately, download the Store Listing Assets ZIP. This contains your banner images (772×250 and 1544×500), icons (128×128 and 256×256), and screenshot placeholder PNGs. These go into the assets/ folder in SVN — NOT in trunk.

Go to wordpress.org/plugins/add/ and upload your plugin ZIP (not the assets ZIP). Fill in the form with your plugin name and a short summary. Click submit.

WordPress.org will run automated checks first. If those pass, a human reviewer will look at your plugin — this typically takes 5–14 business days for a first review.

Once approved, WordPress.org will email you your SVN repository URL. The built-in SVN Walkthrough in the Submission Center gives you the exact commands to:

1. Check out your SVN repository
2. Copy your submission package files into trunk/
3. Copy your assets into assets/ (at the root, not in trunk)
4. Set the correct SVN properties on banner and icon files
5. Tag the release: copy trunk to tags/1.0.0/
6. Commit everything

Each step has a copy button so you can paste commands directly into your terminal.

Reviewers sometimes ask for changes before approving. Paste the reviewer's email into the Rejection Recovery panel in the Submission Center. The AI will:

• Extract each issue from the email with the exact quoted line
• Suggest the specific code change needed for each issue
• Draft a polite reply email for you to send back

Apply the suggested fixes manually, then rebuild or patch the files. Once you've fixed everything, reply to the reviewer's email (don't open a new ticket).