Plugin audit
Peter’s Custom Anti-Spam
Peter’s Custom Anti-Spam is solid but leaving growth on the table.
Active installs
200+
Rating
4.0★
wp.org · 1 reviews
Downloads / 30d
175
Momentum
+0% low volume
30d vs the 30d before
Against 1822 tracked Security plugins: health 61 vs 66 average .
Where it ranks in wp.org search
Not yet in the top 24 results for any search we track. The fixes below are what move it in.
Tags still to break into the top 24: anti spam, captcha, comments.
What to fix first
- 1
Ship an update
Last release was 688 days ago. wp.org lowers a listing's search weight once it goes about 180 days without a release.
- 2
Set "Tested up to" to WordPress 7.1
Tested up to WordPress 6.3.14; the current branch is 7.1. Matching the current branch keeps its full search weight.
- 3
“anti spam”, “captcha” and “comments” aren't earning a slot
You list them, but you're not in the first 24 results for those searches. WordPress.org counts only your first five tags, so free the slot for a search you can win.
- 4
Readme fails 5 of 8 AI readiness checks
Rewrite the readme so each failed check passes: say the job in the first line, answer real questions in the FAQ, name who it is for and what it works with, and use headings and lists.
- 5
Ask happy users for a review
A short in-plugin prompt after a success moment is the usual way. Reviews give the listing a rating people trust at install time.
Ranking signals
Listing score 54/100
- Update recency Holding it back
Updated 688 days ago, past the ~180 days where wp.org starts discounting
- WP compatibility Holding it back
Tested up to WordPress 6.3.14; the current branch is 7.1
- Rating quality Neutral
1 review so far, too few to judge quality
- Listing tuning Strong
4 of 5 tags set · short description in place
What we found
Update cadence is slipping
Needs workLast updated 23 months ago. Freshness is one of the strongest directory-ranking signals.
What to do: Get back on a visible release cadence, even minor releases.
Readme fails 5 of 8 AI readiness checks
Needs workAI assistants recommend what they can quote. Failing: says what it does, has a faq, faq asks real questions, names who it is for and names what it works with. Short description names no action; say what the plugin does for the site.
What to do: Rewrite the readme so each failed check passes: say the job in the first line, answer real questions in the FAQ, name who it is for and what it works with, and use headings and lists. For the same check on your plugin's own website, run the free AI visibility scan from AgentVania.
Run the free AI visibility scan →Review volume is thin
OpportunityOnly 1 rating. A handful of reviews makes your star average fragile and weakens trust at install time.
What to do: Run a structured in-plugin review prompt and a review campaign.
Light support activity. Few recent support threads, so there is no backlog to report.
No open vulnerabilities recorded. No unpatched security advisory is recorded against this plugin.
Downloads, last 2 years
From our own archive, not wp.org's current-week figure.
WP Mayor
Plugin promotion & growth
Work through the fixes, then put Peter’s Custom Anti-Spam in front of the right audience.
WP Mayor reviews and newsletter features reach WordPress users who are choosing plugins.
- A WP Mayor review. An independent, in-depth review in front of a high-intent audience.
- Newsletter coverage. A feature in the WP Mayor newsletter, straight to subscribers.
- A sponsored placement. Targeted visibility across WP Mayor for a defined campaign.