Overview
Authoritative reference for the 18 WordPress.org Plugin Directory guidelines. Covers GPL licensing, plugin naming/trademark rules, trialware restrictions, and all other submission requirements.
When to use
Use this skill when you need to:
- Review a WordPress plugin for compliance with the WordPress.org Plugin Directory guidelines
- Check GPL license compatibility for a plugin or its bundled libraries
- Verify license headers in plugin files
- Identify common guideline violations before submission
- Answer questions about what is or is not allowed on WordPress.org
- Evaluate premium/upsell flows, license checks, or freemium positioning
- Review "teaser" or "preview" UI for trialware violations
Inputs required
- Plugin source code (or specific files to review)
- Optional: plugin readme and plugin header metadata for naming and license checks
Procedure
- Check the plugin's license header against the Valid License Headers section below.
- Walk through the 18 Guidelines checklist, paying special attention to Guidelines 1, 4, 5, 7, 8, and 17.
- Confirm trialware/freemium compliance using the checklist in guideline-review-checklist.md (Guideline 5 section).
- For bundled third-party code, verify license compatibility against GPL-Compatible Licenses (Quick) below.
- Flag matches from Common GPL Violations (Quick) below.
- For edge cases, consult the detailed references and the GNU GPL FAQ.
18-Guideline Review Checklist
Use the detailed, per-guideline checklist in guideline-review-checklist.md. Load this reference file only when a full guideline audit is requested.
GPL Compliance (Guideline 1 in Detail)
Use gpl-compliance.md for full license tables, compatibility nuances, and examples. Keep this inline section as a quick decision aid.
Verification (Licensing)
- Every licensing-related issue must cite Guideline 1 and include the file path and exact license string.
- Confirm compatibility claims against GPL-Compatible Licenses (Quick) and escalate ambiguous licenses.
Failure modes (Licensing)
- If a license is not clearly GPL-compatible, do not guess. Check the GNU license list.
- For dual-license packages, verify both licenses and redistribution terms.
Quick Reference: WordPress GPL Requirements
- WordPress is GPLv2 or later.
- Plugins distributed on WordPress.org must be 100% GPL-compatible (code and assets).
- Include a valid
License: header and License URI: in the main plugin file.
- Do not add restrictions that conflict with GPL freedoms.
Valid License Headers
GPL Versions Summary
| Version |
Year |
Key Addition |
| GPLv1 |
1989 |
Base copyleft: share-alike for modifications |
| GPLv2 |
1991 |
"Liberty or death" clause (Section 7), clearer distribution terms |
| GPLv3 |
2007 |
Anti-tivoization, explicit patent grants, compatibility provisions |
WordPress uses GPLv2 or later, meaning plugins can use GPLv2, GPLv3, or "GPLv2 or later".
For full license texts, see:
License Compliance Checklist
When reviewing a plugin, verify:
Valid License Headers for WordPress Plugins
License: GPL-2.0-or-later
License URI: https://www.gnu.org/licenses/gpl-2.0.html
License: GPL-3.0-or-later
License URI: https://www.gnu.org/licenses/gpl-3.0.html
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html
GPL-Compatible Licenses (Quick)
- Safe defaults: GPL-2.0-or-later, GPL-3.0-or-later.
- Commonly accepted permissive families: MIT/Expat, BSD, ISC, zlib, Boost.
- Conditional compatibility requires care: Apache-2.0 and MPL-2.0 (verify usage context).
- For full accepted and rejected identifiers, use gpl-compliance.md.
Common GPL Violations (Quick)
- Split licensing that restricts distributed code.
- Obfuscated or non-corresponding source distribution.
- Restrictive clauses (non-commercial, no-resale, forced backlink).
- Bundling GPL-incompatible libraries or assets.
Plugin Naming Rules (Guideline 17)
Use naming-rules.md for full trademark lists, slug blocks, and naming examples. Keep this inline checklist for quick screening.
Naming Checklist (Quick)
- Name is not a placeholder and has at least 5 alphanumeric characters.
- Header name and readme name match.
- Name is specific and function-related; avoid keyword stuffing.
- Trademark/project names appear only after connectors like
for, with, using, and.
- No banned/discouraged terms or trademark portmanteaus.
- Slug is lowercase, hyphenated, <= 50 chars, and avoids blocked terms.
1---
2name: wp-plugin-directory-guidelines
3description: "Use when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell/freemium/trialware patterns, validating plugin naming or trademark rules, checking plugin slugs, understanding why a plugin was rejected from WordPress.org, or answering any question about the 18 WordPress.org Plugin Directory guidelines — even if the user doesn't mention 'guidelines' explicitly."
4compatibility: "Targets WordPress 7.0+ (PHP 7.4.0+)."
5metadata:
6 source: https://skillmd.com/skills/gabrielmoreira/wp-plugin-directory-guidelines
7---
8
9## Overview
10
11Authoritative reference for the 18 WordPress.org Plugin Directory guidelines. Covers GPL licensing, plugin naming/trademark rules, trialware restrictions, and all other submission requirements.
12
13## When to use
14
15Use this skill when you need to:
16- Review a WordPress plugin for compliance with the WordPress.org Plugin Directory guidelines
17- Check GPL license compatibility for a plugin or its bundled libraries
18- Verify license headers in plugin files
19- Identify common guideline violations before submission
20- Answer questions about what is or is not allowed on WordPress.org
21- Evaluate premium/upsell flows, license checks, or freemium positioning
22- Review "teaser" or "preview" UI for trialware violations
23
24## Inputs required
25
26- Plugin source code (or specific files to review)
27- Optional: plugin readme and plugin header metadata for naming and license checks
28
29## Procedure
30
311. Check the plugin's license header against the **Valid License Headers** section below.
322. Walk through the **18 Guidelines** checklist, paying special attention to Guidelines 1, 4, 5, 7, 8, and 17.
333. Confirm trialware/freemium compliance using the checklist in [guideline-review-checklist.md](references/guideline-review-checklist.md) (Guideline 5 section).
344. For bundled third-party code, verify license compatibility against **GPL-Compatible Licenses (Quick)** below.
355. Flag matches from **Common GPL Violations (Quick)** below.
366. For edge cases, consult the detailed references and the [GNU GPL FAQ](https://www.gnu.org/licenses/gpl-faq.html).
37
38## 18-Guideline Review Checklist
39
40Use the detailed, per-guideline checklist in [guideline-review-checklist.md](references/guideline-review-checklist.md). Load this reference file only when a full guideline audit is requested.
41
42## GPL Compliance (Guideline 1 in Detail)
43
44Use [gpl-compliance.md](references/gpl-compliance.md) for full license tables, compatibility nuances, and examples. Keep this inline section as a quick decision aid.
45
46### Verification (Licensing)
47
48- Every licensing-related issue must cite **Guideline 1** and include the file path and exact license string.
49- Confirm compatibility claims against **GPL-Compatible Licenses (Quick)** and escalate ambiguous licenses.
50
51### Failure modes (Licensing)
52
53- If a license is not clearly GPL-compatible, do not guess. Check the [GNU license list](https://www.gnu.org/licenses/license-list.html).
54- For dual-license packages, verify both licenses and redistribution terms.
55
56### Quick Reference: WordPress GPL Requirements
57
58- WordPress is **GPLv2 or later**.
59- Plugins distributed on WordPress.org must be 100% GPL-compatible (code and assets).
60- Include a valid `License:` header and `License URI:` in the main plugin file.
61- Do not add restrictions that conflict with GPL freedoms.
62
63### Valid License Headers
64
65## GPL Versions Summary
66
67| Version | Year | Key Addition |
68|---------|------|--------------|
69| GPLv1 | 1989 | Base copyleft: share-alike for modifications |
70| GPLv2 | 1991 | "Liberty or death" clause (Section 7), clearer distribution terms |
71| GPLv3 | 2007 | Anti-tivoization, explicit patent grants, compatibility provisions |
72
73WordPress uses **GPLv2 or later**, meaning plugins can use GPLv2, GPLv3, or "GPLv2 or later".
74
75For full license texts, see:
76- [GNU General Public License v1](https://www.gnu.org/licenses/gpl-1.0.html)
77- [GNU General Public License v2](https://www.gnu.org/licenses/gpl-2.0.html)
78- [GNU General Public License v3](https://www.gnu.org/licenses/gpl-3.0.html)
79
80## License Compliance Checklist
81
82When reviewing a plugin, verify:
83
84- [ ] Main plugin file has a valid `License:` header (e.g., `GPL-2.0-or-later`, `GPL-2.0+`, `GPLv2 or later`)
85- [ ] Main plugin file has a `License URI:` header pointing to the GPL text
86- [ ] If bundled libraries exist, each has a GPL-compatible license
87- [ ] No "split licensing" (e.g., code GPL but premium features proprietary)
88- [ ] No additional restrictions beyond what GPL allows
89- [ ] No clauses restricting commercial use, modification, or redistribution
90- [ ] No obfuscated code (violates the spirit of source code availability)
91
92## Valid License Headers for WordPress Plugins
93
94```
95License: GPL-2.0-or-later
96License URI: https://www.gnu.org/licenses/gpl-2.0.html
97```
98
99```text
100License: GPL-3.0-or-later
101License URI: https://www.gnu.org/licenses/gpl-3.0.html
102```
103
104```text
105License: GPLv2 or later
106License URI: https://www.gnu.org/licenses/gpl-2.0.html
107```
108
109### GPL-Compatible Licenses (Quick)
110
111- Safe defaults: GPL-2.0-or-later, GPL-3.0-or-later.
112- Commonly accepted permissive families: MIT/Expat, BSD, ISC, zlib, Boost.
113- Conditional compatibility requires care: Apache-2.0 and MPL-2.0 (verify usage context).
114- For full accepted and rejected identifiers, use [gpl-compliance.md](references/gpl-compliance.md).
115
116### Common GPL Violations (Quick)
117
118- Split licensing that restricts distributed code.
119- Obfuscated or non-corresponding source distribution.
120- Restrictive clauses (non-commercial, no-resale, forced backlink).
121- Bundling GPL-incompatible libraries or assets.
122
123## Plugin Naming Rules (Guideline 17)
124
125Use [naming-rules.md](references/naming-rules.md) for full trademark lists, slug blocks, and naming examples. Keep this inline checklist for quick screening.
126
127### Naming Checklist (Quick)
128
129- Name is not a placeholder and has at least 5 alphanumeric characters.
130- Header name and readme name match.
131- Name is specific and function-related; avoid keyword stuffing.
132- Trademark/project names appear only after connectors like `for`, `with`, `using`, `and`.
133- No banned/discouraged terms or trademark portmanteaus.
134- Slug is lowercase, hyphenated, <= 50 chars, and avoids blocked terms.