Every SEO problem on your page, in one report.
Enter a URL and get a complete audit — every check measured live against your real page, each with what we found, why it matters, the fix, and exactly how many points it's worth.
What makes up that score
weighted average of six groups · click any to openWhere each number comes from 💻
On-page checks only need the HTML, so they come back in about a second. Everything below needs its own network request, a real page load or a crawl — so the report opens on the fast half and fills in the rest as it lands. Nothing is estimated to fill a gap: a check that can't run says so, and is left out of the score entirely.
Your browser can't read another site's HTML, so we fetch it server-side, follow every redirect and record the final status and headers.
LCP, CLS and INP need the page actually rendered. We run it through Google's PageSpeed Insights and pull the request waterfall and savings list back with it.
Both live at the domain root. We fetch them, check whether this exact URL is allowed, and whether it's actually listed in the sitemap.
Issuer, validity window and days to expiry come from the TLS handshake, which JavaScript cannot inspect.
Every link on the page gets its own request to see whether it still resolves. Capped at 30 per audit.
We fetch the first bytes of your og:image and read its real pixel size out of the file header, rather than trusting the tag.
Sampled scripts, stylesheets and images are probed for size, cache headers and whether they look minified.
Backlinks, rankings and competitor data need a paid index of the whole web. We'd rather leave them out than show you a plausible-looking guess.
The URL isn't logged against you and the report isn't saved. Close the tab and it's gone — use the JSON or CSV export to keep it.
Common questions
How is this different from the detailed SEO checker?
Same underlying question, different report. /seo-checker-detailed gives you sixty tests grouped into seven flat categories — a thorough checklist. This page weights those groups into one score, works out how many points each individual fix is worth, orders them into a plan you can work top-down, and adds a live Google and social preview, a request waterfall and a link crawl. Neither replaces the other.
What does the "+N pts" on each fix actually mean?
Exactly what it says: the amount the headline score rises if you fix that one item. It's derived from the check's weight inside its category and that category's weight in the total — so the numbers in the plan add up to the gap between your current score and the potential one, rather than being decorative.
Why does the score move while I'm reading it?
Because the deeper checks are still landing. The link crawl, certificate check and Lighthouse run take far longer than reading the HTML, so the report opens on the ~50 on-page findings and merges the rest in as each one finishes. A check that hasn't finished is excluded from the score rather than counted as a pass, which is why it usually settles slightly rather than jumping.
Does a 100% score guarantee I'll rank first?
No, and be wary of any tool that implies otherwise. This audits the technical foundation — the things objectively measurable from your page. Ranking also depends on content quality, search intent, competition and domain authority, none of which a page-level crawler can judge.
Can I audit a staging or password-protected site?
Only if it's reachable from the public internet without credentials. We fetch the page from our server, so anything behind a login, a VPN or an IP allowlist won't resolve. Local and private addresses are blocked by design.
Why are some checks marked "not available"?
Because they genuinely couldn't run — a probe was blocked, a module timed out, or the check needs an API key this deployment doesn't have. They're excluded from the score in both directions. A tool that quietly counted them as passes would flatter every site it couldn't fully reach.