Free · no signup · 222 bots tested

Your AI visibility has two realities.

robots.txt may welcome AI crawlers while your firewall quietly turns them away. We compare policy with real server behaviour, then show exactly what to fix.

Free · no signup · 222 static checks + 19 live probes

Sample AI crawler signals passing through a website verification layer
Sample dual-engine signal map
222crawler policies checked
19live User-Agent probes
30 sectypical result time

How it works

Policy, reality, and the gap between them.

Three bounded steps turn a public URL into an evidence-based access report.

01

Read the policy

Parse robots.txt with longest-match rules and evaluate every bot in our 222-entry registry.

02

Probe the server

Send bounded requests with 19 documented AI crawler User-Agents and a browser control.

03

Explain the mismatch

Surface silent blocks, unenforced policies, infrastructure gaps, and an actionable AIVI score.

Dual-engine evidence

A static rule is not a live response.

CDN bot management, WAF rules, challenges, and rate limits live below robots.txt. aibotcheck measures both layers without pretending UA emulation is IP verification.

Read the methodology →
Sample evidence Policy + live
GPTBot Allowed 403 · Silent block
OAI-SearchBot Allowed 200 · Reachable
Browser control Baseline 200 · Reachable
robots.txt ≠ server response

The report

One score. Four explainable signals.

AIVI is designed for decisions, not decoration. Every sub-score maps to evidence and a concrete next action.

AIVI methodology →

Sample AIVI report

geolify.ai

84
Crawler access
92
AI infrastructure
78
GEO readiness
84
Trust signals
66
Structured documents connected to a machine-readable knowledge graph

Practical guidance

Fix the issue while the evidence is fresh.

Short playbooks connect each finding to a decision: what to allow, what to block, and how to make content machine-readable.

Find and fix silent WAF blocksBlock training bots without losing AI searchCreate a valid llms.txt

FAQ

Clear limits. Useful answers.

What does aibotcheck test?

Static robots.txt policy for 222 bots, live response behaviour for 19 core crawlers, plus llms.txt, structured data, markdown alternates, and selected trust signals.

Is UA emulation the same as a real crawler?

No. It shows how your server treats the documented User-Agent from our network. It cannot reproduce vendor IP ranges or TLS fingerprints; every report states this limit.

Why is robots.txt not enough?

robots.txt expresses intent. A WAF, CDN, or security plugin can still block a crawler that the file allows. That mismatch is a common source of accidental AI invisibility.

Is the check free?

Yes. No account is required. Email is optional and only used when you request a report or monitoring.

Start with evidence

See what AI can actually reach.

One URL. Two engines. A report your team can act on.