Key takeaways from this article:
- Most plugin developers guess at which keywords to target. Competitor Keyword Spy shows you exactly which keywords your competitors are actually ranking for — no guessing required.
- The WordPress.org algorithm heavily favors exact keyword matches. Knowing which phrases your competitors have in their readmes tells you precisely what to add to yours.
- Keyword gaps are installs you’re losing every day to a plugin that ranked for a term you never thought to target.
- WhoKnew Directory SEO™ Pro’s Competitor Keyword Spy runs the entire analysis from your browser — enter a competitor’s plugin slug, and within minutes you have a ranked comparison of every keyword they’re targeting versus where you sit.
- The same keyword data feeds directly into the AI Readme optimizer — gaps you find become improvements you make, in one session.
There’s a question every plugin developer eventually asks, usually after staring at a flat install count for too long: what exactly are the top-ranking plugins doing that I’m not?
The instinct is to open the WordPress.org directory, search for your target keyword, click into a competitor’s listing, and read their readme hoping to spot something useful. Sometimes you find something. More often you come away with a vague sense that their description is longer, or their tags look different, or they’ve been around longer — none of which tells you what to actually change.
There’s a better way. And it starts with understanding that the WordPress.org search algorithm doesn’t rank plugins on reputation or longevity alone. It ranks them on keyword relevance — specifically, whether the exact phrases users are searching for appear in the right fields of a plugin’s readme. That means your competitors’ keyword strategy is sitting right there in their listing, visible to anyone who knows how to look at it systematically.
Why WordPress.org Is the Most Undervalued Discovery Channel in the Plugin Business
Before getting into the mechanics of competitor research, it’s worth understanding what’s actually at stake. WordPress.org is not just a place to host your plugin. For freemium plugins — which describes the majority of serious plugin businesses — it is the single most important customer acquisition channel that exists. Users searching the directory are not browsing casually. They have a problem, they’ve decided to solve it with a plugin, and they’re ready to install something right now. That’s as high-intent as traffic gets.
The developers who understand this invest in their directory listing the same way a SaaS company invests in Google SEO. The developers who don’t treat their readme as a formality and wonder why their install count never moves.
The difference between page one and page three for a competitive keyword isn’t usually product quality. It’s optimization. And you can’t optimize what you can’t measure — which is exactly why competitor keyword research matters so much in this space.
What Competitor Keyword Spying Actually Means on WordPress.org
On Google, competitor keyword research means using third-party tools to estimate which search terms are sending traffic to a rival’s website. The data is indirect — inferred from rankings, traffic estimates, and backlink patterns. It’s useful but imprecise.
On WordPress.org it’s more direct than that. The algorithm is open source. The ranking factors are documented. And the fields that drive keyword relevance — plugin title, short description, long description, tags, FAQ section — are all publicly visible in every plugin’s readme. When a competitor ranks for a term, it’s almost certainly because that term appears in those fields. You can see exactly where.
The challenge isn’t access to the data. It’s the time required to work through it manually. Checking a competitor’s keyword positions one by one, comparing them against your own rankings, identifying the gaps — that’s hours of work per competitor, and most developers have neither the time nor the tooling to do it consistently.
This is the problem WhoKnew Directory SEO™ Pro’s Competitor Keyword Spy is built to solve.
How Competitor Keyword Spy Works
The feature lives inside the WhoKnew Directory SEO™ admin panel under the Keyword Spy tab — Pro only, which is where the real intelligence lives. The workflow is simple enough that you can run a full competitor analysis in the time it takes to make a coffee.
You start by identifying a competitor. Either search for any plugin on WordPress.org by name or slug, or pull directly from the plugins already installed on your site. The moment you select a plugin, the tool fetches its live data from WordPress.org — name, rating, active install count, short description — and immediately extracts the keywords it’s targeting. Up to ten candidate keywords are pulled from the competitor’s tags, title, and description, cleaned and deduplicated, and displayed as visual chips before any scanning even begins. You can see at a glance what keyword territory this plugin is playing in.
The keyword extraction isn’t just pulling tags. It analyses the competitor’s plugin title and short description for meaningful phrases — filtering out generic terms like “plugin,” “WordPress,” “free,” and “pro” that carry no ranking weight — and surfaces the actual keyword phrases that are doing the SEO work. This is the vocabulary your competitor chose deliberately. It’s also the vocabulary the algorithm is matching against.
Seeing it laid out before you run a single scan often produces an immediate insight: terms you’ve never used that are sitting right at the top of a competitor’s ranking strategy.
From there, you choose your own plugin for comparison. The tool cross-references your existing keyword history — pulled from previous scans you’ve run — and builds a side-by-side comparison before touching the WordPress.org API at all. You can see where you already have position data versus where you’re flying blind.
Then you run the spy. The tool checks each extracted keyword against the WordPress.org search results and records where your competitor ranks for each one. As the scan runs — sequentially, keyword by keyword — the results table updates live. Each row shows the keyword, their rank, your rank, and a status that tells you immediately what you’re looking at.
The Status Column: Where the Real Insight Lives
The most valuable part of the results table isn’t the rank numbers. It’s the status column, which distills each keyword into one of five situations — each one pointing toward a different action.
- 1
Gap — not ranked. Your competitor ranks for this keyword. You have no position at all. This is the most actionable status in the table — it means there’s a keyword with proven search demand that your readme isn’t capturing. Adding it in the right fields could start generating installs from searches you’re currently invisible for.
- 2
Behind. Both plugins rank for this keyword, but your competitor sits higher. You’re in the game but losing. This calls for optimization of the specific fields where the keyword appears — tightening your title, strengthening your short description, making sure exact-match phrases are present where the algorithm weights them most heavily.
- 3
You rank higher. You’re winning this keyword. Don’t touch it — focus your energy on the gaps and the behind positions instead.
- 4
They don’t rank. Your competitor doesn’t rank for this keyword either. Useful context — it tells you this particular phrase may not be as well-optimized in either plugin’s readme, which could mean an opportunity if there’s genuine search volume behind it.
- 5
Tied. Both plugins rank at the same position. Usually means the term appears in both readmes at similar weights — worth monitoring after your next optimization to see if you can pull ahead.
The summary strip above the table gives you the aggregate picture immediately: how many gaps, how many keywords you’re winning, how many you’re behind on. That number at a glance tells you how much ground you have to make up — and how much opportunity is sitting unclaimed.
Research Mode: When You Just Want the Intel
Not every use case involves comparing against your own plugin. Sometimes you want to understand a competitor’s full keyword strategy before you even build something — to validate a niche, scope out the competition, or identify underserved search terms before you write a single line of readme copy.
Research mode does exactly that. Uncheck the comparison option, and the tool scans the competitor without pulling your own data at all. The results show you every keyword they rank for and where they sit, with no “your rank” column cluttering the view. It’s pure competitive intelligence — useful for market research, planning a new plugin’s positioning, or understanding why a specific plugin is dominating a search term you care about.
Snapshots: The Feature That Turns One-Time Research Into a Trend Line
A single competitor analysis is useful. A series of them over time is where the real strategic value emerges. Every time you run a scan, WhoKnew Directory SEO™ automatically saves a snapshot — a complete record of the keyword positions at that moment in time, for that competitor, for your plugin.
Those snapshots accumulate in the Previous Spy Runs panel. Each one shows the date, the keyword count, and the summary stats — gaps, winning positions, behind positions — so you can see at a glance how the competitive landscape has shifted. Did a competitor gain ground on a keyword you were winning last month? Did a gap close after you updated your readme? Did a new keyword appear in their strategy that wasn’t there before?
This is the kind of intelligence that separates plugin businesses that grow methodically from ones that react randomly. Instead of guessing whether your last readme update moved the needle, you have dated position data that tells you exactly what changed and when.
From Gap to Fix: How the Data Flows Into Your Readme
Finding a keyword gap is step one. Closing it is step two. WhoKnew Directory SEO™ Pro connects both steps without you having to switch tools or copy-paste data manually.
The keywords surfaced by the Competitor Keyword Spy flow automatically into two other features. In the Scan tab, competitor keywords appear as clickable chips — click one and it pre-fills the keyword field so you can run your own position scan for that term instantly. In the AI Readme optimizer, the same keywords appear under “From Keyword Spy” as suggestions — the gaps your competitor is winning feed directly into the prompt that generates your readme improvements.
The full loop looks like this: spy on a competitor, identify the gaps, click through to the AI optimizer, generate a readme that closes those gaps, publish it, and run the comparison again in a few weeks to see if it worked. That’s a repeatable, data-driven process for improving your directory ranking — and it all happens inside a single plugin.
Most plugin developers optimize their readme once — at launch — and never touch it again. Their competitors who use keyword spy are running analyses monthly, catching new gaps as they open, and closing them before they compound into a significant ranking deficit.
The install gap between two equally good plugins often comes down to nothing more than this: one developer is watching the keyword landscape and the other isn’t. Competitor Keyword Spy is what watching looks like in practice.
Who This Feature Is Actually For
Competitor Keyword Spy is most valuable for plugin developers who already have a listing on WordPress.org and are trying to grow installs — not developers who haven’t shipped yet, though the research mode is genuinely useful for pre-launch positioning.
If you have a plugin sitting on page two or three for keywords you know you should be ranking for, this is the fastest way to understand why. If you have a plugin with solid reviews and good ratings but a stagnant install count, keyword gaps are almost certainly part of the explanation. If you’re building a new plugin and want to understand the competitive landscape before writing your readme, research mode gives you that picture in minutes.
And if you manage plugins for clients — as a developer or agency — the ability to run competitive analyses across multiple plugins and save snapshots for comparison over time is the kind of deliverable that justifies the tool on its own.
Three weeks after the first spy run revealed 10 keyword gaps, a readme update closed all of them.
What It Doesn’t Do — And Why That’s Worth Saying
Competitor Keyword Spy is a precision tool, not a magic wand. It surfaces keywords based on what appears in a competitor’s readme and where they rank for those terms. It doesn’t predict search volume, guarantee ranking improvements, or tell you which keywords to prioritize if you have limited time. That prioritization judgment still belongs to you.
It also doesn’t automatically update your readme. The gap identification and the readme optimization are two distinct steps — the tool connects them, but you still decide what changes to make and when to publish them. That’s intentional. Automated readme changes carry risk, and the developers who get the best results from this tool are the ones who treat the keyword data as intelligence to act on thoughtfully, not instructions to follow blindly.
What it does exceptionally well is compress the research time from hours to minutes, surface insights that would be nearly impossible to find manually across multiple competitors, and create a historical record that makes the impact of your optimizations measurable rather than guesswork.
Further Reading
- Why Your Plugin Is Buried on Page 8 (And the 10-Minute Fix) — the readme is the whole game. Most developers never touch it.
- How WordPress.org Search Works and What It Means for You — understand the algorithm before you optimize for it.
- The 7 Fields WordPress.org Actually Indexes — knowing which fields matter tells you exactly where to put the keywords you find.
- We Got Our Own Plugin Shut Down — what happens when keyword optimization goes wrong, and the guardrail we built to prevent it.
Who knew the difference between page one and page three on WordPress.org was sitting right there in a competitor’s readme — and that the only thing standing between you and that data was knowing how to look at it systematically.
