AI Readiness
crawler-readable content, llms.txt, markdown extraction, agent discovery
AI crawler sees mostly empty HTML.Evidence-backed launch readiness scanner
Find launch blockers your agent can fix.
Paste a public URL. isitready.dev checks crawlability, metadata, headers, performance evidence, and launch hygiene, then returns a scored report with copyable fix prompts, re-scan proof, and paid monitoring when the work repeats.
Public URL only · http or https · Read-only, no login.
Read-only scanPublic signals onlyNo signup for core reportRe-scan proof after fixes
isitready.dev scores what a public scan can prove: files, headers, metadata, crawler access, performance evidence, and launch hygiene. The dashboard turns repeated reports into saved history, owned-data recommendations, and regression monitoring.
Evidence is labelled observed / heuristic / unavailable, then turned into weighted scoring with explicit gaps, no mystery math.
Public files and headers
The scan reads the surface your launch already exposes.
No repository. No admin login. The first report uses public URLs, response headers, metadata, and fetchable files.
- GET/200text/html
- GET/robots.txt200cache-control: public
- GET/sitemap.xml200142 URLs indexed
- GET/llms.txt404no AI index file
- HEAD/200hsts: present, csp: missing
- METAog:image–tag not found in <head>
Scan lifecycle
From URL to report.
The scan starts from the public URL, reads what can be verified, and returns the issues that should be fixed first.
- GET /robots.txt -> 200Fetch public surface
HTML, headers, robots.txt, sitemap, metadata, schema, and launch hygiene are read from the public web.
- 5 groups -> evidence rowsResolve readiness checks
Crawler visibility, SEO basics, security headers, performance evidence, and production details are scored with coverage.
- Fix prompt -> re-scanReturn fixes with proof
Each issue includes what failed, why it matters, affected targets, and a copyable fix prompt.
Checks
What the scan checks.
Each group shows the public signals used for scoring and one example of a blocker that changes the verdict.
Technical SEO
robots.txt, sitemap, canonical tags, titles, descriptions, structured data
Canonical points to staging.Security
HTTPS, CSP, HSTS, cookie flags, transport posture
No Content-Security-Policy header.Performance
public lab evidence, field data availability, asset weight, loading quality
Largest contentful paint is slow.Production Quality
status codes, favicon, Open Graph preview, metadata consistency
Social preview image missing.Evidence beats confidence.
The report separates verified findings from missing coverage instead of filling gaps with guessed authority metrics.
Public signals only
The scanner does not require ownership proof for the first report because it reads the same surface crawlers and users can reach.
Coverage shown with every score
Sampling and unavailable evidence are called out instead of being hidden behind one confident number.
No invented authority metrics
Reports use observed headers, files, metadata, public APIs, and scan evidence. Inconclusive results stay marked as inconclusive.
Paid product
Pay for continuity, not the first answer.
Catch regressions after every fix. Keep launch blockers from coming back with saved state, monitoring, owned search data, and metered deep work after the first report.
Free
Free
One useful report without a paywall.
- 10 scans / month
- 1 saved site
- 5 saved reports
- 1-month history
Pro
£8/mo
Keep launch issues from coming back.
- 100 scans / month
- 5 saved sites
- 100 saved reports
- 6-month history
- 25 premium usage credits
- Scheduled monitoring
- Public URL Control (5,000 URLs)
- Google Analytics imports
- Search Console imports
- Site profiles
Run the scan before launch.
Paste the production URL, review the blockers, and give your next fix pass real evidence.
Check a launch URL