AI Visibility Checker

Why AI visibility is the new SEO

A growing share of traffic decisions now happen inside ChatGPT, Claude, Perplexity, and AI-powered search instead of a classic results page. Those systems learn about your site two ways: crawlers like GPTBot and ClaudeBot that index the web, and live agents that fetch your pages on demand when a user asks a question. If your robots.txt blocks those bots, or your content only exists after JavaScript runs, you are invisible to both, no matter how good your traditional SEO is. This checker runs the four checks that matter most: crawler access in robots.txt, an llms.txt discovery file, server-rendered content, and a sitemap, then gives you a 0 to 100 score with exact fixes.

Frequently asked questions

Which AI crawlers does this check?

Eight of the most important ones: GPTBot (OpenAI), ClaudeBot (Anthropic), PerplexityBot, Google-Extended (Gemini training), CCBot (Common Crawl, which many models train on), Bytespider (ByteDance), Applebot-Extended (Apple Intelligence), and meta-externalagent (Meta). For each one we parse your robots.txt the way the crawler does: a group naming the specific bot overrides the wildcard group, and if you have no robots.txt at all, everything is allowed.

What is llms.txt and do I really need one?

llms.txt is a plain-text file at your domain root that gives language models a curated summary of your site: what it is, and links to your most important pages in a format that is cheap to read. It is an emerging convention rather than a hard requirement, but it costs minutes to add and gives fetch-based agents a reliable map of your content. You can use our llms.txt as a template.

Why does server-side rendering matter for AI agents?

Most AI agents and crawlers fetch your raw HTML and never execute JavaScript. A single-page app that renders everything client-side returns a nearly empty document to them: no copy, no headings, no product details. We fetch your homepage exactly like an agent would, strip scripts and markup, and measure how much readable text is actually there. More than 800 characters reads as properly server-rendered; under 200 means agents see essentially nothing.

Do you store the URLs I check?

No. The checks run server-side because browsers cannot fetch other sites directly, but we do not store your URL, log the results, or keep any history. Each check is a one-shot request that fetches four public files from your domain and returns the verdict to your browser.

My score is low. What should I fix first?

Fix blocked crawlers first, since a robots.txt block is absolute, then rendering, since invisible content cannot be cited. llms.txt and the sitemap are quick wins after that. For the deeper playbook, read the AI search guides on our blog, look at the Remote OpenClaw API for an example of a machine-readable surface done right, and join the digest for weekly updates on how AI systems discover content.