Free instant check ยท no account
Check a site the way a crawler sees it
Twelve checks, streamed in as each one answers: AI crawler rules, llms.txt, structured data, content without JavaScript, HTTP, TLS, domain, indexability, sitemap, and secrets left in client-side JavaScript.
Nine to thirty seconds; up to a minute on very large sites. 5 checks an hour.
-
Overall12 checks
-
AI search readiness4 checks
-
Technical health6 checks
-
Security2 checks
PassedNeeds attentionFailing1 block = 10% of that row's checksEvery check counts the same
What gets checked
Everything we look at
From outside, over HTTP, the way a crawler sees the site. Nothing installed, no access asked for, and we obey robots.txt on every host we touch.
| Check | Answers |
|---|---|
| AI search readiness | |
| AI crawlers | Which of GPTBot, ClaudeBot, PerplexityBot and Google-Extended does robots.txt block? |
| llms.txt | Is /llms.txt present, and what is its content hash? |
| Structured data | Is there JSON-LD, and does every block parse? |
| Content without JavaScript | How much of the main content is readable from the raw HTML? |
| Technical health | |
| HTTP status | What status does the page return, and through which redirects? |
| Time to first byte | How long until the first byte of HTML arrives? |
| Indexability | Is the page noindexed by meta robots or X-Robots-Tag, and where does rel=canonical point? |
| Sitemap | Is the XML sitemap reachable, and does it parse? |
| TLS certificate | How many days until the certificate expires? |
| Domain registration | How many days until the domain registration expires? |
| Security | |
| Bot access | Does robots.txt let our bot look at this page? |
| Secrets in JavaScript | Do the page's own script bundles contain leaked keys? |