WikiHome RecentChanges WikiNode Preferences chongqed.org

AntiSpamRecommendations

AntiSpam Recommendations

There are various ways that wiki users can work to keep a wiki clear of WikiSpam. See AntiSpamUserSolution. Often the administrator of a wiki is one of the most active users, and so administrators should also take a look at the ideas on AntiSpamUserSolution. However the most effective antispam measures are only at the disposal of the administrator. This page gives some recommendations for administrators. These are recommendations which most wiki users agree on. On other pages you will find discussion of other antispam ideas which are more controversial.

Specific Recommendations

It's difficult to be specific without talking about specific wiki software. We are attempting to build a set of specific recommendations / instructions for the various wiki engines out there:

OddMuse, UseMod, MediaWiki, MoinMoin, DokuWiki, WackoWiki, Wakka, Wikka, PmWiki, FlexWiki, TWiki, SubWiki, PhpWiki

However this is a work in progress. We recommend you also take a look on the homepage of your wiki engine. You should find antispam recommendations there, although some engine developers are dragging their feet with this.

General Recommendations

"noindex nofollow" on old revision pages

Don't let search engines index your "Page History" or "Recent Revisions" pages. This is important. If old revisions are indexed by search engines, then all AntiSpamUserSolutions are rendered ineffective. Good wiki software prevents this by default, by emitting "noindex nofollow" for the robots META tag, or by including a robots.txt definition. Check that your software is doing this. Most modern wikis and blogs automatically do this. For more information see NoIndexHistory.

Content banning

Use a blacklist to ban spammy content from your wiki. Good wiki software includes a blacklist file, for matching edit content against regular expressions. This method has proven to be more effective than IP banning at reducing spam.

This becomes even more effective if you get Automatic Updates. You can block many of the latest spammers before they even visit your wiki, by getting updates from shared blacklists. We recommend updating your blacklist file with the list here on a regular basis (no more than once or twice a day).

For more information see ContentBanning.

Surge protection

Surge protection or edit throttling means preventing a user from making unusually large numbers of edits in short succession. Some wikis include this feature as an option. We recommend activating this, to help reduce spam, since some spammers use automated SpamBots which quickly place spam on many pages. For more information see SurgeProtection?.

Protection against Spam-agents

I just stumbled over "bad behavior" which looks worth testing. Sorry if it is mentioned on this wiki already. --Nils

I did mention it a while back on the WikiForum, but no one will see it there unless they go back through the archives. I forgot about it so I am glad you brought it up again. It seems like a good idea to me. I am just not sure how effective it is, but from some of the comments on his site it looks like it does an amazing job. – Joe - 2005-06-06 11:10 UTC

I installed and used Bad Behavior for several weeks, but saw absolutely no impact from its use at all. I finally deinstalled it since it was effectively useless. The only decent results I've gotten have been from maintaining an URL blacklist for links - although I've tried running spambotted pages manually through the Vipul's Razor client and noted, so far with testing, a 100% catch rate. If I have time, I plan on hacking together a mediawiki extension that will run proposed edits through Vipul's Razor before applying them. Seems fairly foolproof. – jimbo(at)freebsdwiki.net - 2006-01-22 23:26 EST

A new post on the Bad Behavior site explains that some spammers have adapted to the current methods Bad Behavior uses to block them. That is to be expected though. Michael was working on a new release, but due to his development machine dying he is unable to work on it and is asking for donations so he can get a new laptop. – Joe - 2006-02-05 00:54 UTC


I have tried protect web form works quite good for me. I have protected guestbook and feedback forms on my site. – Richard

That is a simple way to provide a CAPTCHA, but you shut out the visually impaired by using them. – Joe - 2006-02-05 00:45 UTC