How to Rank a New Plugin With Zero Installs

The email arrives, the plugin is approved, and the first thing almost every developer does is search WordPress.org for their own plugin name. It’s not there — or it’s there, buried on page six behind plugins that haven’t shipped an update since 2023. Zero installs. Zero reviews. No support threads, no social proof, nothing for a visitor to judge except a readme file and a promise. This is the exact moment that decides whether a plugin spends its first year invisible or its first month climbing.

The good news is narrower than most advice makes it sound, but it’s real: a brand-new plugin isn’t actually starting from zero on every axis. One part of WordPress.org’s ranking system doesn’t care how many installs you have at all — and that’s the part worth focusing every hour of the first week on.

The Two-Phase Problem You’re Actually Solving

WordPress.org’s plugin search runs on a two-phase Elasticsearch process. Phase one matches keywords across a specific set of fields in your readme — if your target term isn’t present in those fields, your plugin is excluded from the results entirely, full stop, regardless of how good the plugin itself is. Phase two only runs against whatever survived phase one: it re-ranks that smaller pool using active installs, average rating, resolved support ticket percentage, and how recently the plugin was updated.

That order matters enormously for a plugin with nothing yet. Phase two is the phase a zero-install plugin structurally loses, at least for now — there’s no install count to weight, no rating to boost you, no support history to point to. But phase one doesn’t ask any of those questions. It asks one thing: does the keyword appear in the right fields? A plugin with 40,000 installs and a keyword missing from its tags loses that specific search to a brand-new plugin that has the keyword sitting in all seven fields. Visibility and reputation are two different games, and only one of them is available to play on day one.

Why This Is the Only Fight You Can Win Immediately

The same split shows up in a much bigger, better-documented marketplace: mobile app stores. Apple and Google both run ranking systems that weight recency and momentum heavily — a newer app with genuine current activity can outrank an older one that’s coasting on stale downloads, because both stores have learned that lifetime totals are a worse signal of relevance than what’s happening right now. And search dominates discovery in that world too: roughly 65% of App Store downloads start with a keyword search rather than browsing, which means metadata — not popularity — decides who even shows up to be judged. WordPress.org runs on the same basic logic: metadata gets you found, reputation gets you ranked once you’re there, and a new plugin only gets to compete on the first one.

The 7 Fields, and What Each One Is Actually Worth

WordPress.org indexes exactly seven fields from a plugin’s readme: name, slug, tags, short description, description, author, and contributors. They aren’t weighted equally, and knowing the order changes where the first hour of readme-writing should go.

Most plugin developers write a name, skip the short description or leave it generic, and never think about tags again after submission. That’s the 2-to-3-field coverage that’s standard across the directory. A plugin that deliberately fills all 7 fields with the right keyword — including contributors and author, which are easy to overlook entirely — is doing something most of its established competition genuinely isn’t, regardless of how many installs either one has.

Picking Keywords You Can Actually Win at Zero Installs

The instinct for a new plugin is to target the biggest, most obvious term in its category — “contact form,” “SEO plugin,” whatever the head term is. That’s the exact keyword a plugin with 40,000 installs and a five-year update history already owns, and phase two of the algorithm will keep it there regardless of how well a brand-new readme is written. App store optimization research makes the same point from the mobile side: a common mistake is optimizing for keywords that are out of reach, when a benchmark check against the terms’ current leaders would show the gap is too wide to close quickly. The fix is the same in both marketplaces — go narrower before going bigger.

A specific, lower-competition long-tail phrase — the kind with real search intent behind it but far fewer plugins actively targeting it — is winnable on day one, because phase one doesn’t discriminate by install count and phase two has a much smaller, weaker pool to compete against on an uncrowded term. Once a plugin has actual traction on a handful of long-tail phrases, that’s when a head term with real competition behind it becomes worth spending effort on — not before.

Checking Whether a Keyword Is Actually Worth Chasing

