Free · no sign-up · no score, just evidence
Can AI actually access your website? Find out in about 10 seconds.
People increasingly ask ChatGPT, Claude and Perplexity for recommendations. If their crawlers cannot read your site, you may never make it into the answer. Most of the time, nobody tells you.
We request your robots.txt and homepage. We read your sitemap only when robots.txt hides pages from a crawler and we need to measure how much is affected. No other page.
Three layers can keep a site out of an AI answer, and any one of them can fail quietly.
It is often not your fault. A CDN or security setting can block AI crawlers without anyone changing your site or robots.txt. Cloudflare has blocked AI crawlers by default on new sites since July 2025, and as of September 15, 2026 it also blocks AI training and agent bots on ad-supported pages, for new domains and every site on its free plan. A setting nobody remembers choosing can be enough.
robots.txtYour written policy, read the way each AI crawler reads it, not the way it is written.
Fails when One Disallow under the wrong token and ChatGPT stops citing you.
Enforced before your server sees anything. One live request per crawler says what it really does.
Fails when Bot management turns crawlers away while your file still says welcome.
What comes back before any JavaScript runs, compared word for word against a real browser.
Fails when Client-rendered text is a blank page to ChatGPT and Claude.
Your page, quoted back to somebody who asked a question you can answer.
Example GPTBot
Example ClaudeBot
GPTBotCollects training data. Blocking it does not control ChatGPT search.
OAI-SearchBotUsed for ChatGPT search and citations. Blocking it removes your site from that path.
Every crawler, and what blocking it costs you →
GPTBot or OAI-SearchBot: which one to block →
AI gets the attention, but Google still matters. A forgotten noindex, a Googlebot block or a canonical pointing somewhere else can quietly remove a page from search. We check those basics too, along with your title, description and structured data.
Every finding includes a practical fix you can copy. You can also give the whole report to Claude Code, Cursor or Copilot, with the file, rule and reason included.
## 1. OAI-SearchBot is blocked in robots.txt - Matched rule: `Disallow: /` under `User-agent: OAI-SearchBot` **Why it matters:** your site disappears from ChatGPT search answers and citations. **Fix:** remove that Disallow line…
A shop, a studio, a clinic. Someone asks an assistant “who does this near me”, and you want to be the answer.
Webflow, WordPress, Squarespace. You’d have no way of knowing a default setting was quietly hiding you.
A blog, docs, recipes, research. You’d like the citation when an AI answers a question you already answered.
Then you know the story: a deploy at 2am breaks this and nobody notices for weeks. Scan any of them, no sign-up.
Useful on their own. We don’t need your URL for any of these.
Paste the file you already have and see what it says to each AI crawler: which are blocked, which rule did it, and what that costs you. Nothing is uploaded.
Tick the crawlers you want to allow, copy the file. Each choice shows what blocking it costs you before you paste it anywhere.
One page per crawler: who runs it, whether it honours robots.txt, and exactly what you lose by turning it away. Sourced and dated.
Every request a scan makes and why, written for whoever runs the server, including how to block us in one line if you would rather not be scanned.
Or start with a question: Which AI crawlers should you allow? · AI SEO setup: the five things worth checking · Why your site is not showing up in ChatGPT · all guides →
New to this? Start here →
We do not give you a score out of 100. Those scores can move around without telling you what actually changed. We focus on things we can verify: whether a crawler is blocked, whether your CDN treats it differently, and whether the content is present without JavaScript. When something cannot be known from outside, we say so. See exactly what our scanner checks →
Sometimes. A robots.txt rule can block their crawler, your CDN can turn the request away, or the useful content may only appear after JavaScript runs. We check all three.
No. GPTBot is the training crawler. OAI-SearchBot handles ChatGPT search and citations. Blocking GPTBot does not remove you from ChatGPT search, while blocking OAI-SearchBot does.
No. Google-Extended controls Gemini training and grounding. AI Overviews and AI Mode use normal Google Search crawling, so controls such as noindex, nosnippet, data-nosnippet and max-snippet matter instead.
Most do not. Googlebot and Applebot render JavaScript, while GPTBot, ClaudeBot and PerplexityBot largely do not. We compare the initial HTML with a browser render so you can see what a non-rendering crawler misses.
Because robots.txt is only one layer. Your CDN or WAF can turn a crawler away before it reaches your server. A file checker cannot see that; an actual request can.
Free, no sign-up. Enter a domain and get the report. We do not require an email just to show you your own results.
The scan is free. For most sites, the report is enough to make the fix. If something is stuck behind a CDN or server setting, ask us. A real human will help.
What matters for your site, and what you can safely ignore. Free.
robots.txt, CDN and bot rules, noindex and canonical slip-ups, server rendering. With your developer, or instead of one.
A release tweaks a header, a CDN default flips. We keep checking and tell you the day it changes.
Email hello@deployradar.dev →Send your domain and what’s broken. We reply to every one.
We request your robots.txt and homepage. We read your sitemap only when robots.txt hides pages from a crawler and we need to measure how much is affected. No other page.