WordPress.org Plugin Directory Guidelines
Latest commit 5ddb8df Nov 3, 2016 @Ipstenu committed on GitHub Merge pull request #55 from Joel-James/patch-1
"An Checkbox" >> "A Checkbox"

Grammer! It's not just for lunch!
Failed to load latest commit information.
.gitignore Initial commit Jul 29, 2016
LICENSE Initial commit Jul 29, 2016
README.md WE’RE LIVE! Oct 27, 2016
guideline-01.md GPL G1 and G2 Take 2 Sep 4, 2016
guideline-03.md Mergeing Pull Req from Scott: change repo to dir Aug 24, 2016
guideline-04.md Link to Core Coding Standards Sep 1, 2016
guideline-05.md Fixing Inconsistent List Styles Sep 1, 2016
guideline-06.md Minor Text Fixes Oct 20, 2016
guideline-07.md "An Checkbox" -> "A Checkbox" Nov 2, 2016
guideline-08.md Minor fixes: Aug 24, 2016
guideline-09.md Minor Text Changes Sep 3, 2016
guideline-10.md Clarifying with don't hide your opt-in - props @hlashbrooke Sep 8, 2016
guideline-11.md Clarify that alerts can self-dismiss Sep 1, 2016
guideline-12.md Additional Information re links Sep 1, 2016
guideline-14.md Rephrase Frequent Commits Sep 1, 2016
guideline-15.md Removed redundant reminder. Sep 7, 2016
guideline-16.md Removed Statement on Trademark Aug 24, 2016
guideline-17.md Minor Text Changes Sep 2, 2016
guideline-18.md s/anytime/any time/ Aug 31, 2016
introduction.md Minor Text Fixes Oct 20, 2016


WordPress Plugin Directory Guidelines

This is the online repository for the rewrite of the WordPress.org Plugin Guidelines.

As of October 20, 2016, these guidelines match the ones on WordPress.org.


In 2016, an attempt was begun to clean up the Detailed Plugin Guidelines and make them easier to understand, while retaining the heart of their intent. While one might wish we could say "Don't be a gosh darn bad person or spammer!" the reality is that some people need things spelled out. But also a great many situations are difficult to summarize.

The Plugin Review Team made the first pass, followed by many volunteers at WordCamps around the world, and finally a public posting here for anyone in the community. The guidelines went live on October 20, 2016, and this repository remains open for the time being to allow any late changes to be tracked.


If you feel a guideline’s explanation is unclear, please create an issue or a pull request with what you feel should be changed and why. All grammar/spelling corrections are greatly welcome. We’re trying to write these for all levels of developers, as well as people who may not speak English proficiently. Using words like ‘obsequious’ should be avoided (nb: That’s mostly to Mika who uses those words regularly).

All feedback should be opened as issues in the tracker.

Table of Contents


  1. Plugins must be compatible with the GNU General Public License v2, or any later version.
  2. Plugin developers are responsible for the files they upload and services they utilize.
  3. A stable version of your plugin must be available from its WordPress Plugin Directory page.
  4. Keep your code (mostly) human readable.
  5. Trialware is not allowed in the directory.
  6. Software as a Service is permitted in the directory.
  7. The plugin may not “phone home” or track users without their informed, explicit, opt-in consent.
  8. The plugin may not send executable code via third-party systems.
  9. The plugin and its developers must not do anything illegal, dishonest, or morally offensive.
  10. The plugin must not embed external links or credits on the public site without explicitly asking the user’s permission.
  11. The plugin should not hijack the blog admin.
  12. Public facing pages on WordPress.org may not contain “sponsored” or “affiliate” links or third party advertisements.
  13. The plugin page in the directory should include no more than 12 tags.
  14. Frequent commits can be seen as gaming the Recently Updated lists.
  15. The plugin version number must increment every time a new version is released.
  16. A complete plugin must be available at the time of submitting the plugin request to the directory.
  17. Respect trademarks.
  18. We reserve the right to alter the Plugin Guidelines at any time with or without notice.


The content has two licenses:

Just like WordPress, you are free to read, share, distribute, and modify the content however you want, passing on those freedoms to everyone else. Cool!