AI Agent View Checker

Does your page reach ChatGPT, Perplexity and Claude, or a block, a challenge page or an empty shell? One URL, four AI agents, no signup.

What This Tool Checks

A page can look fine in your browser and still be refused, challenged or empty for an AI agent. This tool requests the page once with a browser's user agent and once as each of these agents, using the user-agent string each company publishes:

For each agent it shows the HTTP status, whether it got a block or a bot-challenge page, what your robots.txt says about it, the words of text it received and what share of the browser's text that is. Then a verdict and a plain-English fix list.

How to Read the Results

What It Does Not Do

The requests come from our server, not from OpenAI, Perplexity or Anthropic. A site that checks an agent's network address may answer the real agent differently, so confirm a block in your CDN or server logs. We send one request per agent and never retry or work around a refusal. This free check does not render the page in a browser, so it cannot tell whether your content only appears after JavaScript runs; the paid GET /agent-view does.

More Free Tools

See which AI crawlers your robots.txt allows with the AI crawler checker, or browse all free tools. The background is in why a page can look fine in a browser but not to AI.

Frequently Asked Questions

What does the AI agent view checker do?

It requests your page once with a web browser's user agent and once as each of four AI agents: ChatGPT-User and GPTBot from OpenAI, PerplexityBot from Perplexity and ClaudeBot from Anthropic, each with the user-agent string its company publishes. For each agent it shows the HTTP status, whether it received a block or a bot-challenge page, what robots.txt says about it, the words of text it received and what share of the browser's text that is.

Why would an AI agent get a different page than my browser?

Three common reasons: a CDN, firewall or security plugin rule that refuses or challenges bots (sometimes switched on by default), a robots.txt rule that asks the agent to stay out, and a page whose text is added by JavaScript after it loads. AI agents read the HTML your server sends and do not run the page's scripts.

Is a block here proof that ChatGPT cannot read my site?

No. The requests come from our server with each agent's user-agent string, not from OpenAI, Perplexity or Anthropic. A site that checks an agent's network address may answer the real agent differently. Treat a block as a strong signal and confirm it in your CDN or server logs.

Does it get around firewalls or challenge pages?

No. It sends one request per agent and accepts the answer: no retries, no proxies, no challenge solving. When robots.txt disallows the page for an agent, the page is not requested as that agent.

Does it check whether my content needs JavaScript?

Not this free version. It compares each agent's copy with the HTML a browser receives before any script runs. When that HTML has almost no text, the result says the page is probably built by JavaScript. The paid agent view (GET /agent-view on the SEO Score API) also renders the page in a headless browser and reports content that only appears after JavaScript runs.