Choosing a long-tail phrase because it feels less crowded is a reasonable starting instinct, but “less crowded” and “actually searched for” aren’t the same thing — a term nobody targets because nobody searches it doesn’t help a plugin either. A keyword worth building a readme around needs real search interest behind it, not just low competition. Interest scoring tools that rate a keyword’s search popularity on a simple scale solve this specific problem: a phrase scoring 80+ with only a handful of plugins targeting it is a genuinely good bet, while a phrase scoring in the single digits is low-competition for the obvious reason that almost nobody is looking for it.

The mobile app parallel holds here too — apps that maintain strong ratings tend to get featured more often, and data from AppTweak shows roughly 90% of Apple’s featured apps maintain a rating above 4 stars — reputation compounds into visibility beyond just search rank once a baseline of trust exists. The equivalent for a new WordPress plugin is straightforward: an early run of genuine, earned reviews does more than pad a star count. It’s the input the entire second phase of the algorithm is waiting on before it starts working in a plugin’s favor at all.

Getting Your First Reviews Without an Audience Yet

Phase two eventually starts to matter, and there’s no way around needing some real installs and reviews to get there — but the first ones don’t have to come from nowhere. Every existing channel a developer already has access to counts: a mention in an existing project’s changelog, a post in a relevant WordPress.org support forum where the plugin genuinely helps answer someone’s question, a link from a personal or company site, a request to the handful of people who beta-tested it before submission. None of this needs to be clever. It needs to happen consistently in the first few weeks, because WordPress.org’s quality signals reward recent activity, not just lifetime totals — a plugin that picks up five installs and one honest review in its first month is sending a stronger signal than one that picks up the same five installs spread thinly across a year.

None of these five require an existing audience, a marketing budget, or a lucky mention somewhere with traffic. They require doing the unglamorous parts of running a plugin consistently during the exact stretch most developers treat as a waiting period rather than a working one.

Tracking What Actually Moved the Needle

The hardest part of the first 90 days isn’t picking keywords — it’s knowing which changes worked once traction starts. A readme edited three times in a month with no record of what changed when makes it impossible to tell whether the tag update or the description rewrite is what moved a keyword from position 40 to position 12. Treating this window as a genuine data-collection period — snapshotting the readme and the ranking together before and after every change — turns a guessing game into an actual experiment with a result you can read.

This is exactly the gap a tool built for keyword tracking and readme history closes, and it’s worth using from the very first scan rather than waiting until there’s something to compare against. Competitor gap analysis becomes especially useful once a plugin has a few real competitors in view for its chosen long-tail terms — seeing exactly which of the 7 fields a competing plugin has filled in, and which ones it hasn’t, turns “try to rank higher” into a specific, ordered list of fields to fix.

What This Actually Looks Like Over 90 Days

Picture a plugin approved with the generic readme most developers ship on day one: a plugin name with no keyword in it, a short description that just restates the plugin’s category, tags left mostly blank, zero installs, zero reviews. Week one is entirely readme work — rewriting the name and short description around a specific long-tail phrase, filling all 7 indexed fields deliberately instead of leaving four of them empty, and picking 3 keywords instead of 15 based on actual search interest rather than guesswork. That alone is usually enough to move a plugin from completely absent in search results to appearing somewhere on the first two pages for its chosen long-tail terms, because phase one doesn’t care that the install count is still zero.

Weeks two through six are where phase two starts to matter: a handful of installs from existing channels, two or three honest reviews from people who were actually asked, one real update pushed to keep the last-updated signal fresh, and every support question answered within a day. None of this requires an audience — it requires consistency during the exact window most developers go quiet after the initial launch excitement fades. By week twelve, a plugin that followed this sequence typically has real position data to look at: which of the 3 long-tail terms actually moved, which one didn’t, and whether a competitor closed the same gap faster. That’s the point where expanding into a slightly bigger keyword, backed by real installs and a resolved-ticket history instead of an empty readme, actually makes sense.

Who knew the plugin with zero installs and the plugin with forty thousand were reading from the exact same rulebook for the first search someone ever runs.