Is your website visible to AI?

Enter your URL in the Devs Core AI Visibility Checker. It reads your robots.txt for GPTBot, OAI-SearchBot and ChatGPT-User, then requests your page as each of them and compares the response with what an ordinary browser gets. If robots.txt allows a crawler but your firewall returns a 403 or a challenge page, the checker flags it as likely blocked. The scan is free and takes about 20 seconds.

Three things have to be true. OAI-SearchBot and ChatGPT-User must be able to fetch your pages, which means allowing them in robots.txt and in any firewall or bot protection. Your content must be in the HTML the server sends, because those crawlers do not run JavaScript. And other sites must describe you consistently, because ChatGPT prefers to recommend businesses it can corroborate. The checker tests the first two; its AI scan samples whether ChatGPT, Claude, Gemini and Perplexity already name you, and which sources they cite.

GPTBot collects content to train OpenAI models. OAI-SearchBot builds the index behind ChatGPT search results. ChatGPT-User fetches a page when a ChatGPT user asks about it or pastes a link. Blocking GPTBot keeps your content out of future training; blocking OAI-SearchBot or ChatGPT-User removes you from ChatGPT’s answers today. Anthropic (ClaudeBot, Claude-SearchBot, Claude-User) and Perplexity split their crawlers the same way.

Block training crawlers if you do not want your content used to train models; that is a legitimate choice and does not affect live answers. Do not block search or user-triggered crawlers unless you want to disappear from AI answers, because those are the bots that fetch your pages when someone asks ChatGPT, Claude or Perplexity about your category. The checker groups every crawler by purpose so you can see the consequence of each rule.

The usual cause is client-side rendering. GPTBot, ClaudeBot and PerplexityBot read the HTML your server sends and do not execute JavaScript, so a site that builds its content in the browser can look empty to them. The second cause is bot protection that challenges or blocks non-browser requests. The checker measures both: it compares the words in your raw HTML with the words after a headless browser renders the page, and it fetches your page as 19 different AI crawlers.

llms.txt is a markdown file at the root of a site that gives language models a short summary and a list of your most important pages. It is proposed by llmstxt.org. No major AI engine has confirmed it reads the file, so it will not fix a visibility problem on its own, but it is cheap to publish. The checker tells you whether you have one and validates it against the format.

Yes. The technical scan runs without an email address. The AI scan, which asks ChatGPT, Claude, Gemini and Perplexity real questions about your brand and your category, needs a verified work email because each one costs us money to run. There is no paid tier and no card.

No, and no outside tool honestly can. Crawler visit counts live in your own server or CDN logs, which only you can see. Tools that show “AI visits” or “mentions in conversations” without access to your logs are estimating. The checker reports only what can be measured from outside: whether crawlers are allowed, whether they are actually served your page, what they can read, and what sampled AI answers say.

They are a sample, and the report labels them that way. We ask each engine the same eight questions through its official API with web search on, then twice more with search off, and grade every answer with a separate model. Consumer apps personalise answers and change them over time, so treat the results as a snapshot of how the models see you today, not a guarantee of what any one user will be told.

Your URL is scanned and the report is stored under an unguessable link for 90 days. If you run the AI scan, your email, brand, location and service are used to run it, to email you the report, and to let Devs Core follow up about it. We do not sell or share them, and you can ask us to delete them at any time.