SEO Checker

What it costs you when this is wrong

• The page quietly leaves the index

  One stray noindex removes a page from search completely, and it can arrive as an X-Robots-Tag response header that is invisible when you view the source. Most people find out weeks later from a traffic graph, because a de-indexed page still loads perfectly for anyone who visits it directly.

• The wrong URL ends up ranking

  A relative canonical resolves against the current page, so it silently self-canonicalises and consolidates nothing; two conflicting canonicals are ignored altogether. You end up with the parameterised or duplicated copy competing against the version you actually wrote for.

• You rank, and still lose the click

  A title much over 60 characters is cut mid-word in results, and a page with no Open Graph image posts to Slack, WhatsApp or LinkedIn as a bare grey box with a domain name on it. The position is fine, the click never happens, and nothing in your analytics tells you why.

Why run it here

• The weighting is published, not a black box

  The check list here is much the same as everyone else's - titles, canonicals, indexability, links. The weighting is not: impact is importance times a confidence tier, both published per rule, so the same page scanned twice returns the same number and you can see why a finding weighs what it does.

• No model gets a vote on your score

  The optional AI layer can only return prose. It has no scan context field to write to, it runs after every status and impact is already final, and it can add an explanation beside a finding but never the finding itself.

• A blocked link is not a broken link

  Links on the page are actually requested, and the answers are sorted three ways. Only 404 and 410 count against you; a 5xx weighs less because it may be transient; a 401, 403, 429 or timeout - usually bot protection refusing an automated request - is reported and never scored.

This check runs on its own here, and as part of the full audit alongside the other 985 rules. Either way the findings carry their evidence and their citation, and the report is never published or kept.

1. 1

   Give every page a unique title under about 60 characters that leads with the term the page is about.

2. 2

   Write a distinct meta description per page. Duplicated descriptions are how a site ends up with one page competing against its own.

3. 3

   Use exactly one <h1> per page, describing that page rather than the site.

4. 4

   Add a self-referencing canonical to every indexable page so parameter and tracking variants consolidate.

5. 5

   Confirm the page is reachable — not disallowed in robots.txt, not carrying noindex, and linked from somewhere in your own navigation.

1. 1

   Enter your address

   Just the domain is enough — example.com, with or without the https. No account, no card, no crawl of your whole site.

2. 2

   We render it like a visitor

   Your page opens in a real browser and JavaScript runs to completion, so what gets audited is the page a person actually sees — not the raw HTML your server sent. A screenshot comes back with the report as evidence of exactly what we measured.

3. 3

   You get findings you can act on

   Up to 986 checks run against that rendered page. Each finding names the rule, quotes the evidence found on your page, cites the public specification behind it, and says what to change. Nothing is a judgement call — run it twice on an unchanged page and the score is identical.

What runs this check

• Real browser rendering
• Live HTTP link resolution

Named because provenance is the product. Every finding in your report says which of these produced it, so you can check the reasoning rather than take a score on faith.

Also checks

This page answers these searches too — they are the same job, so they share one page rather than being split across near-identical ones:

• seo audit tool
• seo analyzer
• on page seo checker
• website seo checker

Other checkers

• HTML ValidatorW3C markup conformance, checked by a real parser
• CSS ValidatorStylesheets parsed and checked against the W3C property grammars
• Schema Markup ValidatorJSON-LD parsed, expanded to real schema.org IRIs, and checked
• Rich Results TestWhich search features your structured data qualifies for
• Website Scam DetectorThe trust signals people and payment processors check before believing a site
• AI ValidatorWhether AI models can find, read, quote and operate your site
• Broken Link CheckerEvery link on the page requested, with blocked and broken told apart
• Accessibility CheckerTwo WCAG engines — one in a real browser, one on your markup
• Security Headers CheckerResponse headers, CSP quality, and the TLS certificate underneath
• Core Web Vitals CheckerMeasured for real, plus the page-weight causes behind the numbers
• AI Agent Readiness CheckerCan an agent find your buttons, read your labels and finish the task
• W3C ValidatorMarkup and stylesheet conformance in one pass
• Answer Engine CheckerWhether AI answer engines can quote you, and attribute it
• AI Crawler CheckerWhich AI crawlers your robots.txt actually lets in
• SSL Certificate CheckerA real handshake: certificate, expiry, protocol and cipher
• robots.txt CheckerWhat your robots.txt actually allows, group by group
• Meta Tag CheckerTitles, descriptions, canonicals and robots directives
• Open Graph CheckerHow your link looks when someone shares it
• Image SEO CheckerAlt text, dimensions, formats and lazy loading
• Mobile-Friendly TestViewport, tap targets and responsive behaviour
• Website CheckerEvery module, one scan, one prioritised fix list