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 site owners who 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 site owners 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.
Detection proof
Use these examples as rollout checks: start in monitor mode, confirm the log rows, then enforce only the classes that match your protected routes.
Rollout path
Voidek is meant to start quietly: save the runtime key, run a controlled test, then raise friction only where live logs support it.
Create a personal account on the Free plan, add one protected site, and save the runtime key before turning on AI crawler blocker.
Copy the test request, export VOIDEK_API_KEY, then confirm the GPTBot row appears in Analytics with path, action, and score.
Add the decision API at middleware or backend boundaries, then tune block AI crawlers after live rows 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.
First setup
Create a personal account, add one protected site, copy the runtime key, and run one test decision before enforcing AI crawler blocker.