Plugin Gap is a research tool for WordPress plugin ideas. Describe what you are thinking of building and it searches the live WordPress.org plugin directory, then reads the returned facts into a pursuit read for each competing plugin: active install band, last release date, support resolution, rating volume, and declared WordPress compatibility. Every read shows the numbers that produced it, so you can argue with it.

Yes. Free, with no account, no limits, no watermarks, and no feature gates. It is one HTML file that runs in your browser.

Type a plain-English description of the idea, such as "booking calendar for tutors" rather than "calendar", and hit Research this idea. Plugin Gap queries the WordPress.org plugin directory, scores how much of your wording appears in each result and where it lands, and sorts by opportunity. Open any row for the evidence behind its read, or tick two to six plugins to compare them side by side.

Do not clone: your wording lands in the title, the plugin sits in an established install band, and nothing in the data looks weak. Investigate gap: real overlap plus at least one measurable soft spot, such as a stale release or unresolved support threads. Possible niche: real overlap, no soft spot, and a small installed audience, which is either unserved demand or no demand. Adjacent incumbent: only part of your wording matches and the plugin is large and healthy, so your idea may be a feature it could absorb. Not a rival: too little of your wording appears in the listing to read anything into it. Overlap is graded relative to the strongest match in the same result set, because a search usually contains a word no plugin listing will ever carry, such as the audience you have in mind.

Because sometimes there isn't one. When a plugin shows no stale release, no unresolved support threads, no poor or polarized rating with volume behind it, and no compatibility lag, Plugin Gap says so and stops there. A gap you cannot point at a number for is not a gap this tool found. Opening the plugin's row runs a deep read of its most recent reviews and dated release history, which sometimes surfaces what the summary numbers hide; beyond that, an opening would have to come from the full review archive, the forum threads, or your own use of the plugin.

Because that is all WordPress.org publishes. The directory reports active installs in bands, so a plugin showing 10,000+ has somewhere between 10,000 and 19,999 active installs. Two plugins that both show 10,000+ can be nowhere near each other, and Plugin Gap prints the full band range in each plugin's evidence panel so you can see how wide that range runs.

Sometimes, and the update date alone will not tell you. A plugin that has not shipped in two years but still has 40,000 active installs and most of its support threads resolved is stable. Look at the combination: an old release date, falling support resolution, and a declared WordPress compatibility version behind the rest of the result set. Plugin Gap surfaces all three so you can judge for yourself.

Every number comes from the public WordPress.org Plugin API, fetched live in your browser, and the retrieval time is shown on the results page, in the brief, and in the CSV export. Opening a plugin's row fetches its directory page over the same API for a deep read: star-by-star rating breakdown, its most recent reviews, its dated changelog, and whether it sells a paid tier. Feature comparisons are built from directory tags, plugin names, and public short descriptions, so a plugin that never mentions a capability may still have it.

Yes, the most recent ones. Opening a plugin's row fetches its directory page and shows its newest reviews with their star ratings, quoting the low-star ones, alongside its dated release history and whether it sells a paid tier. Only the latest reviews are published through the API, so the full history stays one click away on WordPress.org.

No account, no server, no database. Everything runs locally in your browser using JavaScript, and your searches go straight to WordPress.org. Recent searches and any conclusion you write are stored on your own device. The only tracking is basic anonymous page analytics, which sees the page address, including the search in it.

Yes. The layout adapts to phone screens, the results table scrolls sideways, and comparison works the same way. A wide screen is easier if you plan to add many columns at once.

The directory shows plugins one at a time and keeps the numbers you need on separate pages. Plugin Gap loads the whole result set, puts install band, update recency, support resolution and rating volume in one sortable table, and adds the interpretation layer with the evidence attached. Paid tools like Plugin Rank, PlugiLyzer and Active Installs cover rank tracking and growth history, which Plugin Gap does not do, and catalog browsers index the whole directory for picking plugins to install. Plugin Gap answers the question that comes before any of that: is the idea taken, and by whom.

No, and it says so on the results page. It reads what WordPress.org returns for your wording, in the relevance order WordPress.org ranks it, thirty at a time. The market read is based on what has loaded, the count is always on screen, and Load more widens the sample.

Write the idea down before you build it. Vibe Brief is a companion worksheet that turns a vague app idea into a scoped, paste-ready prompt, forcing you to name the problem and cut the feature list before you open an editor.