everytime i check nginx logs its more scrapers then i can count and i could not find any good open source solutions
You must log in or # to comment.
If nginx, here’s an open-source blocker/honeypot: https://github.com/raminf/RoboNope-nginx
If you have it set up to be proxied or hosted by Cloudflare, they have their own solution: https://blog.cloudflare.com/declaring-your-aindependence-block-ai-bots-scrapers-and-crawlers-with-a-single-click/
Anubis is the name of the tool. Also, Cloudflare just announced they have something against AI scrapers.
I just realized an interesting thing - if I use Gemini, and tell it to do deep research, it actually goes to the websites it knows/finds, and looks up the content to provide up-to-date answers. So, some of those AI crawlers are actually not crawlers, but actual users who just use AI instead of coming directly to the site.
Soo… blocking AI completely could also potentially reduce exposure, especially as more and more people use AI to basically do searches instead of browsing themselves. That would also explain the amount of requests daily - could be simply different users using AI to research for some topic.
Point is, you should evaluate if the AI requests are just proxies of real users, and blocking AI blocks real users from knowing your site exists.
Porque no los dos?
There is no functional difference between them scraping you systematically and them coming to you on behalf of user. They’re coming to scrape you either way, being asked by someone is just going to make them do it in a smarter fashion.
Also, if you’re not using Gemini, damned if Google.com doesn’t search you with it anyway. They want these AIs trained bad, sooner or later almost all searching will be done through AI. There will eventually be no option.
You are correct that blocking all AI calls well eventually make your search results not work.
So if you want organic traffic, you have to allow ai scraping eventually. You’re just going to get diminishing returns until a point.
some of those AI crawlers are actually not crawlers, but actual users who just use AI instead of coming directly to the site. Soo… blocking AI completely could also potentially reduce exposure.
Normally, websites want users to come to their site, instead of an AI search engine “stealing” the content and presenting it as it’s own. Yes, AI search engines are more convenient for the user, but in the end it will discourage website creators and thereby cut of it’s own “food supply”.
Yeah I’d consider blocking out both the bots and AI-users a win-win lmao
I understand, but the shift in user behaviour is significant and I think websites are not taking it into account. If the users move more and more to AI, and since Google introduced AI mode it’s only a question of time until it becomes the default, we will see more and more of what we thing are AI crawlers and less and less organic users.
AI seems to be the new middleman between you and the user, and if you block the middleman, you block the user. For people with hobby websites or established sites it may make sense because people either know of them, or getting more exposure is not a wish or requirement, but for everyone else, it will be painful.
I honestly don’t think most people replace search with AI, it will also slowly solve itself when google injects ads into the output.
If you’re able to, use GeoIP ranges to only allow access from the countries you want.
That immediately limits a lot of everything
Then - again if you’re able to - use a block list that covers known scrapers in case they’re in your country.
I use pfBlockerNG on my pfSense firewall for exactly this.
Well, someone had great idea to use zipbombs. I saw it somewhere but I don’t remember where.
I’ve seen people mention Anubis, the other one I heard about in a blog post that’s maybe worth looking into is go-away.
I’ve seen people suggesting and using Anubis, haven’t used it myself though.
I’ve had trouble with it using a vpn and privacy browsers. It often blocks me until I use a default browser.
Second Anubis, just finished by setup yesterday i have it of a oracle cloud frre tier vps, which depending on the domain routes the traffic to services hosted on the vps itself or to my server ar home. Relatively easy to setup, blocks most requests with very few false positives (one of which for example it would aggressively challenge by thunderbird trying to reach my baikal instance). I set a bit more aggresive rules than default (i also block googlebot and bingbot, since i received a bit more requests than I’d like). In like 10 hours it straight up denied about 5000 requests from the ai-catchall ruleset (mostly amazonbot) and challenged about 10000, mostly from a block of IPs in singapore, some of the hosts having the user agent of a Macintosh with PowerPC. They all sure love to explore the public repos on my git server.
I’m in the process of changing servers for an upgrade, the old one still hosting more services while I setup the new one. The old one now does run audibly quiter. I don’t even want to think how much electricity went wasted because of those bots
I especially love the irony of Anubis using yesterday’s hype thing to combat today’s.
i tried Anubis and it works great the only issue is it wont support multiple subdomains
I was going to recommend that, very easy to setup
You need yo block the alibaba subnets primarily. In my experience this is where most of them originate
Wern’t there a few AI maze projects in the works? I wonder if running one of those for a bit will cause you to be added to an ignore list, clearly they dont respect your robots file.
Tar pits I think is the term they use to pollute AI data.
crowdsec is arguably not completely open source, but I’m very satisfied with it.
The scraper blocklist on crowdsec requires a paid subscription, though, or did you find another workaround?
I don’t remember how I set it up a long time ago. But when I look at my server logs I only see myself.
Afaik I just added the biggests lists. But I don’t remember.
