AumCreate

Data

Installs per review on WordPress.org

Between 26 and 4,583 — a spread of two orders of magnitude across 14 plugins, measured on .

Whether any of these plugins prompts for a review was not observed. The table measures the size of the difference, not its cause.

AumCreate publishes free plugins on wordpress.org, and some of them appear in this table.

The numbers

Every figure comes from one call, and the slug in the last column is the one that call needs — not the plugin’s common name. Read the ratio as an order of magnitude; active_installs is rounded down to a bucket (10, 70,000, 900,000 …) and reflects sites active now, while num_ratings is cumulative since the plugin was published. Read the ratio as an order of magnitude, never as a conversion rate.

PluginActive installsRatingsInstalls per review5★ / 1★API slug
Weglot50,0001,9382693% / 4%weglot
Tidio70,00039517792% / 4%tidio-live-chat
GTranslate900,0004,96118194% / 2%gtranslate
TranslatePress400,0001,66224190% / 5%translatepress-multilingual
Polylang900,0002,99830089% / 5%polylang
The SEO Framework200,00037952895% / 1%autodescription
WP Super Cache1,000,0001,34674374% / 13%wp-super-cache
WP Mail SMTP4,000,0005,20576894% / 3%wp-mail-smtp
Wordfence Security5,000,0005,02499590% / 5%wordfence
Kadence Blocks600,0003321,80792% / 2%kadence-blocks
Loco Translate1,000,0004532,20894% / 4%loco-translate
Redirection2,000,0007032,84579% / 10%redirection
Blocksy Companion300,000933,22691% / 3%blocksy-companion
Contact Form 710,000,0002,1824,58368% / 19%contact-form-7

A rating is a forum post

There is no star-only rating on WordPress.org. Every rating is a topic in the plugin’s support forum, with a title and a body. The topics were counted and compared with what the API reports:

  • blocksy-companion — API 93, topics counted 93
  • autodescription — API 379, topics counted 379
  • kadence-blocks — API 332, topics counted 333 (one apart, most likely a sticky topic or a post added between the two reads)
  • tidio-live-chat — API 395, topics counted 396 (one apart, most likely a sticky topic or a post added between the two reads)

Which also means a review takes an account, and a few minutes of someone’s writing — not a tap.

Limits of this method

Two limits, both of which you can reproduce. They are the reason to trust the rest of the table, not a disclaimer at the bottom of it.

The reviews list has a page cap

The reviews list stops at page 49. Contact Form 7 and Weglot — two plugins an order of magnitude apart — both come out at exactly 49 × 30 = 1,470. An identical number from two different-sized plugins is the page cap, not the real last page. So any plugin with more than 1,470 ratings cannot be counted this way, and is listed without a count.

The ratio drifts on its own

num_ratings only ever goes up; active_installs can fall. So the installs-per-review figure drifts upward over time on its own. If you re-run these calls next month and get a larger number, that is the metric moving, not an error in the table.

Reproduce it

One call per plugin, no key, no parameters beyond the slug:

https://api.wordpress.org/plugins/info/1.2/?action=plugin_information&request[slug]=contact-form-7

The square brackets in request[slug] are a wildcard to curl, so pasting this straight into a terminal fails before it sends anything. Add -g (curl -g '…') or escape them. In a browser it works as-is.

The fields used here are active_installs, num_ratings, rating and the ratings buckets. Topic counts come from the reviews list, 30 topics a page.

Sources

All figures checked on .