Designed for AI crawler pressure
AI crawlers often arrive as known user agents, bare HTTP clients, headless browsers, or high-rate path probes. Voidek scores those signals before your protected route returns content.
AI crawler blocker
A low-cost AI crawler defense layer for teams that need visibility, logging, challenge, and block controls before content is served.
AI crawlers often arrive as known user agents, bare HTTP clients, headless browsers, or high-rate path probes. Voidek scores those signals before your protected route returns content.
Known search engines can be tagged separately from AI crawlers, so teams can allow Googlebot while blocking or challenging unwanted model-training and content-copying traffic.
Use monitor mode to see which crawlers are hitting your site, then switch specific traffic classes to challenge or block when the decision logs look clean.
FAQ
Yes. Voidek detects common AI crawler user agents and combines them with browser, header, route, and rate signals before returning allow, log, challenge, or block.
Voidek tags known search-engine traffic separately so Googlebot can remain allowed while AI crawlers and scraper tooling are challenged or blocked.