What the AI visibility checker tests
We fetch the page you enter, plus /robots.txt and /llms.txt from the same site, and run three groups of checks.
- AI crawler access (40 points). We read your robots.txt the way crawlers do and test this exact page for OAI-SearchBot, ChatGPT-User, Claude-SearchBot, PerplexityBot and Bingbot, which power AI search and citations. We also test GPTBot, ClaudeBot and Google-Extended, which relate to model training.
- AI-ready content (35 points). Does an llms.txt file exist? Is there valid JSON-LD structured data, and which types? Is the main content in the raw HTML, or does it only appear after JavaScript runs?
- Page basics (25 points). Is the page indexable, and does it have a title, a meta description and one clear H1?
Why it matters
More people now ask an assistant before they search, and those assistants answer from pages they can crawl. If robots.txt blocks their crawler, or your content only appears after JavaScript runs, you're left out of the answer, even if you rank well on Google. These blocks are often accidental: a security plugin, a copied robots.txt or a CDN bot rule can shut out AI crawlers without anyone noticing.
How to fix common issues
- Crawler blocked: find the matching
User-agentgroup in robots.txt and remove theDisallowrule, or addAllow: /for that bot. Also check your CDN or firewall, since some block AI bots by default. - Thin raw HTML: switch the page to server-side rendering or static generation so the text is in the first response.
- No schema: add JSON-LD for your Organization and the page type, such as Article, Service, Product or FAQPage, and keep it consistent with what's on the page.
- Missing basics: give every page a unique title, a one- or two-sentence description and a single H1 that says what it's about.
Fixing access and structure is the foundation. Earning citations takes content worth quoting — our AI search optimization service handles both, from crawler access to citation-worthy content.