Disable Trackbacks vs Kama SpamBlock — WordPress

Disable Trackbacks vs Kama SpamBlock

Name: Disable Trackbacks
Rating: 5 (1 reviews)

Side-by-side comparison · 24 data points

Disable Trackbacks

5.0·1reviews·200+installs

wordpress

Change

1. Listing metadata

Field-level data

	Disable Trackbacks	Kama SpamBlock
Tagline	—	—
Description	1313 / 5000 chars26% used	2614 / 5000 chars52% used
Screenshots	—	—
Languages
Platforms	WordPress	WordPress
Developer	Automattic	Timur Kamaev
Listed	—	—
Last updated	—	—

2. Categories & rankings

Shared categories on the same row · in-category position inline

Disable Trackbacks

Kama SpamBlock

Shared

At a glance

4 metrics · auto-computed

Feature comparison between Disable Trackbacks and Kama SpamBlock
Metric	Disable Trackbacks	Kama SpamBlock
Rating	5.0 ★	5.0 ★
Total reviews	1	★ 17
Active installs	200+	4,000+
Free plan	—	—

Keyword	Disable Trackbacks	Kama SpamBlock
forms	Not ranked	#767
form	Not ranked	#810

5. App details

Long-form description · keyword frequency

Disable Trackbacks

When it comes to spam and pingbacks/trackbacks, the vast majority by far is via trackbacks rather than pingbacks. Very, very few people use trackbacks for legitimate uses anymore (I’ve gotten less than 5 in the last 8 months) as WordPress, etc. all use pingbacks now as their primary ping method. I had already installed Cookies For Comments which successfully stops most spam comments but I still had to deal with the tons of trackback spam. So, I wrote this plugin. It will disable new trackbacks across your site, both legitimate and spam. However since very few people use trackbacks legitimately, this combined with Cookies For Comments should cut your spam down to next to zero. Why should I use this plugin over one of those trackback validator plugins? Most non-Akismet style anti-trackback spam plugins work by connecting to the URL that sent the trackback and looking for a link to your blog. The problem with this is that many spammers actually post links to your blog in their spam posts rendering those types of plugins useless. Even those that check the IP address to make sure it matches are beaten by spam blogs (aka splogs). In the end it’s up to you what to use for anti-spam, but I personally use Cookies For Comments, this plugin, and then Akismet to catch anything that makes it through.

Top keywords

spam8×3.49%
trackbacks5×2.18%
comments4×1.75%
cookies3×1.31%
cookies for comments3×1.31%
pingbacks3×1.31%
trackback3×1.31%
blog2×0.87%
few2×0.87%
few people2×0.87%
legitimate2×0.87%
people2×0.87%

Kama SpamBlock

Kama Spamblock blocks simple automated comment spam. It is invisible to normal visitors and does not use captchas. The plugin protects the standard WordPress comment endpoint, wp-comments-post.php. It adds a small check to the comment form. Direct requests that skip the form are blocked. This is a basic check, not proof that a person wrote the comment. Bots that load the page and run JavaScript can pass it. Kama Spamblock does not replace a full anti-spam service. It also checks pings and trackbacks for a link back to your site. Even if you are using an external comment system like Disqus, Kama Spamblock can add lightweight protection. Automated requests can be posted directly to the ‘wp-comments-post.php’ file, where the plugin can block basic bots. Simple and effective protection Kama Spamblock combines several small checks that are inexpensive for the site and invisible during normal commenting: The protective field name and its unique code rotate together every four hours. Ten recent pairs remain valid for pages served from full-page cache. Each marker is tied to the specific WordPress post, so a marker copied from another comment form is rejected. The form must remain open for at least three seconds before it can be accepted. Protective fields are added only after interaction with the comment submit button. If a valid comment is blocked, a JavaScript-only retry form preserves the entered data. The retry challenge changes its HTML structure to make basic scraping less reliable. Pingbacks and trackbacks must return a successful HTTP response, non-binary content, and a real backlink. These checks deliberately remain lightweight. A capable bot that loads the page, runs JavaScript, and reproduces normal browser behaviour can still pass them. Using Kama Spamblock with other anti-spam plugins Kama Spamblock can work with a full anti-spam plugin or service. It blocks simple direct spam requests first. The other tool can then check the comments that remain. For example, it can analyse comment text, reputation, or behaviour. The plugins complement each other. For this combination to work as intended: The other plugin should use the standard WordPress comment flow, or check comments after Kama Spamblock allows them. The site must show the standard comment form and allow the plugin’s JavaScript to run. Set the correct ID for the form’s submit button in the plugin settings. Test the setup if another plugin replaces the comment form, uses AJAX, or sends comments to its own endpoint. Kama Spamblock may need extra integration, or it may not check those comments.

Top keywords

comment12×2.86%
form8×1.91%

Frequently asked

Common questions about this comparison

Which has better reviews, Disable Trackbacks or Kama SpamBlock?

Disable Trackbacks (5.0★, 1 reviews) and Kama SpamBlock (5.0★, 17 reviews) are essentially tied on rating. Look at review velocity and individual reviewer quotes — both visible on each app's detail page — to differentiate.

Should I choose Disable Trackbacks or Kama SpamBlock?

AppRanks cannot separate these two on rating — both sit at 5.0★. Kama SpamBlock does carry the larger published review base (17 vs 1). Read both apps' detail pages for the feature breakdown and recent listing changes.

Which is faster to set up, Disable Trackbacks or Kama SpamBlock?

Both apps are one-click installs from the WordPress Plugin Directory. Kama SpamBlock has the deeper published review base (17 vs 1), which often — though not always — accompanies better-tested setup docs. AppRanks doesn't measure setup time directly: read the recent reviews on each app's detail page for user-reported install experience.

Which works better for small vs large WordPress Plugin Directory site owners?

Disable Trackbacks typically suits early-stage and growth-mode teams based on its published review base (1 reviews). Kama SpamBlock typically suits early-stage and growth-mode teams based on its published review base (17 reviews). A larger review base generally means the app has been exercised at scale — relevant if you are processing high volume or handling enterprise compliance requirements.

Can I migrate data between Disable Trackbacks and Kama SpamBlock?

Migration support varies by app and category. Disable Trackbacks and Kama SpamBlock both publish their export options on their marketplace listing pages (or in their support docs); some apps offer one-click import from competitors, others require CSV. The fastest check: search "import from Disable Trackbacks" in each app's help center. AppRanks does not track migration tooling directly — this is a category-specific capability worth verifying before commitment.

Disable Trackbacks vs Kama SpamBlock

Disable Trackbacks

1. Listing metadata

2. Categories & rankings

Kama SpamBlock

At a glance

AppRanks verdict

3. Search rankings

4. Activity in the last 90 days

Disable Trackbacks · 0 changes

Kama SpamBlock · 2 changes

5. App details

Frequently asked

Which has better reviews, Disable Trackbacks or Kama SpamBlock?

Should I choose Disable Trackbacks or Kama SpamBlock?

Which is faster to set up, Disable Trackbacks or Kama SpamBlock?

Which works better for small vs large WordPress Plugin Directory site owners?

Can I migrate data between Disable Trackbacks and Kama SpamBlock?

See full keyword rankings, install trends, and weekly alerts

More popular comparisons