Skip to main content
Akismet Anti-spam logo

Akismet Anti-spam

Checks WordPress comments and supported form submissions against Akismet’s anti-spam service to reduce automated junk and moderation work.
Anti-SpamRecommendedFreemium
Visit Plugin
Last Updated: October 16, 2026

Plugin Health & Stats

Checked 1 day agoSource: WordPress.org
Active installs
5,000,000+Official WordPress.org tier
WP.org rating
4.7/51,186 ratings
Version
5.7.2Current repository release
Last updated
3 months agoAug 18, 2026
Total downloads408,905,010
Tested with WP7.1.4
Requires WP5.8+
Requires PHP7.2+
Support resolved (2 mo.)0 of 1 (0%)
Plugin age21 years
Updates observed0
Tracking sinceSep 12, 2026

Historical overview

364-day WordPress.org history
Download trendDaily package downloads · last 90 days
7d222,524 30d1,248,375 90d10,047,633 Peak day2.9MAug 19
Aug 19Sep 17Oct 17Nov 16
Active version adoptionCurrent usage share
5.7 63.2%other 15.2%5.3 9.3%4.1 6.3%5.6 6.0%

Quick take

Akismet solves a boring but expensive WordPress problem: spam that consumes moderation time and pollutes comments or form submissions. Instead of relying only on local rules or CAPTCHAs, Akismet sends supported content through its cloud anti-spam service and decides whether it looks legitimate.

Best fit: Akismet Anti-spam makes the most sense for blogs, publications, business sites, and form-heavy WordPress sites that need low-maintenance cloud-based spam filtering. I would choose a different option for sites that require a fully local anti-spam system or commercial sites that do not want an ongoing service subscription.

I would choose Akismet when you want protection that mostly works in the background. If you need an entirely self-hosted anti-spam approach or dislike sending submission data to an external filtering service, I would compare local honeypot and firewall-based alternatives.

Setup and activation

Akismet setup starts by installing the plugin, activating it, and connecting a valid Akismet account or API key. After activation, review the Anti-Spam settings instead of treating the connection itself as the whole configuration. The setup is intentionally small, which is one reason Akismet works well on sites where the owner wants spam filtering without another complex admin workflow.

Why Akismet is different from a CAPTCHA

A CAPTCHA tries to decide whether the visitor is human before a submission is accepted. Akismet takes a different route. It evaluates the content and other submission signals through its spam-detection service, which means the visitor often does not have to solve an extra challenge.

That makes the experience less intrusive for legitimate users, but it also means your site depends on an external service for the spam decision.

Features that matter

Automatic comment filtering

Akismet checks new WordPress comments and can automatically place likely spam into the spam queue. On active blogs, this can save far more time than manually reviewing every suspicious comment.

Form integration

Akismet can also protect supported contact and lead forms when the form plugin integrates with the Akismet API. That makes it useful beyond traditional blog comments.

Spam history and moderation context

WordPress administrators can see spam status information and review items when necessary. I would still check the spam queue occasionally because no automated filter should be treated as perfect.

Cloud-based detection

The filtering model benefits from Akismet’s large network rather than relying only on rules stored on one website. This is the main technical advantage, but it is also the main privacy and dependency consideration.

Choose Akismet if

  • You want spam protection that works with little day-to-day configuration.
  • Your site receives enough comments or form submissions that manual moderation is becoming a burden.
  • You are comfortable using Automattic’s cloud filtering service.

Compare alternatives if

  • You require a completely local anti-spam workflow.
  • You want a no-subscription commercial solution.
  • A simple honeypot already stops the small amount of spam your site receives.

How Akismet fits into a real moderation workflow

Akismet is most useful when it reduces the number of submissions a human has to inspect without hiding the moderation process completely. On a busy publication, community site, or lead-generation site, I would let Akismet handle the first classification layer and keep a simple review routine for the spam queue. That catches false positives and gives the team a way to confirm that legitimate messages are not being discarded silently.

Marking mistakes helps the filtering system learn

If a legitimate comment is classified as spam, restore it. If obvious spam reaches the normal comment queue, mark it as spam rather than simply deleting it. Akismet’s own support guidance encourages this correction loop because the service can use those signals to improve future classification.

For teams with multiple moderators, I would document this behavior. Deleting everything suspicious without marking spam throws away useful classification feedback, while approving questionable submissions just to clear the queue can create a poor content-quality signal on the site.

Comment spam and form spam are not exactly the same deployment

Comment protection is native to the WordPress integration, while contact-form protection depends on the form plugin supporting Akismet and passing appropriate field data. Before relying on it for lead forms, confirm the specific form plugin documents an Akismet integration and then test representative spam and legitimate submissions. A green Akismet status in WordPress does not automatically mean every third-party form is protected.

For business forms, I would also keep durable entry storage. Spam filtering decides whether a submission looks suspicious; it should not be the only record of a valuable lead, support request, or application. Entry storage, mail delivery, and anti-spam are separate reliability layers.

Privacy, API usage, and operational considerations

Akismet is a cloud service. Supported content and associated request data are evaluated by Automattic’s anti-spam infrastructure, so the site owner should review privacy disclosures and the data-processing requirements that apply to the site. This matters more for forms collecting customer, account, health, financial, or other sensitive information than for a simple public blog comment.

