Why the Gap Between 100 and 1,000 Installs Matters More Than You Think

A plugin at 100 active installs and a plugin at 1,000 active installs are not ten times different in visibility on WordPress.org. They’re worlds apart.

That’s not intuitive, but it’s how the algorithm works — and understanding why changes everything about how you should be thinking about early plugin growth. Most developers treat their install count as a vanity metric, something to watch passively while they focus on building features. The reality is that the install count is the most consequential number in your plugin’s early life, and the window between 100 and 1,000 is where that number has the highest leverage.

How the WordPress.org Algorithm Actually Scores Installs

WordPress.org published its plugin search ranking formula, and it contains a detail most plugin developers have never noticed. The formula for a plugin’s search ranking score is:

The active installs component uses log₂ — logarithm base 2. This is the detail that matters. Logarithmic scaling means that each successive doubling of your install count produces the same fixed increment in your ranking score, regardless of where you are on the curve. Going from 100 to 200 installs produces the same logarithmic increment as going from 10,000 to 20,000 installs. But getting from 100 to 200 installs takes far less absolute effort than getting from 10,000 to 20,000.

Put another way: in absolute terms, the first 1,000 installs improve your ranking score more per install than any subsequent 1,000. The curve is steepest at the bottom. This is not a reason to despair — it’s a reason to understand that the 100-to-1,000 gap is where your optimization effort has maximum impact, and to pursue it aggressively.

Each row in that table represents the same ranking improvement from the active installs component. Getting from 100 to 1,000 installs is exactly as valuable algorithmically as getting from 1,000 to 10,000 — but it requires roughly one-ninth the installs. That asymmetry is the entire argument for treating the 100-to-1,000 gap as a first-priority growth objective.

Why 100 Installs Keeps You Invisible

WordPress.org processes over 100,000 plugin searches every day. The plugins that appear in those search results capture the lion’s share of organic installs. Plugins that don’t appear in results get none.

At 100 installs, most plugins are invisible to most searches in their category — not because their readme is wrong or their product is weak, but because the install count component of the ranking formula is still too low to overcome the accumulated advantage of plugins that have been in the directory for years. A competitor with 5,000 installs and a mediocre readme will outrank you on install count alone until you close the gap.

There’s a secondary effect that compounds this. Plugins with zero reviews are assigned a default rating of 2.5 stars by the algorithm — not a neutral rating, not a blank, but an actual 2.5-star score that actively penalizes them in the √(rating) component of the formula. A plugin with five genuine 5-star reviews and a plugin with zero reviews are not equally ranked. The reviewed plugin scores √5 = 2.24 on that component. The unreviewed plugin scores √2.5 = 1.58. That’s a 42% difference in the rating component from just five reviews.

The Flywheel That Starts at 1,000

The difference between 100 installs and 1,000 installs isn’t just a number. It’s the difference between a plugin that’s stuck and a plugin that’s moving.

At 1,000 installs, several things change simultaneously. Your ranking score has improved enough to appear on page one or two for at least some relevant searches in your category. That visibility produces new organic installs from users who found you through WordPress.org search — installs you didn’t generate through any active effort. Those installs produce support threads. Support threads, when resolved promptly, improve your log₂(support_threads_resolved) score. Resolved threads also produce the user relationships most likely to result in reviews. Reviews improve your √(rating) score. The improved scores produce better rankings. Better rankings produce more installs.

This is the flywheel. It doesn’t operate meaningfully at 100 installs — the visibility just isn’t there yet. At 1,000 installs it begins. At 5,000 it accelerates noticeably. By 10,000, it’s largely self-sustaining.

The practical implication: virtually all of your early growth effort should be focused on closing the gap to 1,000 installs as quickly as possible. Adding features, refining UX, building a marketing presence — all of that has greater ROI once the flywheel is running. Before 1,000 installs, the algorithm is working against you. After 1,000, it starts working with you.

What You Can Actually Control

The install count itself is an output — you can’t set it directly. But the inputs that produce installs are largely within your control, and the algorithm signals you can improve immediately are well-documented.

1. 1

   Readme optimization — the fastest-moving lever. The text_relevance component of the ranking formula determines whether your plugin appears in searches at all. A plugin that doesn’t appear in search results can’t accumulate installs regardless of install count. Get your title, short description, and long description optimized for the exact phrases your users search before doing anything else. Understanding how the WordPress.org algorithm works and which fields it actually indexes is the prerequisite for any effective readme optimization.

2. 2

   Competitor keyword gap analysis. Before rewriting your readme, find out which keywords your competitors rank for that you don’t. Those gaps represent searches where you could be appearing but aren’t. Mapping your competitors’ keyword strategy before you optimize ensures you’re targeting the right phrases rather than guessing. WhoKnew Directory SEO™ automates this — surfacing every term your competitors rank for that your plugin doesn’t, scored by relevance and gap size.

3. 3

   Get one genuine review, immediately. Contact every person who has installed your plugin — beta testers, early adopters, colleagues who tried it — and ask for an honest review. One review moves you off the 2.5-star default and changes your rating component the same day. The ask doesn’t have to be elaborate: “Would you mind leaving an honest review on WordPress.org? Even a short one helps.”

4. 4

   Resolve every support thread. The log₂(support_threads_resolved) component rewards resolution rate, not just reply rate. Many developers reply to threads but don’t mark them resolved — those threads still count against you. Go through every open thread and close it. Respond to any new thread within 48 hours and resolve it once answered. Support users are the most likely people to leave reviews — treat every thread as a review opportunity.

5. 5

   Keep “Tested up to” current. The compatibility_decay component penalizes plugins that haven’t been tested against recent WordPress versions. Update your readme’s “Tested up to” field to reflect the current WordPress version after every release. This is a five-second change that eliminates an unnecessary ranking penalty.

6. 6

   Track your positions after changes. WordPress.org doesn’t surface keyword ranking data to developers. Without tracking, you can’t tell whether your readme changes are working or which keywords are moving. WhoKnew Directory SEO™ tracks your live positions on WordPress.org for every keyword you care about — so you can see movement within days of making readme changes rather than wondering whether anything happened.

Who knew the gap between 100 installs and 1,000 installs was worth more algorithmically than the gap between 1,000 and 10,000 — and that most developers spend their energy chasing the wrong end of the curve.