Devenia WordPress plugin guide
The WordPress.org Plugin Review Process: A Comedy in Three Acts
A practical, lightly satirical guide to the WordPress.org plugin review process: queues, slug changes, Plugin Check, long emails, and what actually helps before approval.
WordPress.org plugin review is slower than it looks
So you built a WordPress plugin. Congratulations. Now you want to share it with the world through WordPress.org.
How hard can it be? Upload a zip file, wait a bit, done. Right? Not quite.
Reader decision
- Have you run Plugin Check before submitting?
- Do the plugin name, slug, folder, main file, and text domain match?
- Are you ready to read the whole review email and wait through the queue?
The comedy in three acts
The process usually feels simple before you submit, confusing while you wait, and obvious only after you have been through it once.
Act 1: The submission
You zip up the plugin, test it, submit it, and wait. Then you learn the current queue may be four to six weeks.
Act 2: The feedback loop
An email arrives with issues. You fix the name, slug, or text domain, upload again, then discover another mismatch or a changed expectation.
Act 3: The existential questions
What you expected was upload, review, approved or rejected, done. What happens can feel like wait, fix A, wait, fix B, then find A is wrong again.
The plot twists
The review emails can be a mix of automated messages, AI-generated suggestions, actual human feedback, other conversations, and documentation links.
They can also be thousands of words long, with nested quotes going back through the whole thread. The important bit may be buried deep in the email.
Common surprises
- The slug dance: display name, slug, text domain, folder name, and main file name all need to line up.
- The reply paradox: do not reply unless you have a question, but also reply after fixing issues, but also maybe just upload.
- The generic name trap: descriptive plugin names can be too generic for WordPress.org.
- Plugin Check may expect one slug while the review thread points you toward another.
- A 52-email thread can hide the actual change that matters.
What actually helps
Despite the chaos, the useful lessons are practical and repeatable.
- Run Plugin Check early: Run the Plugin Check plugin before submitting. It catches many issues upfront and can save weeks.
- Pick a unique name: Choose a branded name from the start, such as YourBrand Thing rather than a generic function name.
- Keep identifiers matching: Folder name, main file name, slug, and text domain should all match. Do not get creative.
- Read the whole email: The important instruction may be buried after automated text, AI suggestions, or quoted thread history.
- Expect iteration: You may change plugin name, slug, text domain, folder, or file names more than once.
Treat review feedback as a process to work through, not as a single pass/fail event.
Why the process exists
The WordPress.org plugin review team are volunteers. Real humans give their free time to check thousands of plugins.
What feels frustrating
- The wait can be four to six weeks or longer.
- The emails can be long, confusing, and sometimes contradictory.
- A plugin that felt done at version 1.0 may need several review-specific updates.
What the review protects
- Every plugin on WordPress.org could theoretically run on many websites.
- One bad plugin can create a serious security or stability problem for site owners.
- The process is trying to keep WordPress safer, even when the workflow is confusing.
Submission checklist
Before submitting, check the small details that create the most back-and-forth.
- Plugin Check passes locally.
- Plugin name is unique and branded enough.
- Slug, folder, main file, and text domain match.
- The review email has been read all the way through.
- Documentation links and human feedback have been separated from automated noise.
- If the review team changes the slug, re-check every identifier that depends on it.
Preparation does not remove the queue, but it reduces avoidable review loops.
Frequently asked questions
How long does WordPress.org plugin review take?
The queue can take four to six weeks or more, depending on current workload and follow-up issues.
What causes repeated review loops?
Common causes include generic plugin names, slug changes, mismatched text domains, folder names, main file names, and missed instructions in long emails.
What should plugin developers do before submitting?
Run Plugin Check, choose a unique branded name, keep slug/folder/main file/text domain aligned, and read every review email carefully.
The TL;DR
The process can be confusing, but it eventually ends.
- Expect WordPress.org plugin review to take weeks.
- Expect name, slug, and text-domain changes.
- Run Plugin Check before submitting.
- Remember the reviewers are volunteers doing important work.
Good luck out there. You will probably get approved eventually, then immediately start building the next plugin.