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.

Start setupOpen quickstart
GPTBot blockerblock GPTBotGPTBot robots.txt alternativeAI crawler logs

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.

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.

Detection proof

GPTBot Blocker signals Voidek can separate before content is served.

Use these examples as rollout checks: start in monitor mode, confirm the log rows, then enforce only the classes that match your protected routes.

Known botGPTBot/1.2 on protected pageLog in monitor mode, block in enforce mode
Policy gaprobots.txt ignored at runtimeUse server decision before content
Useful crawlerGooglebot on public routeKeep search-safe allow behavior

Rollout path

Start with one protected site, one test request, and one Analytics row.

Voidek is meant to start quietly: save the runtime key, run a controlled test, then raise friction only where live logs support it.

01

Add one protected site

Create a personal account on the Free plan, add one protected site, and save the runtime key before turning on GPTBot blocker.

02

Run the test decision

Copy the test request, export VOIDEK_API_KEY, then confirm the GPTBot row appears in Analytics with path, action, and score.

03

Enforce by route

Add the decision API at middleware or backend boundaries, then tune GPTBot robots.txt alternative after live rows look clean.

Related crawler defense pages
ProofPublic proof matrixReplay evidence, decisions, and limits.GuideAI Crawler BlockerAI bot blocker · block AI crawlersGuideScraper ProtectionPython requests blocker · Selenium detectionGuideCrawler Defensecrawler protection · crawler blocking APIGuideWebsite Crawler Blockerblock website crawlers · crawler blocker for website

FAQ

Questions site owners 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.

First setup

Set up one protected site before the next crawl spike.

Create a personal account, add one protected site, copy the runtime key, and run one test decision before enforcing GPTBot blocker.

Start protected site setupOpen quickstart