WordPress.org directory
Historification
Our own WordPress plugin — taken through the directory's notoriously strict review, security checks and guidelines, and kept compliant.
Visit historification.net →WordPress.org has one of the strictest reviews in software — mostly about security. We fix the exact issues reviewers flag, make your plugin pass the official Plugin Check, and work the reviewer thread until you're listed. We took our own plugin through this same review.
The directory's review is mostly a security audit. If your feedback mentions any of these, we've handled it before.
User input used without cleaning it first. We sanitize every input the WordPress way, everywhere it enters your code.
Data printed to the page without escaping — a top rejection reason. We escape all output to the correct context.
Actions without CSRF protection or permission checks. We add nonce verification and capability checks to every handler.
Generic function, option and table names collide with other plugins. We prefix everything uniquely to your plugin.
Loading scripts or data from outside servers. We bundle assets locally and use the WordPress HTTP API where calls are needed.
Locked features, upsell nags and "powered by" spam get rejected. We bring the plugin in line with the guidelines.
Send the reviewer's email. We map every point to a concrete code fix.
Sanitize, escape, add nonces, prefix, remove external calls — until it's clean.
We run the official Plugin Check to zero errors before we reply.
We answer the reviewer on the same ticket until your plugin is approved and listed.
We didn't just read the guidelines — we took our own plugin through the directory's full security and guideline review.
Our own WordPress plugin — taken through the directory's notoriously strict review, security checks and guidelines, and kept compliant.
Visit historification.net →Almost always security and guidelines: missing sanitization, unescaped output, missing nonce/capability checks, non-prefixed names, external calls, or bundled trialware and nag screens. Fix those and it passes.
Yes. We harden it to the guidelines, make it pass the official Plugin Check with zero errors, and reply on the reviewer thread until it's approved and listed.
Anywhere from a few days to several weeks depending on the queue, and every feedback round adds time. Getting it right the first pass is the fastest route — that's what we optimise for.
No one can guarantee a reviewer's call, but we remove the reasons plugins get rejected and manage the conversation. We took our own plugin through this exact review.
Paste what WordPress.org told you. We'll tell you exactly what needs fixing and how fast we can get you listed. First reply is from a human, usually within a day.
Fix my rejectionAlso rejected elsewhere? Chrome extension · Google Play app.