Block more than one header string
Robots.txt is useful policy, but it does not enforce runtime behavior. Voidek adds an API decision point that can block known GPTBot traffic and related scraper pressure at request time.
GPTBot blocker
Block GPTBot and log AI crawler traffic by route.
A focused GPTBot blocking workflow with route-level logs, score reasons, and rollout controls.
GPTBot blockerblock GPTBotGPTBot robots.txt alternativeAI crawler logsOpenAI crawler blocker
Understand where GPTBot goes
Dashboard logs group request paths, actions, scores, and client labels so you can see whether AI crawlers are hitting docs, pricing, content, or API routes.
Fail open while tuning
For early rollout, keep normal browser traffic safe by using log mode first and only enabling block mode for high-confidence AI crawler and automation signals.
FAQ
Questions teams ask before turning on crawler defense.
Is blocking GPTBot enough to stop all AI crawling?
No. GPTBot is one identifiable crawler. Voidek also scores ClaudeBot, PerplexityBot, CCBot, headless browsers, Python clients, path scans, and rate pressure.
Does Voidek replace robots.txt?
No. Use robots.txt for public policy and Voidek for runtime logging, challenge, and blocking at protected routes.