# Geo Blocking plugin

**URL:** <https://meta.discourse.org/t/geo-blocking-plugin/227824>\
**Category:** Plugin\
**Created:** [May 23, 2022, 9:43am UTC](https://meta.discourse.org/t/geo-blocking-plugin/227824 "2022-05-23T09:43:22Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)\
**Post date:** [June 17, 2025, 6:21am UTC](https://meta.discourse.org/t/geo-blocking-plugin/227824/18 "2025-06-17T06:21:15Z")

</div>

And we already have bots that creates accounts 🤷‍♂️

Scrapers are a different thing, because those steal content. Spam bots that are an issue on public instances are a totally similar issue for private forums. That’s why we have AI scanning content.

For me, geo blocking cuts away a decent amount of unwanted calls and logins. I can use it because I have an all-Finnish forum \[1\] but a global one can’t use it, of course.

Every knocker increases the load for the web server, but Discourse is different than the PHP-world. A bot can easily do a DDoS type effect to WordPress, and then geo blocking might be one part of the defense strategy. But Discourse is much more immune to that, I guess.

But against spam bots, geo blocking doesn’t help if all countries must be allowed.

* * *

1. translator may change that situation, if it is production ready someday

---

_[View the full topic](https://meta.discourse.org/t/geo-blocking-plugin/227824)._