Reading your Site Check report
How to read the overall score, the per-area findings, and the AI fix prompts in your report.
# Reading your Site Check report
We **walk** your site in a real cloud browser — clicking through it like a user —
then report on the pages we actually visited. Nothing here is guessed from a
single homepage fetch.
## The headline score
At the top you get an overall score and a **verdict** (pass / warn / fail — or
*blocked* if a firewall stopped the walk). The score rolls up the areas below;
open each area for the detail behind it.
## The areas we check
- **Security** — TLS, security headers, cookie flags, mixed content, CSRF on
forms, auth tokens leaking in URLs.
- **SEO** — titles, meta, headings, crawlability across the pages walked.
- **Tech stack** — framework, CDN, hosting, and any bot-protection vendor.
- **Personal-data collection** — what PII your forms ask users for.
- **Pages walked** — every URL we visited, with its title and HTTP status.
## AI fix prompts
Every finding comes with a **paste-ready prompt** for your AI builder
(Lovable, v0, Bolt, Cursor, Replit). Copy it back into the tool that built the
site and it'll know exactly what to change.
## What's not in the free report
Performance is a paid upgrade (L2). We never show made-up performance numbers —
if no load test ran, there's no perf section. See *Your scan report — what L1,
L2 and L3 show* for the full tier breakdown.
Tags: report, reading the report, score, findings, sections, results, what does it mean, fix prompts