free tool · no login
AI Visibility Checker
Paste a page and see how ready it is to be found, read and quoted by ChatGPT, Perplexity, Claude and Google's AI Overviews. The checker looks at the parts you control: whether the AI crawlers are let in, whether a firewall quietly turns them away, whether the words are in the HTML without JavaScript, whether the site says who is behind it, and whether the page answers questions in a shape a machine can lift.
One thing it does not do: tell you whether those tools already cite you. Nobody can measure that without asking the answer engines themselves, and this tool does not scrape them. It scores readiness, and says so.
- A score out of 100, a score for each of five groups, and the three fixes worth the most first.
- Every finding in plain English, with the fix and a link to the guide and tool that go deeper.
- A summary you can copy and send to your developer. Nothing stored.
Check a page
Use the page you most want AI answers to quote. A domain checks its homepage. The homepage is read either way for the site-wide signals.
nothing checked yet
AI search readiness
Fix these first
This scores readiness: what your site controls. It cannot tell you whether ChatGPT, Perplexity or AI Overviews already cite you. That takes sampling the answers themselves.
What the checker looks at
About twenty checks in five groups, in the order an AI crawler meets them. First it has to get in, then find the page, then read it, then trust it enough to name it, then find a line worth quoting. The share next to each group is how much it counts toward the overall score.
Access 30%
Whether robots.txt lets in Googlebot, Bingbot, the AI search bots (OAI-SearchBot, ChatGPT-User, PerplexityBot, Claude) and the AI training bots. Whether a firewall turns away requests that carry AI crawler names while a browser gets through. And whether nosnippet, max-snippet or noai tags stop the page being quoted.
Discoverability 20%
Whether robots.txt names a sitemap, whether the site has an llms.txt and what the llms.txt checker makes of it, and whether anything stops the page being indexed. Most AI answers start from a search index, so a page that cannot be indexed is rarely quoted.
llms.txt v2: what changedSitemap checkerllms.txt generator and checkerIndexability checker
Readable without JavaScript 20%
How much text is in the HTML the server sends before any script runs, because most AI crawlers have never said they run JavaScript. Plus a clear title, one H1, headings in order, a meta description, a declared language and a <main> or <article> element around the real content.
Entity and trust 15%
Organization or Person markup that says who is behind the site, sameAs links to your profiles elsewhere, an author and dates on articles, about and contact pages that load, and a canonical that points to the page itself.
Does schema help with AI search?How to track brand mentions in AI search
Answerability 15%
Headings phrased as questions, a short answer of 8 to 60 words right under each heading, lists and tables for steps and comparisons, and a date that shows the page is current.
Do I need to optimize for AI Overviews?AI search visibility, explained
Each check passes, warns or fails. A warning gets half credit. Checks that do not apply, like author and dates on a page that is not an article, are left out rather than counted against you. Blocking AI training bots is a fair business choice, so it only costs a little; blocking the AI search bots costs a lot, because those are the ones that fetch pages to cite them.
What it cannot see
- Whether you are cited today. That needs sampling the answers. The AI search visibility guide has a baseline you can run by hand in an afternoon.
- The real bots' view through a firewall. The checker sends AI crawler names from this site's server, not from OpenAI's or Anthropic's addresses. A firewall that checks addresses may let the real bots in and still refuse the checker, so a refusal is a hint to go and look.
- Text added by JavaScript. It reads the HTML the server sends, which is all most AI crawlers are known to read. Google renders scripts; the others may not.
- How good the writing is. It can tell a short answer sits under a heading. It cannot tell whether the answer is right, specific or better than a competitor's.
- Links and mentions from other sites. They matter a great deal to which sources get named, and they are outside what one page can show.
For the details behind a single group, the robots.txt tester shows the rule for every crawler, the indexability checker explains any indexing block, thesitemap checker validates the whole sitemap and thellms.txt generator writes or checks the file line by line.
Straight answers
What does this AI visibility checker actually measure?
Readiness. It checks the things on your side that decide whether an AI search tool can reach a page, read it and quote it: crawler access, firewall rules, the HTML itself, structured data and how the answers are written. Each group gets a score out of 100, and the overall score weighs access most, because a blocked page cannot be quoted however well it is written.
Can it tell me whether ChatGPT or Google AI Overviews already cite my site?
No, and no free tool honestly can. Knowing that means asking the answer engines a list of questions and recording who they name, which takes paid APIs or automated scraping of their answers. This checker does neither. To measure real visibility, sample the answers yourself on a schedule, the way tracking brand mentions in AI search describes. The readiness score tells you what to fix before that number can move.
Why does a firewall matter if robots.txt allows the AI bots?
Because robots.txt is a request and a firewall is a wall. Cloudflare and other hosts can block AI crawlers with a switch, and many sites have it on without knowing. The checker asks for the page as a browser and again under each AI crawler name. If only the AI names get a 403 or a challenge page, something in front of the site is turning them away. Some firewalls also check that a bot comes from its operator's addresses, which this checker cannot, so treat a refusal as a strong hint and check your bot settings.
Do AI crawlers run JavaScript?
Googlebot does. OpenAI, Anthropic and Perplexity have never said their crawlers do, so the safe assumption is that they read only the HTML your server sends. A page built entirely in the browser can look empty to them. The checker counts the text in the raw HTML to show you what they get. What is documented, and what is not.
Do schema markup and llms.txt improve AI visibility?
Neither is a switch. Schema hands machines your name, your profiles and your dates without guessing, which helps them attribute a quote to you. llms.txt is a short map of your best pages that some agents and coding tools read and no major engine has promised to use. Both are cheap, so they count in the score, but lightly. Access and clear answers count for more.
My score is high but AI answers never mention me. Why?
Because readiness is only the entry ticket. AI answers pick sources that rank, that answer the exact question plainly and that other sites refer to. A ready page that says nothing specific, or that nobody links to, still gets passed over. The AI search visibility guide covers what moves the number once the basics are in place.
What does the checker store?
Nothing. A small reader on this domain fetches the page, the homepage, robots.txt and llms.txt, hands the answers to your browser and keeps no copy and no log. The scoring runs in your tab. Details are on the privacy page.
Scored well and still left out of AI answers? Send me the page and I will tell you why, free.Send it on WhatsApp.