Catch the launch-killers — robots.txt, noindex, SSL, sitemap, analytics, Core Web Vitals & WCAG — before you go live.
Enter your live domain to get the exact paths to check (robots.txt, sitemap.xml).
Self-attestation only — ticking a box says you verified it. The tool can't see your live site. Re-check robots.txt, noindex & SSL directly on the production URL.
This pre-launch checklist walks you through every step that flatlines organic traffic when it's skipped — the catastrophic robots.txt Disallow: / left over from staging, a stray noindex, a missing or expired SSL certificate, broken redirects, absent meta titles, an unsubmitted sitemap, dead analytics, failing Core Web Vitals, and WCAG accessibility gaps. It weights each item by severity, computes a launch-readiness score, and hard-gates the verdict: if any launch-blocker is still open, you'll see NOT READY no matter how high the percentage climbs.
https://example.com/robots.txt).You're launching https://acme.example. You tick almost everything — SSL valid, titles unique, GA4 firing, sitemap submitted — and hit 92%. But you haven't yet confirmed that robots.txt is clean. Because the "no site-wide Disallow: /" item is a Blocker and it's still unchecked, the headline reads NOT READY — 1 launch-blocker open and the score ring turns red. You open https://acme.example/robots.txt, find the staging Disallow: /, remove it, re-tick the item — and the verdict flips to READY TO LAUNCH — 100%. That single gate is the whole point: a 92% "looks done" score is exactly how a site ships fully de-indexed.
Shipping the staging robots.txt with a site-wide Disallow: / line, which tells Google not to crawl any page and de-indexes the entire site. A lingering noindex meta tag or X-Robots-Tag header does the same thing silently. This checklist flags both as launch-blockers that override your score.
Each item is weighted by severity — Blockers count most, then Critical, then Recommended — and the score is the weighted percentage of items you've verified. Items marked Not Applicable drop out of both numerator and denominator. If any Blocker is still unchecked the verdict is forced to NOT READY no matter how high the percentage is.
No. It's a self-attestation checklist: ticking a box asserts you verified that item yourself. The tool can't confirm the live state of your site, so treat the output as "based on what you've confirmed." Always re-verify the critical items (robots.txt, noindex, SSL) directly on the production URL.
As of the March 2026 core update: LCP under 2.0s (tightened from 2.5s), INP under 200ms, CLS under 0.1 — judged on the 75th percentile of real-user field data over 28 days, not a single Lighthouse lab run. Thresholds drift; re-verify against web.dev and Search Central.
WCAG 2.2 AA requires 4.5:1 for normal text and 3:1 for large text (18pt, or 14pt bold). Compare the unrounded ratio — 4.499:1 fails 4.5:1. Automated checks catch only ~30–50% of WCAG issues, so passing this is not a legal certification; a manual audit is still required.
Yes. Everything runs in your browser and your ticks, N/A marks, and the URL you enter are saved in localStorage, so a refresh won't wipe your checklist. Nothing is uploaded.
Everything runs in your browser — your checklist never leaves this device and nothing is sent to our servers. See our privacy policy.