Using Nginx to block Meta, Twitter and ChatGPT access to your sites
1–10 of 26 posts
Re: Using Nginx to block Meta, Twitter and ChatGPT access to your sites
#2Re: Using Nginx to block Meta, Twitter and ChatGPT access to your sites
#3Re: Using Nginx to block Meta, Twitter and ChatGPT access to your sites
#4How to turn your site ( and/or fediverse instance) invisible for Meta (Facebook, Instagram, Threads), Twitter and OpenAi ChatGPT.
[0] https://webmasters.stackexchange.com/questions/137914/spike-...
Re: Using Nginx to block Meta, Twitter and ChatGPT access to your sites
#5Re: Using Nginx to block Meta, Twitter and ChatGPT access to your sites
#6why not use robots.txt
Re: Using Nginx to block Meta, Twitter and ChatGPT access to your sites
#7Re: Using Nginx to block Meta, Twitter and ChatGPT access to your sites
#8why not use robots.txt
and check your logs to see who is not complying
Re: Using Nginx to block Meta, Twitter and ChatGPT access to your sites
#9Once it’s online, it’s online.
Re: Using Nginx to block Meta, Twitter and ChatGPT access to your sites
#10Worth noting that most of these bots are 'good bots' (i.e. they will obey robots.txt). So you can avoid the nginx resource usage entirely by adding suitable robots.txt entries.
I think using nginx tests like this could have negative effects on showing OpenGraph metadata (including images).
If choosing this approach however I would probably respond with a 403 code to mark forbidden as bots are more likely to continue making attempts if they think the server would come back online.