Check AI visibility: Can ChatGPT read your website?
Are AI crawlers allowed in, do they see your text, do they understand who you are? A score from 0 to 100 in 30 seconds.
Related services for AI visibility
What AI crawlers see on your website
Six areas decide whether AI systems find, read and cite you. The check tests all of them – with read-only requests.
Bot access & robots.txt
We evaluate 16 crawlers from AI and search providers in your robots.txt, fetch your homepage live as GPTBot, ClaudeBot and PerplexityBot – and detect 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 prioritize.
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.
Your result at a glance
Right after the check you see where your website stands and what to tackle first:
- Overall score from 0 to 100, rated from “Critical” to “AI-ready”
- Scores for all 9 categories – from bot access to citability
- Every finding with raw data, such as the HTTP status GPTBot gets from your server
- The biggest levers first, with the possible points gained per fix
58/100Needs work
Categories- AI citability40
- Authority & trust30
- robots.txt88
- Bot blocker67
- Technical & performance74
- Homepage81
- Schema & structured data45
- Sitemap100
- llms.txt0
Online shops
- Typical AI question
- “Which shop has good e-bikes under €3,000?”
- Typical blocker
- Product data only via JavaScript, bot protection in the CDN
B2B & industry
- Typical AI question
- “Manufacturers of stainless steel tanks in NRW?”
- Typical blocker
- No schema, thin homepage, details only in PDFs
Service providers & agencies
- Typical AI question
- “Good tax advisor in Düsseldorf?”
- Typical blocker
- No LocalBusiness data, profiles not linked via sameAs
Why AI overlooks your website
The six most common blockers and how to fix them
GPTBot or ClaudeBot are blocked in robots.txt.
Content only shows up after JavaScript has loaded.
There is no llms.txt and no schema markup.
Copy is promotional rather than factual and hard to quote.
A Cloudflare or WAF rule blocks unknown user agents.
High server response time (TTFB) makes crawlers give up.
Become AI-visible in 4 steps
Order matters: open the gate first, then structure content, then monitor.
Open bot access01
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.
Build Schema.org and entity linking02
Add Organization, WebSite and BreadcrumbList schema. Use sameAs links to LinkedIn, Wikipedia and Crunchbase so AI can uniquely identify your brand.
Publish llms.txt03
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.
Establish server rendering and monitoring04
Make sure main content lives in the initial HTML. Set up weekly monitoring that tracks bot responses, schema coverage and response times.
You have your score. Here is what comes next.
Every finding and fix is in the report. How you implement them is up to you.
Do it yourself
For teams with in-house development
The GEO guide bundles the key fixes from the check into an actionable playbook – free as a PDF.
Get the guideFull audit
For shops and sites with many page types
We check every template, not just the homepage – category, product, blog, landing pages – and deliver a prioritized action plan.
Request an auditImplementation & monitoring
For companies without in-house GEO capacity
Our GEO agency implements technology and content and keeps checking whether AI crawlers can still read your pages.
To the GEO agency
Check one part on its own: Check your llms.txt · May GPTBot & ClaudeBot crawl your site?
Technical check or mention tracking?
Two tools, two questions. Get the technical basis right first, then track – otherwise you measure symptoms instead of causes.
Can AI read and cite my website?AI Visibility Check
Does AI actually mention my brand?Mention tracking
GEO check vs. SEO audit: what is the difference?
A GEO check tests whether AI systems can read and cite your website as a source. An SEO audit tests how well you rank in Google. The levers overlap, but signals, bots and success metrics are their own thing.
| Aspect | SEO audit | GEO check |
|---|---|---|
| Goal | Top-10 ranking on Google | Citation in ChatGPT, Claude, Perplexity |
| Key bots | Googlebot, Bingbot | GPTBot, ClaudeBot, PerplexityBot |
| Index file | sitemap.xml | llms.txt + sitemap.xml |
| Structured data | Rich snippets (Product, FAQ) | Entity linking (Organization, sameAs, @graph) |
| Rendering | Google renders JS — with delay | AI bots often skip JS — SSR mandatory |
| Success tracking | Search Console, rank trackers | Citation tracking, brand mentions in LLMs |
Categories and weights
Ask ChatGPT, Claude or Perplexity for a provider and you get sources back. Whether your website can be one of them depends on technology first: are AI crawlers allowed in, do they see your text, do they understand who you are? The check answers that in 30 seconds – with a score from 0 to 100, every finding with its raw data and concrete fixes.
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.
| Category | Weight |
|---|---|
| AI citability | 22 % |
| Authority & trust | 18 % |
| robots.txt | 14 % |
| Bot blocker | 12 % |
| Technical & performance | 12 % |
| Homepage | 10 % |
| Schema & structured data | 9 % |
| Sitemap | 2 % |
| llms.txt | 1 % |
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-optimized 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.
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.
You can verify every finding yourself, for example the bot-blocker check in your terminal:
curl -A "GPTBot" -I https://your-domain.com
Version history of 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.
The key AI crawlers
The big providers run training and search through separate user agents. The check evaluates 16 crawlers in your robots.txt and also fetches your homepage live as GPTBot, ClaudeBot and PerplexityBot.
More in our wiki: Google AI Mode
GPTBot & OAI-SearchBot – the OpenAI crawlers
ClaudeBot – Anthropic's crawler for Claude
PerplexityBot – the AI search engine
The GEO guide for mid-sized companies
The key measures from the check as an actionable guide – free as a PDF.
DownloadWhat is an AI Visibility Check?
What is a GEO check?
How do I check whether ChatGPT knows my website?
How can I measure my AI visibility?
What is LLM visibility and how does it differ from SEO?
What is the difference between a visibility index and AI visibility?
Why is LLM visibility especially important for online shops?
Which AI crawlers should I know about?
Is it harmful to allow AI crawlers?
What is llms.txt and do I need it?
Why do AI bots sometimes get different content than browsers?
Which Schema.org types matter most for AI?
How often should I check my AI visibility?
What is a good score?
How quickly do improvements take effect?
Can nextlevels help me improve and monitor my LLM visibility?
Is the check worth it for B2B and industrial companies without an online shop?
Does the AI Visibility Check cost anything?
Can I check a subpage as well?
What happens to my URL and the result?
AI visibility: data & insights
All postsMore tools & checks
Related goal: More leads & visibility
From score to strategy.
Your result shows where it breaks. In a free 30-minute call we walk through your report together and tell you which fixes have the biggest impact.
What's it about?

Kevin Bolleßen
Head of BD & Digital Marketing
- 30 minutes by video or phone
- You talk directly to a partner, not to sales
- You get the order of steps, risks and rough costs