Fighting Spam In WordPress

Written by Jeffro On February 10, 2008 | Category Of Post (Wordpress) | 348 views | |

Mashable.com has published an article that highlights 7 Tools For Fighting Spam In WordPress. The list of plugins includes:

From my own experience, Akismet has been the only spam fighting tool I’ve needed to use on this blog. Akismet seems to pick up just about everything that is spammy, including pingbacks. Of course, the ultimate way of stopping spam is to turn commenting off on your blog, but that wouldn’t be any fun now would it? What sort of anti spam techniques/plugins are you using on your own WordPress blog?

Check Out These Related Posts:

Letting Spam Loose For A Day

I Need Your Help With Spam

Is This How Comment Spam Works

Look At All That Spam

Another Mile Stone Reached

This Post Has The Following Tags:

Share This Print This Post

There Are 6 Responses So Far. Jump To The Comment Form And Join In

Comment by Lee on 10 February 2008

Wow I just wrote about this topic a little while ago. Anyways, one of the best ways of keeping automated spam away I have found is to use Javascript to redirect real people while letting the comment bots think they commented but have actually just been ignored. Check out my post about it, maybe it will make more sense.
Keep the Comment Bots at Bay
Reply - Quote

Comment by Jeffro on 10 February 2008

@Lee Sounds like an interesting solution. Thanks for stopping by and leaving a comment, I’ll let you know what I think of the article.
Reply - Quote

Comment by Ronald Huereca on 10 February 2008

Jeff,

You should try SpamFree. It’s an awesome plugin.
Reply - Quote

Comment by Andrew on 11 February 2008

I use an anti spam plugin of my own that randomises the form names on page load to prevent bots using the html on the page to figure out which post variables to send.
Reply - Quote

Comment by Jeffro on 11 February 2008

@Andrew I came up with the idea one time to try and change the names of the form fields so that bots couldn’t automatically fill in their information. For instance, the email field would be called Emale, URL would be called Yoorl ect. However, I discovered that the form fields were hardcoded or tied into the way comments were processed and it broke the commenting form. Your idea sounds better. Is it a customized solution?
Reply - Quote

Comment by Andrew on 11 February 2008

It is something I wrote myself; I have explained it on my site.

The website link attached to this comment points to the post.

The key to it changing the post variables back to standard before WordPress starts to use them.
Reply - Quote