Skip to content

AI Search Visibility Checker

This AI search visibility checker fetches one page and answers the questions an answer engine asks before it can cite it.

Step 1: does ChatGPT mention your brand?

We ask ChatGPT, with web search on, five buyer-style questions about your category and count how often it names you, where you sit in its lists, and which of your pages it cites.

Step 2: AI readiness score for one page

Why you might not be cited: can AI engines reach, quote and understand the page?

Try it on or paste any public page.

Note

We fetch the page, its site's robots.txt and /llms.txt from our server and score what an answer engine can verify: which AI crawlers may fetch this path (grouped by whether they index for AI search, fetch on a user's behalf, or collect training data), whether the server or its firewall turns five of them away when we request the page with their user agents (from our server, not their IP ranges, so a refusal is a rule to check rather than proof), whether noindex, nosnippet or max-snippet:0 keeps it out of answers, and whether the HTML carries a title, one H1, real sections, readable body text, a language, a canonical, structured data, a named organisation or author and dates. The score is a heuristic. Google has said no special markup or file is needed to appear in AI Overviews or AI Mode, so llms.txt and content-type markup are reported as extras, never as defects. Nothing from the fetched pages is stored or shown back; only these derived facts leave the server.

Can its crawler reach the page, or does robots.txt turn it away? Is it allowed to quote it, or does a nosnippet rule say no? Can it tell what the page is about, who published it and when? Each check comes back with a verdict, the evidence and the fix, and the whole thing is summed into a readiness score that is honest about being a heuristic. No sign-up, nothing to install.

Use this tool often? Bookmark this page, so it is one click away next time.

Email me this result

Want a copy for your records or a client? Leave your email and we'll send you this result. It is written by a real person at Crawl Cove, not an automated blast, so it may take a little while to arrive. We'll only use your address to send it, unless you also tick the box below. Privacy policy.

That email address doesn't look right. Please check it and try again.

Something went wrong saving your address. Your result above is unaffected; please try again.

Got it. We'll email your result to you. Nothing else lands in your inbox unless you ticked the tips box.

What this AI search visibility checker looks at

Paste a URL and three things are fetched server-side: the page itself, its site's robots.txt and its /llms.txt. Then the page is requested again, once as a browser and once as each of five AI crawlers, to see whether the server lets them in. From all that it runs over twenty checks in four groups. Access: can the AI search crawlers, the user-triggered fetchers and Googlebot reach this exact path under robots.txt, does the server or its firewall turn the AI crawlers away anyway, and does a noindex, nosnippet or max-snippet:0 directive keep it out of answers? Understanding: a title, a meta description, one H1, real section headings, enough readable body text, a declared language, a canonical and, as an optional extra, a linked Markdown copy. Attribution: JSON-LD and which types it declares, an Organization or Person entity, an author, and published and modified dates. Site-level: an llms.txt file and a sitemap declared in robots.txt. Each check shows the evidence it found and, where something is wrong, the fix.

Why the score is a heuristic, and says so

No answer engine publishes its ranking inputs, and Google has stated that no special markup or file is needed for a page to appear in AI Overviews or AI Mode: the same Search index and the same quality signals apply. So this tool does not pretend to measure how likely you are to be cited. It measures the documented prerequisites (crawler access, snippet controls, indexability) that can rule a page out entirely, plus the structural signals every engine's own guidance names, and adds them up. A blocking failure costs more than a missing nicety, optional extras such as llms.txt are never scored against you, and a score of 100 means nothing is in the way, not that citations are guaranteed.

How to measure AI visibility

Three kinds of AI crawler, and why they are scored differently

Blocking "AI bots" as one group is the mistake this checker is built to catch. AI search crawlers such as OAI-SearchBot, Claude-SearchBot and PerplexityBot build the search indexes their assistants answer from. OpenAI says a site that blocks OAI-SearchBot is not shown in ChatGPT search answers (it can still appear as a navigational link), Perplexity recommends allowing PerplexityBot to appear in its results, and Anthropic says blocking Claude-SearchBot may reduce visibility, so that is scored as a failure. User-triggered fetchers such as ChatGPT-User and Claude-User only open a page when someone pastes its URL into an assistant; blocking them makes the page unusable inside assistants but does not affect search, so that is a warning. Training crawlers such as GPTBot, ClaudeBot and Google-Extended collect data for model building; blocking them opts you out of training without touching AI search or Google Search, so the tool reports the choice and does not score it either way. Google-Extended has a second job: Google also reads it to decide whether your content can ground answers in the Gemini app, so blocking it can keep your pages out of those.

AI Crawler Access Checker (per-bot rules) · The full AI crawler user-agent list

