Skip to content
Free AI visibility check · 30 seconds

AI visibilitycheck

Find out in under 30 seconds whether AI crawlers from ChatGPT, Claude, Perplexity and Google can fetch and read your website – and how citable your content is.

The check measures the technical requirements, not actual mentions: we simulate AI crawlers, parse your robots.txt, llms.txt and sitemap, and analyse the delivered HTML including structured data and bot-blocker detection.

100% free. No email, no sign-up – results instantly in your browser.

The check fetches your domain with several bot user agents: robots.txt, llms.txt, sitemap.xml, the homepage and 3 bot simulations – read-only requests. We store the checked domain and the resulting score to evaluate the tool. Details in our privacy policy. Please only check domains you are responsible for.

The quick check analyses your homepage, robots.txt, llms.txt and sitemap. We do full site audits manually.

How the score is calculated

The score is built from 9 categories with weighted individual checks. A warning counts 40% of a check's points. Every check shows its raw data – you can trace and verify each finding yourself.

How the score is calculated
CategoryWeight
AI citability22 %
Authority & trust18 %
robots.txt14 %
Bot blocker12 %
Technical & performance12 %
Homepage10 %
Schema & structured data9 %
Sitemap2 %
llms.txt1 %

Fundamental blockers cap the score: if all three simulated AI bots are blocked, it tops out at 39. A full robots.txt block caps it at 25, missing server rendering at 49.

What your score means

  • 0–39CriticalAI crawlers can't reach your content or find barely any usable text.
  • 40–59Needs workTypical non-optimised websites land here – the basics exist, but key AI signals are missing.
  • 60–79Solid baseThe key requirements are met; some levers remain open.
  • 80–100AI-readyTechnically well set up – AI systems can read and cite your content.

What the check does not measure

  • No actual mentions or citations in AI answers – that requires mention tracking. The check shows the technical blockers behind them.
  • Only the homepage plus robots.txt, llms.txt and sitemap.xml – no subpages.
  • Bot simulation via user agent from our IP, not IP-verified crawler identity.
  • No domain authority: a very well-known website would get cited despite a mediocre score.

You can verify every finding yourself, for example the bot-blocker check in your terminal:

curl -A "GPTBot" -I https://your-domain.com

What the check tests in detail

Each category bundles several individual checks. They all run on every scan – weighted by the share shown above.

AI citability
Fact density (numbers, percentages, years), definition and answer patterns, paragraph and passage length, lists and tables, clean heading hierarchy, question-style headings.
Authority & trust
Freshness and date signals, sameAs profile links, author/byline, contact details, outbound source links, about-us signals, experience signals, visible ratings, knowsAbout topics.
robots.txt
robots.txt reachability, access rules per AI crawler (GPTBot, ClaudeBot, PerplexityBot and more), training/scraper bots, wildcard blocks, sitemap reference, Content-Signal directives, noai meta tags.
Bot blocker
Live fetches as GPTBot, ClaudeBot and PerplexityBot – is the page served in full, suspiciously throttled, or blocked?
Technical & performance
Server rendering (content visible without JavaScript), security headers, canonical tag, viewport, compression, cache-control, image dimensions (CLS), alt text.
Homepage
HTTP status, response time (TTFB), HTTPS, X-Robots-Tag, amount of text, meta description, title tag, exactly one H1.
Schema & structured data
JSON-LD present and parses cleanly, recommended @types (Organization, WebSite, LocalBusiness, BreadcrumbList, FAQPage), required fields per type, invalid properties (markup errors), required fields for app rich results, speakable, Open Graph tags, hreflang.
Sitemap
sitemap.xml reachability, lastmod freshness signal, number of listed URLs.
llms.txt
Presence and formal validity of an llms.txt.

Changes to the test suite

The check is extended continuously. Recently added tests:

  • 2026-07-01Schema markup errors: new checks for invalid properties (which Google Search Console reports as “markup errors”) and for missing required fields for app rich results (SoftwareApplication needs offers plus aggregateRating or review).
  • 2026-06-11Weighted scoring model with published category weights, score caps as kill criteria, and the new “Authority & Trust” category (E-E-A-T signals).
  • 2026-05-26Added the “Technical & Performance” and “AI Citability” categories with their individual checks.
  • Baserobots.txt evaluation, live bot access, homepage basics, core schema data, sitemap and llms.txt.

What the AI Visibility Check analyses

Bot access & robots.txt

