AISeeWhy

See your site the way AI crawlers see it

Fetch any page as 14 AI and search crawlers next to a real browser. Find out which crawler is blocked, which firewall did it, and get the exact fix to paste: a robots.txt change, a Cloudflare rule, JSON-LD or llms.txt.

Free: 5 checks per hour. Nothing is stored after the report is sent.

What the check covers

Crawler access

GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User, Googlebot, Bingbot, Applebot, CCBot, Bytespider and Meta-ExternalAgent, each compared with a browser: blocks, challenge pages, stub pages and redirects, with the firewall named.

robots.txt

Rules per crawler under RFC 9309, including Google-Extended and Applebot-Extended, conflicts between your rules and what your server does, and a ready diff.

Answer readiness

A short answer under the H1, question headings, links to sources, content that needs JavaScript, and hidden contact emails.

Structured data & freshness

Article dates and author, app prices, publisher, FAQ markup, dateModified against the sitemap, hreflang and llms.txt.

Priorities, not a score

Every finding is P1 (AI answers cannot read or cite the page), P2 (important) or P3 (nice to have or a policy choice), with the evidence we saw and the fix. There is no 0–100 score to argue with.

Questions

Why can't AI search see my page?

Most often a firewall or bot protection answers AI crawlers with a challenge page or a 403 while people get the page. Other causes are robots.txt rules, content that only appears after JavaScript runs, and redirects to a login page. The check fetches your page as each crawler and as a browser and shows which one differs.

Is blocking GPTBot or other training crawlers a mistake?

No. Training crawlers such as GPTBot, ClaudeBot and CCBot collect data for model training, and blocking them is a policy choice, so the report lists it as P3. Search and user-fetch crawlers such as OAI-SearchBot, Claude-SearchBot and Perplexity-User decide whether answers can cite you, so blocking them is P1.

Does the result prove what the real crawler gets?

Not fully. The requests come from our server with each crawler's user agent, not from the vendor's verified IP ranges. The result shows how your firewall treats that user agent. Firewalls that verify crawlers by IP may let the real one through, and every block finding says so.

What does the check cost?

Checking one URL here is free, up to five checks per hour from one network. For batches, run the same audit by sitemap at a pay-per-URL price, call the API with a key, or connect an AI agent over MCP. Pages that cannot be audited are never charged.

More than one URL?

Batch audits

Audit a list of URLs or a whole sitemap, pay per audited URL, results as JSON and Markdown. Run a batch audit.

API

One POST per URL, reports in 30 languages. Read the API docs.

MCP for AI agents

Connect an agent to https://api.aiseewhy.com/mcp and call audit_url. Set it up.