Firewall and CDN rules that robots.txt cannot show

robots.txt is a request a crawler chooses to honour. A CDN, firewall or hosting rule is not: if it matches the crawler's user agent, the crawler gets a 403 or a bot challenge whatever robots.txt allows. Some CDNs now offer a one-click "block AI bots" setting, and a site can switch it on for training crawlers and catch OAI-SearchBot and PerplexityBot with it. A robots.txt-only checker reports that site as open. This one requests the page as a browser and then as OAI-SearchBot, ChatGPT-User, Claude-User, PerplexityBot and Perplexity-User, and flags any crawler the server answers differently. One limit, stated in the result: the requests come from our server with each bot's user agent, not from the bot's own IP addresses, so a firewall that admits real crawlers by IP and refuses impostors will look like a refusal here. Treat a refusal as a rule worth checking in your CDN settings and server logs, not as proof.

Test every AI crawler live

Why Googlebot gets its own row

Google's AI Overviews and AI Mode are not fed by a separate AI crawler. They draw on the ordinary Search index, so a page Googlebot cannot crawl is out of them too, whatever the AI-specific tokens say. The row is there because the most expensive robots.txt mistake is a rule written for AI crawlers, or a staging Disallow promoted to production, that catches Google Search as well. Google-Extended, the token that controls Gemini training and grounding, is listed with the training crawlers, because it never affects Google Search.

The snippet controls that quietly remove a page from AI answers

Google documents nosnippet, max-snippet and data-nosnippet as the controls that decide whether a page's content can appear in AI Overviews and AI Mode, and the same directives are respected by other engines. A site that once added nosnippet to keep a paragraph out of a search result has, since, also kept the whole page out of every AI answer. The checker reads the meta robots tag, the googlebot-specific variant and the X-Robots-Tag header, and flags noindex, nosnippet and max-snippet:0 as blocking. If only one passage is sensitive, the fix is data-nosnippet on that element, not a page-wide rule.

Build and test a robots.txt

Structure an engine can quote from

An answer engine does not cite a page, it cites a passage. It finds that passage by heading, so the structure checks reward what makes a passage liftable: one H1 that states the topic, H2 headings that read like the question a person would type, the answer in the first sentence beneath each, and a body worth quoting served in the HTML rather than assembled by JavaScript the crawler will not run. The tool counts how many of your H2 and H3 headings are phrased as questions because that is the cheapest rewrite with the most direct effect on which passage gets chosen.

Entity, author and date: the attribution signals

Engines prefer sources they can name and date. The checker looks for JSON-LD and lists the types it finds, then asks three narrower questions: is there an Organization, Person or WebSite entity that says who is behind the page; is there an author in the markup or the meta tags; and are there published and modified dates in the JSON-LD, the article meta tags or a time element. A missing author or date is scored as something to improve rather than a blocker, because plenty of pages are cited without them, but a page that carries all three is easier to trust and easier to keep fresh.

Schema Markup Generator · Structured data checker (whole-site)

llms.txt: reported, not required

An llms.txt file is a short markdown list of the pages you most want assistants to read. The checker fetches /llms.txt and reports whether it exists, whether it is really a text file or an HTML page answering 200 for a path that does not exist, or whether it is missing. It is scored as a bonus when present and never as a defect when absent: no major engine has committed to reading it, and Google has said it is not needed. It is cheap to add and harmless, which is a different thing from being required.

Generate an llms.txt · What llms.txt is

One page here, every page there

A page-level check tells you about the page you already suspected. The costly problems are the ones spread across a template: a robots.txt rule that blocks an AI search crawler on every blog post, a theme that emits two H1s on every product page, an author block that never made it into the JSON-LD. Finding those means crawling the whole site. Crawl Cove's AI search visibility audit runs its AI visibility pack on every page in one desktop crawl and groups the findings by cause, alongside its full technical SEO audit. The app grades blocked AI crawlers by purpose, as this page does, so a blocked search crawler is a problem and a blocked training crawler is only a note, and it flags nosnippet and max-snippet:0 on every indexable page.

AI visibility tracking for your whole site · Full site audit

Frequently asked questions

