✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Antispam Bee Pro: spam decisions & rule history as tables

Antispam Bee Pro decides on every incoming comment using rules stored in wp_options and tags the result on the comment row. SleekView joins comments with their spam reason, country, and rule into one grid.

♾️ Lifetime License available

SleekView table view for Antispam Bee Pro

Spam decisions, not just statistics

Antispam Bee Pro keeps its configuration in wp_options under the antispam_bee key and stores per-decision context on the comment itself. The reason a comment was marked as spam is added to wp_commentmeta, the country and language are written as meta values, and counters accumulate inside the option entry. The plugin's stats screen is concise; the underlying rows that make those stats true are scattered.

SleekView reads wp_comments with the antispam_bee_ meta keys joined back on, so each comment row shows the spam decision, the matched rule, the country, and the language alongside the comment fields a moderator already knows. Configuration entries appear as a settings grid where each Antispam Bee toggle is a row with its current value and the option key that backs it.

The point is to take the plugin's quiet, efficient blocking and make it inspectable. Why was this comment marked as spam? Which rule fired most often this week? Which ignored country is suddenly noisier than expected? The data already lives in WordPress; SleekView just exposes it as a grid that filters, sorts, and saves.

Workflow

From comments to a spam decision grid

1

Join comments and meta

Create a SleekView that reads wp_comments and joins the antispam_bee_ keys from wp_commentmeta. Native fields like author, date, and status sit beside spam reason, country, and rule.
2

Promote rule columns

Surface the matched rule, country, language, and the spam reason as first-class columns. Add WordPress comment status so reclassification can be done from the same grid.
3

Save moderation slices

Pin filters that recur: Spam catches this week, Pending by country, Approved with high spam score. Each saved view captures columns, filter, and sort for the next moderator.
4

Reclassify and export

Mark a row as not spam through the plugin's normal API, or annotate it inline for context. Export the active view as CSV for weekly reviews, client reports, or compliance summaries.

Sample columns

A typical Antispam Bee Pro decisions view

One row per comment with the spam reason, country, and rule joined from wp_commentmeta.
Source: wp_comments + wp_commentmeta (antispam_bee_ keys) + wp_options (antispam_bee)
When Author Decision Rule Country Comment
Today 09:14 alex Approved regular DE Great post, thanks
Today 09:33 anon Spam regexp RU buy cheap...
Today 09:52 bot42 Spam honeypot BR (empty)
Today 10:18 ria Pending manual US Awaiting moderation

Comparison

Default Antispam Bee Pro admin vs SleekView

Default Antispam Bee Pro admin

  • Stats screen is summary-only, with no row-level filter on the reason or country.
  • Per-decision context stored in wp_commentmeta is not exposed as filterable columns.
  • There is no joined view of a comment row with its spam decision and matched rule.
  • Bulk reclassification or annotation directly from the decision view is not part of the UI.
  • Configuration sits in a long form rather than a tracked grid of toggles.

SleekView

  • Joins wp_comments with its antispam_bee_ meta keys so the decision, rule, and country sit on the row.
  • Filter by rule, country, language, or comment status and save the view per moderator.
  • Inline reclassify a comment, mark it as not spam, or tag the row with internal context.
  • Surface the antispam_bee option entry as a settings grid for inspectable configuration.
  • Bulk export filtered slices for a weekly moderation review.

Features

What SleekView gives you for Antispam Bee Pro

Comments and meta

Promotes the antispam_bee_ keys from wp_commentmeta onto the matching comment row. Spam reason, country, language, and matched rule become filterable columns rather than buried meta.

Per-rule analysis

Filter the joined grid by matched rule to see which heuristics drive most of the catch. Save views like Honeypot catches this week or Regex spam by country for stable moderation reviews.

Configuration as a grid

Reads the antispam_bee option entry as a settings grid where each toggle is a row. Edits write back through the option, leaving the plugin's normal hook chain untouched.

Audience

Who uses SleekView for Antispam Bee Pro

Comment moderators

Triage comment queues by joining the spam reason and matched rule onto every row. Reclassify borderline cases inline and add an internal note so the policy decision stays visible.

Security-conscious editors

Spot campaigns by filtering decisions on country and rule. See whether one heuristic is doing all the work or whether several rules are converging on the same set of comments.

Site owners

Inspect the configuration as a grid rather than reading down a long form. See which toggles are on, when they last changed, and whether the catch rate per rule matches expectations.

The bigger picture

Why spam decisions need a grid

Antispam Bee's reputation rests on being quiet and effective, which is exactly what most sites want from comment spam. The downside of being quiet is that the per-comment reasoning lives in metadata most moderators never see. When a borderline comment is flagged, the answer to why is buried in a antispam_bee_ key on wp_commentmeta.

When a campaign suddenly spikes, the answer to which rule caught most of it is implicit in the data but not visible in the stats card. Comment moderators end up either trusting the plugin and missing the chance to tune it, or building ad hoc SQL each time a policy question comes up. Treating wp_comments joined with the Antispam Bee meta keys as a real grid changes that.

The decision becomes a column, the matched rule becomes a column, the country becomes a column, and the moderation queue finally feels like a tool the team can read together rather than a black box that occasionally needs to be trusted.

Questions

Common questions about SleekView for Antispam Bee Pro

No. The plugin keeps deciding which comments are spam and writing the reason to wp_commentmeta. SleekView reads the joined data for display and only writes back if a moderator explicitly reclassifies a comment from the row.

 

Yes. Marking a row as not spam writes through WordPress' own wp_set_comment_status path, so Antispam Bee's hooks fire and any other plugin listening for the status change sees it. SleekView does not bypass the comment moderation chain.

 

Yes. Every value Antispam Bee writes to a antispam_bee_ meta key is promoted to a column. Filter by the rule that matched, the country code, or the language and combine them with comment status.

 

SleekView paginates server-side and uses WordPress' own indexes on wp_comments and wp_commentmeta. Even on sites with hundreds of thousands of comments the grid stays responsive because the page is filtered against an indexed join.

 

Yes. The antispam_bee option entry appears as a settings grid where each toggle is a row. Edits write back through the option API so the plugin's normal load and hook chain stays intact.

 

Yes. SleekView respects WordPress' comment moderation capabilities, so only users with moderate_comments see the joined decision grid. Saved views can layer additional capability gates when the slice is sensitive.

 

Yes. Exports include only the columns currently visible and respect the active filter and sort. Use it for a weekly moderation review, a client report on spam volumes, or to feed a downstream tool that wants CSV.

 

Yes. SleekView reads wp_N_comments and the matching meta tables on each subsite the same way Antispam Bee does. A super-admin view can union across sites when the meta keys are consistent across the network.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView