What are some alternatives to Akismet

GDPR / DSGVO: A victory for data protection compliant plugins like "AntispamBee" - A defeat for data throwers like "Akismet" and "Jetpack"


  1. Obviously you are not following the discussions about Jetpack ... or are deliberately ignoring them.

    Jetpack is adapted to the GDPR:


    Why not uninstall WordPress right away, which currently does not yet meet the requirements of the GDPR? ;-)

    • DSGV has been known for 2 years. The criticism of the WordPress core is entirely justified and I also share it. So now “First Steps” are being initiated at Jetpack. I'm following the matter closely, but for the time being these are nice promises - and it has to be shown how the majority of the functions will then work in compliance with data protection laws (as far as the core of WP is concerned, this is already formulated much more specifically). And I like to be taught better. One can criticize the greed for data
      nevertheless (and especially if you only stir now).

  2. P. S. Just by the way: Gravatar in comments will no longer be allowed ...

  3. Thank you for the hints and suggestions about replacing the Jetpack and Akismet functions with alternative plugins! I have a few questions / a note about this:

    1. Regarding YARPP: This means that I convert my WP_POSTS database table from InnoDB to an older format that the MariaDB I use has not existed for a long time or was replaced by InnoDB ages ago. Wonder what this is about, because the replacement of this format by InnoDB seems to have had good reasons. In any case, this is too risky for me, so that my readers * will probably have to forego the function of similar articles in the future.

    2. There doesn't seem to be any equivalent for functions like likes on WordPress and logging in with different social profiles, so this will also be dropped in the future.

    3. Does anyone have any advice on how I can automatically post new posts to Twitter? There are some plugins there, but they are either old or have bad reviews. Or I'm looking wrong. ;) I would be very grateful for a useful tip, would not like to have to use services like IFTTT.

    Many Thanks!

    • Hello Marco, we have used YARPP many times and always with InnoDB. In no case should you - absolutely right - rely on MyIsam, it makes your installation painfully slow. YARRP itself also recommends InnoDB.

  4. In this context, I don't understand why the REST API has to be open by default or why you have to rely on plugins to deactivate them. In my opinion, there should be an option in the WP settings to disable XML-RPC and REST API. (Okay, I'll admit: I haven't followed up on whether this is planned for the next few releases.)

  5. Instead of Yoast SEO, I recommend the better, high-performance "SEO Framework" (https://de.wordpress.org/plugins/autodescription/) without annoying up-selling!

  6. The SEO Framework is really great. I don't see why I should still use Yoast.
    I wonder why it still hasn't come out of the secret tip status.

  7. Thank you for the article!
    So far I have always used Jetpack (or the shortcode function) for my recipes. Now, due to the GDPR, I also have concerns and would like to do without this plugin. Does anyone happen to know an alternative to the plugin that works with WordPress' shortcodes? I would not like to have to enter all recipes in a completely new plugin and I appreciate the freedom to be able to work with just one shortcode. Unfortunately, my research has not yet revealed anything comparable.

    Thank you and greetings

  8. I wasn't even aware of this with Jetpack ... You always learn something new with such great blogs!

  9. To start with, a brief piece of information for you. There is no consent for the data to be saved in the comment function. As far as I know, this must be included for forms and comments. Such a text to confirm the data protection regulations with a tick.

    I have used Jetpack for a long time, albeit not all of its functions. In the meantime I've thrown it out and realized that I'm missing important things. I use the Windows WordPress app to write articles. This is no longer possible without a jetpack. In addition, the automatic sharing on social media function is missing. (So ​​far no good free alternative found).

    Isn't it enough to simply deactivate the statistics module?

    This is actually the only module I use that collects data and sends it to WordPress. Everything else would have to run internally (on your own server). That would actually save you, wouldn't you?
    For the statistics I currently use Statify although it is a bit too spartan for me. But that's enough for the beginning until the whole GDPR jumble is cleared up.

    • Hello Chris, thanks for your comment. As far as I know, it is sufficient to "disguise" or delete the IP of the commenting party in WordPress (this is the case with us in the context of the commenting function). Since you can post anonymously without logging in, the IP is the only personal date. We're not lawyers, of course. That would look different if we were to save and evaluate the IP again, yes.

      Regarding your query with the statistics: We use PIWIK / Matobo to graphically evaluate the log data. The IP is anonymized one way or another. For the statistics module you have to connect Jetpack to WordPress.com. I can't say to what extent data will flow if you only use one module. I would hardly be surprised if Jetpack is very economical ;-) As is well known, miracles happen again and again. Maybe you can test it out and publish your experiences here. Would be interesting information on the topic. Best wishes.

  10. Regarding contact forms, I heard in a webinar from a lawyer that Contact Forms 7 also stores data on US servers. Ninja Forms was recommended to us at the time. Since then, I've had Ninja Forms running on five websites everywhere. Also has a few more features that are only possible with the CF7 with an additional plug-in.

    Greetings Sascha

  11. Hi everyone,
    For everyone who deals with the GDPR compliance of backups, a reference to our documentation BackWPup, Backups and the GDPR (https://backwpup.de/doku/backwpup-backups-und-die-dsgvo/), where we describe in detail to what extent backups are GDPR-compliant and what we, as a plugin manufacturer, do so that our users make their backups compliant :) So if our pro users upload their backup to the clouds, they are encrypted there and cannot be viewed (in the event that strangers should get access to this cloud.) Here we explain in more detail how the encryption works: https: // backwpup.de/doku/wie-kann-ich-backups-verschluesseln-bevor-sie-hochladen-haben/

    Best wishes
    Jessie from Inpsyde

  12. Hmm… instead of the cookie banner cookie, can the information that the user has given his consent be saved in localStorage?