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 branch to open itHow the score is built
No black box. Every check lands in one of five states, each category is the weighted average of its own graded checks, and the headline score is the weighted average of the six categories — so you can always trace a number back to the checks underneath it.
What we check, and why it matters 💡
Every term below shows up somewhere in your report. None of them are as technical as they sound — here is what each one actually is, and what it costs you when it's wrong. If you're handing the report to a developer, this is the part worth reading first so you know what you're asking for.
The padlock in the address bar. It encrypts whatever visitors send you and proves the site really is yours.
Without it Chrome labels the page “Not secure” before anyone reads a word, forms get flagged, and Google counts HTTPS as a ranking signal. Certificates are free now — the usual problem is one that quietly expired.Google's three speed measurements: how fast the main content appears, how much the layout jumps while loading, and how quickly the page reacts to a tap.
They're a genuine ranking factor, but the bigger cost is invisible — on mobile a large share of visitors leave before a slow page has finished loading, and you never see them in your analytics.The blue link in Google, and the grey text underneath it. You write both.
They decide whether someone clicks your result or the one below it. Google cuts them off by width rather than character count, which is why this report measures the title in pixels.Two files at your domain root. One tells search engines where they may go; the other lists every page you want found.
A page missing from the sitemap has to be discovered through internal links alone, and a single stray line in robots.txt can hide an entire section of the site from search without any other symptom.A tag that names the one official address for a page.
Without it, the same page reached through a tracking link, a trailing slash, or www versus non-www can be treated as several competing pages — splitting the ranking strength that should all be pointing at one.The picture and headline that appear when your link is pasted into WhatsApp, LinkedIn, Slack or X.
Set it and your link becomes a card with artwork. Leave it and the same link arrives as a bare grey URL that noticeably fewer people click — for the sake of one tag and a 1200×630 image.Google ranks your site on the mobile version, not the desktop one.
A layout that looks right on a laptop and cramped on a phone is judged on the phone. That's why the viewport tag and responsive breakpoints carry real weight in the score rather than being a nicety.Links pointing at pages that no longer answer.
Each one drops a visitor at a dead end and wastes the credibility you passed along to it. They appear on their own over time as other sites reorganise, which is why they're worth re-checking rather than fixing once.Hidden, machine-readable notes telling Google what a page is — an article, a product, a list of questions.
This is what earns star ratings, FAQ dropdowns and breadcrumb trails in the results. It's extra space on the search page that competitors without it simply don't get.A short written description attached to each picture.
Screen readers read it aloud, so it's an accessibility requirement in most places — and it's the only way Google knows what an image shows, which is what puts you in image search.Instructions sending one address to another, usually left behind after a page moves.
One hop is normal. A chain of them slows every visit and leaks a little authority at each step, and it's the sort of thing that quietly accumulates through years of site changes.Backlinks, keyword rankings and competitor comparisons need a paid index of the entire web.
We'd rather leave those blank and say so than show you a plausible-looking guess. Everything you do see here was measured against your live page at the moment you asked.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.