✨ 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

SleekPixel for Akismet Anti-Spam sites

Akismet writes akismet_result verdicts into wp_commentmeta and an aggregate count into wp_options under akismet_spam_count. SleekPixel reads both, builds a share card with the week's blocked count and the running total, and pins it to the weekly community report on save.

♾️ Lifetime License available

SleekPixel example output for Akismet Anti-Spam

Make Akismet's wall of saves visible

Akismet is the default spam wall on most WordPress sites. Every comment that lands in wp_comments goes through Akismet's API, gets a verdict, and the verdict is written into wp_commentmeta under the akismet_result key. Spam comments end up in the spam queue, the aggregate count gets bumped in wp_options under akismet_spam_count, and the moderator never sees the comment again. The save happens, and no public record names the work.

That number is one of the most underused signals on a WordPress site. A site that blocks four thousand spam comments a week has a story to tell. Most editors never tell it because the only surface to tell it on is a stats dashboard hidden behind the admin login. SleekPixel surfaces it. The plugin reads the akismet_spam_count delta over the last seven days, the per-comment verdicts in wp_commentmeta, and renders a card that names the count and the week.

The composition matters as much as the data. The number is the headline. The subhead names the week. The badge says spam report. Readers scrolling Slack or LinkedIn see the count first and click through to the post for the story. The save is no longer invisible.

Workflow

From spam verdict to share card

1

Install alongside Akismet

Activate SleekPixel on a site that already runs Akismet. The plugin detects Akismet's commentmeta keys and offers a community report preset for the template slot map.
2

Pick a community template

Start from the community preset. The preset includes a large count slot for the blocked total, a week mark slot in the corner, and a small footer line for the false-positive count.
3

Map count fields to slots

Connect template slots to a grouped count of wp_commentmeta rows where meta_key is akismet_result and value is spam, filtered by the post's week.
4

Publish the weekly report

On save_post for the community report post type, SleekPixel renders the card and writes the PNG into uploads. The share image is live the moment the report goes out.

Output

Sample spam report share card

Rendered from a real Akismet weekly aggregate. The blocked count comes from the akismet_spam_count delta, the week mark from the report post date.

Format: PNG, OG + Twitter card Dimensions: 1200 × 630
SleekPixel example output for Akismet Anti-Spam

Comparison

Default community post vs SleekPixel for Akismet

Generic blog post OG image

  • Akismet has no built-in share image or social preview generation
  • Spam counts live in the admin stats page, never on a public surface
  • Weekly community reports default to a generic featured image with no data
  • No hook from akismet_spam_count into a per-week social card
  • Moderation work is invisible to readers who never see the comment queue

SleekPixel

  • Reads wp_commentmeta for akismet_result verdicts grouped by week
  • Pulls the running total from wp_options under akismet_spam_count
  • Renders a share card with the week's blocked count in the headline slot
  • Hooks save_post on the community report post type to refresh on publish
  • Adds a false-positive count from akismet_history records in commentmeta

Features

What SleekPixel gives you for Akismet Anti-Spam

Blocked count headline

The template puts the weekly blocked count in the headline slot. Readers see how much spam was filtered before the post itself loads, which converts the moderation save into a visible signal of community health.

Reads from commentmeta

Akismet stores per-comment verdicts in wp_commentmeta. SleekPixel reads those rows grouped by week, which gives an accurate per-week count even if the akismet_spam_count option was reset.

Pins to weekly post

The card lives on a recurring weekly community report post type. SleekPixel pins the render to save_post on that type, so every Monday's report gets a fresh card without any editor work in the middle of the loop.

Use cases

Where high-traffic comment sites get the most lift

Community-driven blogs

Community blogs with active comment sections get a weekly card that names the moderation save and reminds readers the wall is working.

News and editorial

News sites with controversial coverage attract spam and abuse waves. The weekly spam card gives moderators a public artifact of the work.

Multisite networks

Networks that aggregate spam counts across sites can render a network-wide card from a custom query against each site's wp_commentmeta table.

The bigger picture

Why moderation work deserves a public artifact

Moderation is the part of running a community site that nobody sees from the outside. Akismet does most of the work on a typical WordPress site, the spam never lands in front of a reader, and the moderator never has to clear the queue. The cost of the work and the value of the save are both invisible.

The only place the work shows up is a count on an admin stats page nobody outside the team ever sees. SleekPixel takes that count and turns it into a public artifact. The weekly community report post gets a share card with the blocked count in the headline, the week in the subhead, and the site brand on the footer.

When the post is shared into Slack or LinkedIn, the count is the first thing readers see, and the moderation team gets credit for the wall of saves they spent the week doing. The cost is the price of the plugin and the time to wire one template slot to a commentmeta query. The benefit is that the moderation save is no longer invisible, the community sees the trend, and the post itself gets the read-through every weekly report should get.

Questions

Common questions about SleekPixel for Akismet Anti-Spam

Both. SleekPixel reads wp_commentmeta and wp_options directly, which both Akismet free and Akismet Pro write to in the same way. No premium-specific API call is required to get the per-week count or the running total.

 

SleekPixel falls back to whatever count exists in wp_commentmeta at render time. If Akismet was deactivated, no new spam verdicts are written, so the week's count holds at whatever it was when the plugin stopped. The card still renders, just with the partial-week count.

 

Yes. SleekPixel reads the current site's wp_commentmeta table by default, so each blog in the network gets its own card. A network-wide card needs a custom query that switch_to_blogs through each site and aggregates the counts.

 

Yes, if the template includes the slot. SleekPixel can read the akismet_history entries in wp_commentmeta to find comments that were marked spam by Akismet but later approved by a moderator. The count goes into a small footer slot under the main headline.

 

No. SleekPixel only reads from Akismet's tables. The render output is a PNG and an og:image meta value, both stored in uploads and on wp_postmeta. Akismet's own counters, history rows and dashboard stats are untouched.

 

Yes, with the right template. SleekPixel templates can include a small inline sparkline that renders a seven-day or thirty-day rolling count from wp_commentmeta. The query is run inside the render, not at request time.

 

The default community template renders at 1200 by 630, the standard Open Graph aspect ratio. The same PNG works as og:image for Facebook, LinkedIn and Slack and as twitter:image for X with the summary_large_image card type.

 

No. Rendering happens on save_post for the community report post, not on wp_insert_comment or any of the comment hooks. The comment moderation path is unchanged, and readers leaving comments see no delay caused by SleekPixel.

 

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