Free tool / AI search technical visibility

Free AI visibility checker.
See what AI search can read.

Enter one public page. We check whether AI search crawlers (OAI-SearchBot, ChatGPT-User, Claude-SearchBot, PerplexityBot, Bingbot) are allowed by your robots.txt, look for an llms.txt file, and read the page the way a crawler does. Then we turn what we find into a short action plan. You get evidence about search foundations, page structure, and accessibility—not a made-up AI rank. The audit is a snapshot of the submitted public URL; it is not a live visibility monitor or a guarantee of inclusion.

01 / Public page

One URL.
Seven signal groups.

The scan checks AI crawler access in robots.txt, llms.txt, and the page’s HTML: indexability, title and description, headings, structured data, mobile viewport, and image alt text. It usually takes under 10 seconds.

Page to scan
Use a public page, not a dashboard or preview link. Query strings and fragments are removed before the scan.

Our scanner fetches only the public page you enter, reads up to 200 KB of its HTML, and stores none of the page content. It refuses logins, IP addresses, private networks, and unsafe redirects.

What it checks

What the AI visibility
checker looks at.

Seven signal groups, scored out of 100.

SignalPointsWhat we look for
AI crawler access25Whether robots.txt allows the AI search crawlers: OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User, and Bingbot.
Indexability15No noindex tag blocking search engines.
Search result metadata15A title and meta description.
Answer structure15A visible H1 and structured data (JSON-LD).
Mobile viewport15A mobile viewport tag.
Image alt coverage10Alt text on images.
llms.txt5An optional /llms.txt summary file.

How to read your score

  • 86–100: a strong technical foundation. Focus on content and off-site mentions.
  • 70–85: good, with visible gaps. Fix the high-priority items first.
  • Below 70: start with crawler access and indexing, because nothing else matters until AI tools can reach the page.

Questions

Common questions.

Short, honest answers.

What is an AI visibility checker?

It checks whether AI search tools can reach and understand a page: whether your robots.txt lets their crawlers in, whether you publish an llms.txt file, and whether the page has clear titles, headings, structured data, and a mobile layout.

Does this test what ChatGPT says about my business?

No. AI answers change by question, user, and time, so no tool can show every answer. This checks the access and page signals those tools rely on. For answers, keep a dated prompt log.

Should I block GPTBot or other AI crawlers?

It depends on the crawler. GPTBot and ClaudeBot collect content for AI training; blocking them does not remove you from ChatGPT or Claude search answers. Search crawlers such as OAI-SearchBot, Claude-SearchBot, and PerplexityBot are different: blocking them can keep you out of those answers. The checker scores only the search crawlers and lists training opt-outs for information.

What is llms.txt?

An optional text file at the root of your site that lists your key pages and facts for AI tools. It is an emerging convention, not a Google requirement.

Is the checker free?

Yes. The score and signal breakdown are free with no login. Enter your name and email to unlock the full fix list.

03 / Honest boundaries

A real technical scan.
Not an “AI rank.”

  • One public HTTPS page per scan; no logins or private networks.
  • Our scanner fetches the public page with a clear user agent and a 9-second limit.
  • Private hosts, IP addresses, and unsafe redirects are refused.
  • Only scores and checks are returned; page content is not stored.
  • No Google rank, Search Console position, traffic, or AI citation claim.
  • A bot check and per-visitor limits keep the scanner fair to use.

Next / Review

Need actual query and citation evidence?

Start with an audit-first review. With verified Search Console or Bing Webmaster access, we can pair first-party visibility data with crawl checks, content evidence, schema markup, and WCAG 2.1 AA accessibility testing.

Start a review

Project image

Open original image ↗