HomeTools › Agent Access Test

03 · Free toolunder construction

Agent Access Test

Can the automated readers of the AI systems reach your site? Tested one by one, with the status code on screen.

vynco · agent access test · exampleexample
GPTBot200
OAI-SearchBot200
ChatGPT-User200
ClaudeBot403
Claude-User403
PerplexityBot200
Perplexity-User200
Googlebot200
Google-Extended200
Bingbot200
Applebot-Extended429
Two agents blocked. The CDN anti-bot is returning 403 to the Anthropic agents and 429 to Apple. While that holds, that site does not exist for anyone asking there, no matter how much content it has.

This tool is not live yet. The screen above is the approved mockup; while it does not exist, the button tells you so and promises nothing.

How it works

  1. The tool hits your site posing as each agent, one at a time.
  2. Records the real status code: 200 gets in, 403 is a block, 429 is rate limiting.
  3. It also checks robots.txt, which is where the block is usually written without anyone knowing.
  4. Where there is a block, it names the layer doing it: robots, firewall or the CDN anti-bot.

What it does not do. It does not fix the block. The test shows the closed door and names the lock, but opening it depends on touching the CDN or the client server. That goes into the platform fix queue, or into the full audit.

See more

Keep going from here

Other free tools and other content from the site, chosen by the subject of this page.

Start with the measurement, no card

The free tools run right now, without an account. When you want to take this to your client portfolio, the start page shows the ways in, and none of them asks for a card.

See how to start