We check whether GPTBot, ClaudeBot and PerplexityBot are allowed to fetch your pages, whether the Google-Extended opt-out directive is set – and whether a bot blocker like Cloudflare quietly shuts them out.

llms.txt

The check looks for an llms.txt – a proposed convention (llmstxt.org), not an official standard, that tells AI systems which content to use and prioritise.

Sitemap & freshness

We read your XML sitemap, count its entries and inspect lastmod dates – the freshness signals AI crawlers use to decide what is worth indexing.

Structured data

JSON-LD schema, sameAs links and speakable markup make your entity unambiguous to AI. The check lists existing types and missing fields.

Server rendering

Content that only appears after JavaScript runs stays invisible to many AI crawlers. We measure how much text already sits in the delivered HTML (SSR).

Citability

Clear definitions, short paragraphs, lists and a clean heading hierarchy decide whether AI quotes your passages verbatim. The check scores exactly that.

The key AI crawlers in detail

Three bot families decide whether your content shows up in the major AI answers. Know them – and don't accidentally block them in robots.txt – and you have the foundation for AI visibility.

More in our wiki: Google AI Mode

GPTBot & OAI-SearchBot – the OpenAI crawlers

GPTBot controls whether your content flows into the training data of OpenAI's models. For citations in ChatGPT search, OAI-SearchBot is the one that matters – the check tests both separately. So don't block wholesale: if you only want to opt out of training, keep OAI-SearchBot and ChatGPT-User allowed.

ClaudeBot – Anthropic's crawler for Claude

ClaudeBot collects content for Anthropic's Claude models; Claude-User and Claude-SearchBot fetch pages when users work with Claude on the web or search. Anthropic strictly respects robots.txt – a Disallow means no citations in Claude answers and no access via the web search tools.

PerplexityBot – the AI search engine

Perplexity is an AI search that cites sources prominently with a link. User agents: 'PerplexityBot' and 'Perplexity-User' (live browsing during a user query). If your pages are readable here, they can appear as linked sources in answers.

Common reasons AI overlooks your website

  • GPTBot or ClaudeBot are blocked in robots.txt.

    Explicitly allow the relevant AI providers' crawlers – otherwise you appear in no AI answer.
  • Content only shows up after JavaScript has loaded.

    Server-side rendering (SSR) delivers the text straight in the HTML – readable for every bot, even without running JS.
  • There is no llms.txt and no schema markup.

    Provide an llms.txt and add JSON-LD for organisation, product and FAQ – so AI systems understand your entity.
  • Copy is promotional rather than factual and hard to quote.

    Phrase answers in short, self-contained paragraphs with numbers, definitions and lists – the format AI models prefer to cite.
  • A Cloudflare or WAF rule blocks unknown user agents.

    Allowlist AI bot user agents instead of rejecting them wholesale as scrapers.
  • High server response time (TTFB) makes crawlers give up.

    Caching, a CDN and lean HTML push TTFB under one second – crawlers fetch more pages in less time.

Classic SEO vs. AI visibility

The levers overlap, but signals, bots and success metrics are their own thing.

Classic SEO vs. AI visibility
AspectClassic SEOAI visibility
GoalTop-10 ranking on GoogleCitation in ChatGPT, Claude, Perplexity
Key botsGooglebot, BingbotGPTBot, ClaudeBot, PerplexityBot
Index filesitemap.xmlllms.txt + sitemap.xml
Structured dataRich snippets (Product, FAQ)Entity linking (Organization, sameAs, @graph)
RenderingGoogle renders JS — with delayAI bots often skip JS — SSR mandatory
Success trackingSearch Console, rank trackersCitation tracking, brand mentions in LLMs

Become AI-visible in 4 steps

Order matters: open the gate first, then structure content, then monitor.

  1. 01

    Open bot access

    Allow GPTBot, ClaudeBot and PerplexityBot in robots.txt. Check Cloudflare, WAF and plugins for user-agent filters – common pitfall: Cloudflare defaults tend to reset on updates, so re-check after changes.

  2. 02

    Build Schema.org and entity linking

    Add Organization, WebSite and BreadcrumbList schema. Use sameAs links to LinkedIn, Wikipedia and Crunchbase so AI can uniquely identify your brand.

  3. 03

    Publish llms.txt

    Create a Markdown file at /llms.txt with a curated list of your most important URLs. Format per llmstxt.org – a proposed convention, not an official standard; some AI crawlers and research agents already read it.

  4. 04

    Establish server rendering and monitoring

    Make sure main content lives in the initial HTML. Set up weekly monitoring that tracks bot responses, schema coverage and response times.

