Can AI read your website?
Type your web address below. We will check whether ChatGPT, Claude, Perplexity, Google and Bing are allowed to read your site, and explain what we find in plain English.
Free. No email address. We do not store the address you enter.
Watch: Is Your Website Invisible to AI?
Recorded 21 September 2026. Prices quoted in the audio were the listed prices that day — the figures on this page are the current ones, and where the two disagree, the page is right. Plays from YouTube, and nothing loads from YouTube until you press play.
Read the full transcript
All right, let's jump right into this explainer because there's a massive, completely silent shift happening on the web today. For the last 20 years, the whole game was search engine optimization, SEO. It was all about being seen by Google. But today, we're rapidly moving into the era of answer engine optimization, or AEO. It's not just about being seen anymore. It is entirely about being recommended by artificial intelligence. It's a totally new landscape.
And that brings us to the absolute make-or-break question. You have to ask yourself right now: can ChatGPT actually read your website? If an AI like ChatGPT, Claude, or Perplexity literally cannot access your content, do you even exist in this new digital economy?
Millions of people are skipping traditional searches and asking these assistants direct questions. If those bots are flying blind when it comes to your business, you're missing out on the entire next generation of internet traffic.
So, to help audit your site and figure out if you're accidentally invisible, we're bringing in the Rank Judge. Think of him as your friendly guide to the backend laws of the internet. You see, there are underlying technical rules governing your website that could be accidentally hiding your amazing content from millions of AI users right this very second.
The Front Door Sign: How robots.txt Controls Your AI Destiny
Let's move to our first major concept: the front door sign, and see how a tiny, often completely forgotten file sitting on your server secretly controls your entire AI destiny.
Okay, every website out there has a small text file called robots.txt. Imagine your website is a house. This file isn't some heavy deadbolt lock keeping intruders out. It's really just a polite written sign hanging on your front door. It's simply asking visiting automated bots to please stay out of certain rooms. And most well-behaved bots, from search engines to AI crawlers, are absolutely going to read this sign and follow it to the letter.
What's wild about this is that most site owners have never even opened this file. It's usually just autogenerated by platforms like WordPress or Shopify when the site is first built. And because it was probably written years ago, back when Google and Bing were the only visitors that mattered, it can be incredibly outdated.
Literally one single line of text written by a developer who doesn't even work for you anymore could be telling ChatGPT to go away. And an accidental block means zero AI citations for you.
Not All Bots Are Created Equal: Answering Bots vs. Training Bots
To fix this, we're moving on to our next section. To understand a critical difference: not all bots are created equal. You absolutely must put these AI bots into two distinct camps. Treating them the same is a huge pitfall.
On one side, you have answering bots. These fetch your pages live when somebody asks an AI assistant a specific question so they can quote and link to you.
But on the other side, you have training bots. These just scrape in massive amounts of your content to train future AI models, but they don't actually send you live visitors today.
This divide is super clear when you look at the specific bots out there:
- Answering bots — OAI-SearchBot (ChatGPT), Claude-User, PerplexityBot. Fetch your pages live to quote and link to you.
- Training bots — GPTBot, ClaudeBot, Google-Extended. Scrape content to train future AI models.
So, here's the crucial takeaway. Blocking an AI from training on your hard work—that's a perfectly sensible business decision. Plenty of publishers do it intentionally. But blocking an answering bot from reading your site to answer a live user's question—that is almost always a massive mistake. It literally costs you immediate traffic, visibility, and those highly valuable citations.
The Google-Extended Trap
Quick jargon-busting moment here before we move on, because the Google-Extended trap catches so many folks off guard. A lot of website owners add rules to block Google-Extended, thinking it automatically hides their content from Google’s new AI overviews. That is totally false.
Google-Extended only stops Google from training its Gemini model on your data. AI overviews are built from their normal search index, which uses the standard Googlebot. So blocking Google-Extended does nothing to keep you out of AI overviews.
The Solution: The AI Crawler Check Tool
All right, let's dive into the actual solution. How do we find out exactly what your front door sign is telling the world without needing a computer science degree?
The answer is this fantastic, completely free resource built by founder Ron Clo over at rankjudge.com. The AI Crawler Check tool reads your site's robots.txt file and translates all that confusing technical jargon into plain simple English. Best of all, it just reads the file from the outside, so it doesn't change a single thing on your actual website.
What's really great here is how incredibly safe and private it is:
- It instantly checks your rules for the major players we talked about, like ChatGPT, Claude, and Perplexity
- There’s no database log of your searches
- You don’t need to hand over an email address
- They don’t even store the web address you type in
- It just runs the check, gives you the translation, and throws the results away instantly
What If You Get a Zero?
So, what happens if you run the check and get a big fat zero? Your doors are completely shut. Let's look at opening the right doors and getting those rules fixed.
First things first, there's a ton of buzz right now about a new file called LLM.txt, which is basically a clean site summary specifically for AI. Look, don't even worry about that right now. It's a newer, entirely optional proposal. Not having one won't hurt you at all today.
We just need to focus on fixing your core robots.txt file.
Here is your simple four-step playbook for doing this safely:
- Don't panic. If your site is silent about AI, your site isn't broken.
- Decide clearly if you want to allow answering bots, training bots, or both.
- Never edit this file by hand. One misplaced asterisk can literally block your whole site from Google. Instead, ask an AI like Claude or Codex to draft the exact text based on your decision.
- Hand that drafted text straight to your web developer so they can upload it safely.
A Quick Caveat: Network-Level Blocks
Just a quick caveat I have to point out. If you've used the Rank Judge tool and it says your doors are wide open, but you are absolutely sure you still aren't getting any AI traffic, you need to check your network settings.
Services like Cloudflare or certain hosting platforms can block bots invisibly at the network level before they even reach your robots.txt file. External tools just can't see those network blocks. So if the file looks fine but the traffic isn't coming, check your CDN or hosting provider's bot settings.
Final Thought
So to sum up the core of this explainer, remember that you have total power over who reads your site. You are in control. You just need to ensure your digital front door sign is speaking the right language for today’s internet, not the internet of 5 years ago.
Decide your strategy, draft it safely, and deploy it.
If you're curious about your own visibility, run your site through the exact AI Crawler Check tool we talked about today. It's completely free, entirely private, and it literally takes 3 seconds. Just head over to rankjudge.com/ai-crawler-check to see exactly what your site is telling the AI engines.
I'll leave you with this final thought to investigate: Are you unknowingly turning away the next massive generation of internet traffic right at your front door?
Get out there, check your file, and make sure your brilliant content is actually part of the AI conversation. Thanks for joining me on this explainer and happy optimizing.
What this check is actually looking at
Every website has a small text file called robots.txt. Yours sits at yoursite.com/robots.txt. It is a list of instructions for automated visitors, telling them which parts of your site they may look at.
Most site owners have never opened it. It was usually written when the site was built, or added automatically by WordPress, Shopify, Wix or whatever your site runs on. That was fine when the only visitors that mattered were Google and Bing.
It matters a lot more now. That same old file is what decides whether ChatGPT can look at your pages when somebody asks it a question about your industry. A single line in it, written years ago by someone who no longer works on your site, can be the reason you never come up.
This check reads that file, works out what it says about each AI bot, and tells you what it means. It does not change anything on your site.
The three kinds of bot, and why the difference matters
Bots that can quote you in an AI answer
These fetch your pages when somebody asks an AI assistant a question. If one of these is blocked, that assistant cannot read your site, so it cannot mention you in its answer or link to you. This is the group that costs you visitors.
Search engines that feed AI answers
Google and Bing still do the hard work behind most AI answers. Google AI Overviews are built from Google’s normal search index, and Bing’s index is used by ChatGPT search. Blocking these removes you from ordinary search results too, so it is rarely intentional.
Bots that learn from your content
These collect pages to help train AI models. They do not send you visitors and they do not decide whether you get quoted today. Plenty of publishers block them on purpose, and that is a perfectly sensible choice — it is a decision, not a mistake.
Common questions
- What is a robots.txt file?
- It is a small text file that sits at the top level of your website, at yoursite.com/robots.txt. It tells automated visitors which parts of your site they are allowed to look at. Most website owners have never opened theirs, because it was usually created automatically when the site was built.
- Why would my site be blocking ChatGPT?
- Usually by accident. A lot of robots.txt files were copied from a blog post, generated by a plugin, or written years ago by a developer who has since moved on. Some website platforms also add blocking rules by default. The result is the same either way: the assistant cannot read your pages, so it cannot mention you.
- Is it bad to block AI bots?
- It depends entirely on which bot. Blocking a training crawler stops AI companies learning from your writing, and plenty of publishers choose that on purpose. Blocking an answer engine stops ChatGPT, Claude or Perplexity from reading your site when somebody asks about you, which means you never get mentioned or linked. The first is a decision. The second is usually a mistake.
- Does blocking Google-Extended remove me from AI Overviews?
- No, and this catches people out. Google-Extended only controls whether Google may train Gemini on your content. Google’s AI Overviews are built from the ordinary search index, which follows Googlebot. If you want out of AI Overviews, Google-Extended is not the lever.
- What is llms.txt?
- A newer, optional file that offers AI systems a clean summary of your site and links to your most important pages. It is a proposal rather than an official standard, and no AI company has committed to reading it. We report whether you have one, but not having one is not a problem today.
- Do you store the address I check?
- No. There is no database, no logging of the address, no cookie and no email form. The check runs and the result is thrown away. RankJudge collects nothing from visitors anywhere on the site.
What this check cannot tell you
Robots.txt is not the only way a site blocks bots. Cloudflare and similar services can block them at the network level, before a request ever reaches your site, and that is invisible from the outside. Some website platforms block bots in their own settings. If this check says everything is allowed but you still see no AI traffic, those are the next places to look.
We also check the file as it stands at your home page. A site can allow a bot at the top level and block it deeper down. And bot names change without announcement, so this list is the ones we know about today, not every bot that exists.
Found this useful?
This tool is free and always will be. There is no account to make, no email to hand over and nothing collected about you. If it saved you some time, you are very welcome to put something in the tip jar.
Buy us a coffeeOpens PayPal in a new tab. Entirely optional.