wordpress-org-compliance

WordPress.org freemium compliance requires that all free features work without a license key, upsells are non-intrusive, and premium functionality is offered as separate add-ons rather than locked within the free version. Use a compliance checklist to review your plugin's free vs. premium distinctions and replace any license-locked features with feature detection or add-on patterns before submission.

Compliant upselling uses informational teasers and non-intrusive upgrade notes without blocking functionality. Non-compliant approaches include trial limits, quota restrictions, feature gates requiring license keys, or intrusive upgrade prompts. WordPress.org requires separate premium plugins for additional features, never locked code or trialware within the free version.

No. WordPress.org compliance prohibits trials, quotas, and feature restrictions in free versions. All free features must be fully functional without a license key. Premium functionality should be offered as separate add-on plugins with clear, non-intrusive upsell messaging only.

Structure premium features as separate paid add-on plugins rather than gating them with license checks in the free version. Use informational teasers to guide users toward premium offerings without blocking access to free functionality. This pattern keeps the free plugin compliant while maintaining a clear upgrade path.

Before submission, verify that your plugin has no premium locking, no license key requirements for free features, no trials or quotas, and uses only non-intrusive upsell messaging. Use the compliance checklist to review free vs. premium distinctions, code patterns, and upgrade UI. Address any violations to avoid rejection.