GEO guide

The GEO guide for mid-sized companies

The key measures from the check as an actionable guide – free as a PDF.

Download

Frequently asked LLM visibility questions

What is LLM visibility and how does it differ from SEO?
LLM visibility describes whether and how your content appears in answers from ChatGPT, Claude, Perplexity, Gemini and Google AI Overviews. Classic SEO optimises for Google rankings; LLM optimisation optimises for AI citations. The levers overlap (clean HTML, schema, speed) but the bots, the signals (llms.txt, entity linking, FAQPage schema) and the success metrics are their own thing.
Why is LLM visibility especially important for online shops?
More and more shoppers ask ChatGPT or Perplexity instead of Google for product research. If you're not quoted or linked in those answers, you lose qualified traffic — even with strong Google rankings. Shops need server-rendered product data, Product and Offer schema, and they have to make sure AI bots aren't blocked at the WAF.
Which AI crawlers should I know about?
The most important: GPTBot (OpenAI training), OAI-SearchBot and ChatGPT-User (ChatGPT search and browsing), ClaudeBot, Claude-User and Claude-SearchBot (Anthropic), PerplexityBot and Perplexity-User (Perplexity), Applebot-Extended (Apple Intelligence), CCBot (Common Crawl, feeds many LLMs) and Bytespider (ByteDance/Doubao). Google-Extended is not a crawler of its own but an opt-out directive for Gemini training in robots.txt. Our check inspects all of them in robots.txt and simulates the most important ones.
What is llms.txt and do I need it?
llms.txt is a proposed convention (llmstxt.org): a Markdown file at /llms.txt that gives AI crawlers a curated list of your most important URLs – similar to sitemap.xml for Google. It's not an official standard, but some AI crawlers and research agents already read it. Minimal effort, clear upside.
Why do AI bots sometimes get different content than browsers?
Cloudflare Bot Fight Mode, ModSecurity, fail2ban, Varnish rules, Shopware plugins and nginx user-agent filters often block AI bots wholesale. Some setups respond with a captcha page, an empty fallback HTML or status 403. Browsers never see this — AI bots do. That's exactly the gap our bot-blocker check exposes.
Which Schema.org types matter most for AI?
Mandatory: Organization (who you are), WebSite (sitelinks search) and — if local — LocalBusiness or ProfessionalService. Strongly recommended: BreadcrumbList (hierarchy), FAQPage (voice/AI answers), Product + Offer (shops), Article + Author (blog/magazine), HowTo (guides). Combine in one @graph and enrich with sameAs links to LinkedIn, Wikipedia, Crunchbase, GitHub.
How often should I run the AI visibility check?
At minimum after every release that touches routing, headers, robots.txt, schema or performance. A regular routine also makes sense – CDN bot protection, Cloudflare defaults or Shopware plugins can change without you noticing. The tool keeps no history: note down your score or commission monitoring if you want to track progress.
Can nextlevels help me improve and monitor my LLM visibility?
Yes. We audit your full site (not just the homepage), build the missing JSON-LD, llms.txt and FAQ structures, clear bot blockers at the CDN and WAF layer, optimise server rendering and set up ongoing monitoring that tracks changes in robots.txt, bot responses, schema coverage and response times. Drop us a line about what you want to achieve — we'll get back to you within one business day.
Is the check worth it for B2B and industrial companies without an online shop?
Yes. Buyers and specialists increasingly research in ChatGPT or Perplexity – with queries like "manufacturer for X" or "provider for Y in NRW". Whether your website can appear as a source there depends on the same technical requirements as for shops: crawler access, structured data, citable content. Entity visibility matters regardless of whether you sell online.
What happens to my URL and the result?
The check only fetches publicly accessible files (robots.txt, llms.txt, sitemap.xml, homepage). We store the checked domain, score and timestamp to evaluate and improve the tool. No email address is required and there is no automatic follow-up contact. Details are in our privacy policy.

From score to strategy.

Your check result shows where it breaks. We audit the entire site, build the missing schema, llms.txt and SSR pieces and set up monitoring for ChatGPT, Perplexity & co.

Profile picture of Kevin Bolleßen, Head of BD & Digital Marketing
Kevin Bolleßen
Head of BD & Digital Marketing