AI Readiness Scanner · Beta

Can an AI agent actually read your site?

AI search engines and autonomous agents read your pages before your customers do. If your content is buried in JavaScript, trapped behind cookie walls, or invisible on mobile, you are dark to them. Scan a domain and get a structured readiness readout in seconds.

https://

Free readiness score · 14 checks · no signup to see your grade

What the scanner checks

Fourteen checks across the things that decide whether an AI system can parse, understand, and trust your pages. Each is graded and weighted into a single score.

01

JavaScript dependency

How much of your content exists in the raw HTML versus only after JavaScript runs. Many AI crawlers never run it.

02

Semantic HTML

Whether your page uses main, article, and a single clear heading structure that machines can follow.

03

ARIA roles

Role markers that let an AI chunker separate your real content from navigation and footer boilerplate.

04

Structured metadata

JSON-LD and Open Graph data that tell machines what your page is about without guessing.

05

llms.txt

The AI-native index file that gives agents a clean map of your most important content.

06

AI crawler directives

Whether your robots rules explicitly address modern AI crawlers like GPTBot and ClaudeBot.

07

Sitemap and freshness

A sitemap with last-modified data so agents can find and re-check your pages efficiently.

08

Canonical tags

Protection against the same page being embedded many times and poisoning a retrieval index.

09

Text-to-code ratio

How much real content you deliver per byte, so crawlers do not burn their budget on markup.

10

Chunkability

Whether your content is in clean, coherent blocks that embed well rather than as one undivided mass.

11

Blocking overlays

Cookie walls and modals that an agent cannot dismiss, causing it to read the popup instead of your content.

12

Content traps

Content locked in PDFs or images without text alternatives, invisible to machines.

13

Agent traps

JavaScript-only links and parameter loops that send an autonomous crawler down dead ends.

14

Mobile parity

Whether your mobile version shows the same content as desktop, since mobile is what often gets indexed.

Sample readout

example scan · illustrative
62/ 100
GRADE C · AI READINESS
JavaScript dependency
38% of content is JS-injected, invisible to non-rendering crawlers
5 / 13
llms.txt standard
No llms.txt at domain root
0 / 6
!
Mobile parity
Mobile shows 71% of desktop text
4 / 8
!
Structured metadata
Open Graph present, no valid JSON-LD
3 / 8
Semantic HTML
main, article, single h1 present
9 / 9
Canonical tags
Protects against duplicate embedding
6 / 6
Remediation locked

Get the fixes as agent-ready prompts

Each failed check comes with a tested remediation prompt you paste straight into your coding agent. Stop guessing what to fix and hand your developer the exact instructions.

Unlock remediation →