From URL to certified in six steps.
Most founders see their first score in under two minutes. Here's what happens at each step, what's automated, and what's up to you.
- 01~90 seconds
Scan
Enter your URL. A headless browser loads the page the way a first-time visitor would, and Google's Lighthouse runs alongside it.
- You
- Paste one URL. No account needed.
- Automated
- Page load, DOM facts, Lighthouse audits, robots.txt and 404 probe.
- 02instant
Score
31 rule-based checks across 8 dimensions produce one score out of 100 and a launch verdict.
- You
- Read the verdict and the dimension bars.
- Automated
- Every check, every weight, the verdict bands and the blocker cap.
- 03instant
Prioritise
Findings are ordered by severity, then impact, then effort: launch blockers first, then high-impact fixes, then quick wins under an hour.
- You
- Decide what to do today.
- Automated
- Severity (P0–P3), impact and effort per finding; the fix-first list.
- 04you set the pace
Fix
Each finding says why it matters, how to fix it, and the technical detail underneath — written for the person who decides, with the detail for the person who implements.
- You
- Make the changes on your site (or hand the Markdown export to whoever will).
- Automated
- Nothing. We never touch your site.
- 05~90 seconds
Rescan
Run it again on the same standard and see exactly what moved. Score history is kept per site so improvement is provable, not a feeling.
- You
- Click rescan. Mark things as fixed if you like.
- Automated
- Before/after comparison, what changed between scans.
- 06when you clear the bar
Certify
Score 90 or more with zero blockers and you can opt in to a public certificate page and an embeddable badge that links to your breakdown.
- You
- Opt in. Add the badge to your site if you want.
- Automated
- Certificate page, badge SVG, listing on the certified sites page.
What the scanner reads — and what it never touches.
- The one public page you submit, plus its HTML, metadata and linked assets — exactly what a browser downloads.
- A Lighthouse run from Google's PageSpeed Insights API (performance, accessibility, SEO, best practices).
- Your robots.txt, and one request to a random path to confirm you return a real 404.
- Up to 10 MB per page, with a hard time limit. Our crawler identifies itself as LaunchGradedBot.
Error states we handle honestly.
A scan that can't complete tells you why and what to do next. It is never silently scored as a zero.
- Site unreachable
- DNS fails, the server times out or refuses the connection. We say so and suggest checking the URL or trying again.
- Blocked by robots.txt
- If your robots.txt disallows LaunchGradedBot we stop, tell you, and explain how to allow us.
- Password-protected or behind a login
- We only read public pages. If the URL redirects to a login we report that rather than scoring the login screen.
- Page too large or too slow
- Pages over 10 MB or that don't finish loading in time are reported as such, not scored badly.
- Lighthouse unavailable
- If Google's PageSpeed API is down we retry, then report the performance checks as unavailable rather than failing them.