Stores & marketplaces

WordPress plugin directory

Huge install base. A free plugin can lead to a paid version.

Visit wordpress.org
Cost
Free

Free to publish. Check current guidelines.

Verdict
works

Works: a large install base, and free plugins can lead to paid versions.

Difficulty
Medium

Needs preparation, a review, or a steady habit before results.

Effort
Medium

About 5 to 10 hours a month.

First result
1 to 2 weeks

A rough range for one person working on it part-time.

Payoff
Compounds

keeps growing while you keep at it.

Best for

Plugins for WordPress sites.

Not for

Products that do not run on WordPress.

Pros

  • Huge install base
  • Free plugin can lead to paid

Cons

  • Support load from many users
  • Crowded categories

The full guide

Last verified 2026-10-30

Links checked 2026-10-30 · All links answer

01What it is and who is there

The WordPress.org plugin directory hosts free plugins for WordPress sites. Site owners search it from their dashboard, so a useful plugin can reach many installs. Many businesses offer a free plugin there and sell a paid version or service elsewhere. Every plugin is reviewed against WordPress guidelines.

02Cost and what you actually pay for

Hosting a plugin in the directory is free. Plugins in the directory must be GPL-compatible. Your main cost is support: many users means many questions.

03Is it right for you?

It fits plugins that add a feature to WordPress sites, and products that can offer a free version. It fits poorly for products that do not run on WordPress. If you cannot support free users, think twice.

04Before you start

  • Read the WordPress plugin guidelines, including the licensing and "no tracking without consent" rules.
  • A working plugin tested on a current WordPress version.
  • A readme.txt in the required format, with a clear description.

05Step-by-step: how to distribute here

  1. Build and test the plugin.
  2. Submit it for review and respond to the review team.
  3. Once approved, upload through the plugin repository.
  4. Write a readme that names the problem and lists features.
  5. Answer support forum threads quickly.
  6. If you sell a pro version, follow the guidelines on upselling.

06What to post or submit

Short description:

[Plugin] [does job] for WordPress sites. [Key benefit]. No coding needed.

07Common mistakes and do-nots

  • Do not track users without consent; the guidelines forbid it.
  • Do not use a non-GPL-compatible license.
  • Do not ignore support threads.
  • Do not spam admin dashboards with upsells.

08How to measure it

  • Track active installs and ratings on the plugin page.
  • Track upgrades to paid.
  • A realistic test: three months.

09Time budget

  • Before: 10 to 40 hours.
  • Ongoing: 2 to 6 hours a month on support.

10Pair it with

11Sources

Sources