The WordPress plugin also needs a valid Akismet API key or an eligible connected setup. The plan determines commercial eligibility and usage allowances. The current Pro tier starts with 500 monthly spam checks for one site, while Business is designed for multiple sites and higher volume. Personal is intended for eligible non-commercial use and uses a name-your-price model.

Do not confuse spam checks with page views

Akismet usage is tied to spam-checking API activity, not ordinary page traffic. A high-traffic site with few comments or form submissions can use fewer checks than a smaller site hit by heavy automated spam. When estimating the right plan, look at the number of protected submissions and the current service allowance rather than using monthly visits as a direct proxy.

Use the plugin settings intentionally

Akismet exposes settings for comment handling, spam filtering, and privacy-related display behavior. I would configure those settings according to the site’s moderation policy instead of accepting defaults without review. A news site with active discussion may want a different moderation workflow from a small business site that mainly uses Akismet through contact forms.

Where the trade-offs show up

Akismet is not simply a free plugin for every use case. Personal pricing is designed for qualifying non-commercial sites, while business and commercial sites should evaluate the paid plans. That distinction matters when you are building client or revenue-generating sites.

There is also an external-service dependency. Supported submission data is processed through Akismet’s service, so privacy disclosures and your own data-handling requirements should be considered.

Akismet pricing

Pricing checked October 16, 2026.

Akismet’s Personal plan uses a name-your-price model for personal sites. The Pro plan is currently $9.95 per month when billed yearly for one site and includes up to 500 spam checks per month. The Business plan is currently $49.95 per month billed yearly and expands the allowance and site coverage.

The right plan depends on whether the site is personal or commercial and how much spam-checking volume it generates.

When Akismet earns its place in the stack

Akismet is easiest to justify when spam volume is high enough that moderation has become recurring work. A publication receiving dozens of junk comments every day, a lead form targeted by bots, or a client site where staff cannot manually inspect every submission gets direct value from an automated first-pass filter. The value is not another visible front-end feature. It is fewer bad items reaching the people responsible for content, sales, or support.

On a small site receiving only occasional spam, I would compare the ongoing plan requirement with simpler local defenses such as a honeypot, rate limiting, or the anti-spam controls already included in the form plugin. Akismet can still work well there, but the buying case is weaker if the problem is already contained without an external filtering service.

Keep a recovery path for false positives

For comments, that means reviewing the spam queue before automatic cleanup removes old items. For business forms, it means understanding how the form plugin handles a submission that Akismet marks as spam and whether administrators can inspect or restore it. The exact workflow varies by integration, so I would test it with the specific form plugin instead of assuming every Akismet-enabled form exposes the same moderation controls.

Commercial eligibility should be decided before launch

The Personal plan is aimed at eligible non-commercial sites. A business, store, professional service, client project, or revenue-generating publication should evaluate the commercial tiers rather than treating the free or name-your-price route as a permanent business license. That avoids a licensing mismatch later when the site grows or changes ownership.

Review volume before choosing a higher Akismet tier

If the site approaches its plan allowance, I would first identify which forms and comment surfaces are generating the checks. A sudden increase can indicate a spam campaign, a newly exposed endpoint, or a form that is being hit repeatedly. That context matters because moving to a higher plan solves the quota problem but not necessarily the underlying abuse pattern. Rate limiting, stronger form controls, or removing an unused public form can reduce needless checks while Akismet continues handling the submissions that matter.

For agencies managing many sites, the Business plan is easier to justify when centralized commercial eligibility and higher aggregate usage matter more than buying separate single-site Pro plans. I would still track which client sites create most of the volume so one noisy installation does not hide the behavior of the rest.

Current version and compatibility

The synchronized PluginSuggest profile data currently lists Akismet 5.7.2. Before deploying a major update on a high-volume site, check the official changelog and test the moderation queue, API connection, and any form integrations that depend on Akismet. Anti-spam normally runs quietly, which is exactly why a broken connection can go unnoticed until the spam volume changes.

PluginSuggest verdict

Akismet remains easy to recommend for sites where spam is a recurring operational problem. Its main strength is that it asks very little from the site owner after setup.

I would use it when the convenience of cloud filtering is worth the service dependency and commercial pricing. On a tiny site with almost no spam, a lighter local solution may be enough.

Akismet FAQs

Is Akismet free?

Akismet offers a name-your-price Personal plan for qualifying personal sites. Commercial and business use should be evaluated against its paid plans.

Does Akismet stop contact form spam?

Yes, when the form plugin integrates with Akismet. Support depends on the form plugin and how its fields are mapped to Akismet.

Does Akismet use a CAPTCHA?

Akismet is primarily a cloud content-filtering service, so it can identify spam without forcing every visitor to solve a visible CAPTCHA.

Can Akismet make mistakes?

Yes. Any automated spam system can produce false positives or miss some spam, so important sites should review the spam queue periodically.

Does Akismet send data to an external service?

Yes. Akismet uses its cloud service to evaluate supported submissions, so site owners should account for that in their privacy and data-handling practices.

Who should use Akismet?

It is a strong fit for WordPress sites with recurring comment or form spam that want low-maintenance filtering rather than a heavily configured local rule set.

How is Akismet usage measured?

Akismet plans use spam-checking API activity rather than normal page views. A site with many protected submissions can consume more checks even if its overall traffic is modest.

Similar Plugins

Community Reviews

0 community reviews
Log in or create an account to write a review.
No published community reviews yet.