What is AI search visibility?
Whether an AI answer engine such as ChatGPT search, Perplexity, Claude or Google AI Overviews and AI Mode can find your page, is allowed to quote it, and can tell what it is about and who wrote it. Being visible does not guarantee being cited, and failing a check does not always rule a page out: OpenAI, for example, can still show a page that blocks its search crawler as a navigational link. But each failure costs visibility in the engines it applies to, and Google says nothing beyond normal Search eligibility is needed for AI Overviews and AI Mode.
Does this show how often ChatGPT or Perplexity mentions my brand?
No. Brand-mention trackers put thousands of prompts to the assistants and count how often your name or your pages come back in the answers, which takes a stored database of prompts and responses. This checker answers the question that comes before that one: can a given page be fetched, quoted and attributed at all? A page that fails here is held back in the engines the failure applies to however well known the brand, so run this first and fix what it finds, then measure mentions.
How is the readiness score calculated?
Each scored check has a weight. Blocking checks (AI search crawler access, Googlebot access, indexability) weigh most, structural checks less, and optional extras such as llms.txt are not scored at all. Passes count in full, warnings count half, failures count nothing, and the total is shown out of 100. It is a heuristic, and the page says so: it measures the prerequisites you can verify, not any engine's ranking.
Does Google require llms.txt or special markup for AI Overviews?
No. Google has said that no special markup or file is needed, and that AI Overviews and AI Mode draw on the same Search index and quality signals as ordinary results. That is why this tool treats llms.txt and content-type markup as extras rather than requirements.
Which AI crawlers does it check?
Every token in our AI crawler list: OpenAI (GPTBot, OAI-SearchBot, ChatGPT-User, OAI-AdsBot), Anthropic (ClaudeBot, Claude-SearchBot, Claude-User, anthropic-ai), Google-Extended, PerplexityBot and Perplexity-User, Applebot-Extended, Meta-ExternalAgent and Meta-ExternalFetcher, Amazon (Amazonbot, Amzn-SearchBot, Amzn-User), Bytespider, CCBot, DuckAssistBot, the three Mistral AI tokens and YouBot, with Googlebot alongside. Each is grouped by purpose so that blocking training crawlers is never scored against you.
Why is blocking GPTBot not counted as a problem?
GPTBot collects training data; it is not the crawler behind ChatGPT search, which is OAI-SearchBot. Blocking training crawlers is a legitimate choice that does not remove you from AI answers, so the tool reports it as a note. Blocking OAI-SearchBot, Claude-SearchBot or PerplexityBot is different: those build the indexes the assistants cite from, and that is scored as blocking.
What does nosnippet have to do with AI search?
Google documents nosnippet, max-snippet and data-nosnippet as the controls that decide whether your content can appear in AI Overviews and AI Mode, and other engines honour them too. A page-wide nosnippet or max-snippet:0 therefore removes the page from AI answers. If only one passage is sensitive, wrap that element in data-nosnippet instead.
Does it check whether my CDN or firewall blocks AI crawlers?
Yes. Besides reading robots.txt, it requests the page as a browser and then as OAI-SearchBot, ChatGPT-User, Claude-User, PerplexityBot and Perplexity-User, and flags any of them the server refuses, challenges or rate-limits. The requests come from our server rather than the crawlers' own IP ranges, so a refusal is a rule to check, not proof that the real crawler is locked out, and the result says so.
Does it render JavaScript?
No, deliberately. Most AI crawlers fetch the raw HTML and do not execute scripts, so what this tool sees is roughly what they see. If the body-text check reports very few words but the page looks full in a browser, the content is being assembled client-side and AI crawlers are missing it.
Is this AI search visibility checker free?
Yes. It is completely free and needs no sign-up. Enter a URL and the page, its robots.txt and its llms.txt are fetched and analysed server-side; only the derived results are returned, never the page content.
Can I check a page I do not own?
Yes, the same as any browser could reach the URL. It is a read-only check: about ten requests to the target site (the page, robots.txt, llms.txt, then the page once as a browser and once as each of five AI crawlers), nothing submitted, and results are not stored anywhere you or anyone else can browse back to.
Does this check my whole site?
No, one URL at a time. Crawl Cove's desktop app runs its AI visibility pack across every page in a single crawl: AI crawler access graded by purpose, snippet controls, llms.txt, answer structure, extractability, entity markup, author and freshness. Findings are grouped by cause, so a template-level problem shows up once with every affected URL under it rather than one page at a time.
Can I export the results?
Yes. A "Download CSV" button appears once a check completes, listing every check's group, name, verdict, evidence and fix.

From one page to your whole site

This checks one page. Crawl Cove's desktop app runs its AI visibility pack across every page on your site in a single crawl, alongside the rest of the technical audit: robots.txt access for AI crawlers graded by purpose, nosnippet and max-snippet controls, llms.txt, answer structure, extractable content, entity markup, author and freshness. That is how you find the template that blocks PerplexityBot on 300 URLs rather than the one page you happened to test. See AI visibility tracking for your whole site or compare the plans.

Download free

More free tools