Transparent methodology · version 2.0

What the website health check measures.

The free check is a focused review of public signals on one page and a small set of root files. It is designed to surface useful first actions—not to replace a full technical, content, accessibility or search audit.

How to read the result

A high score means the scanner detected the weighted public signals listed below. It does not guarantee rankings, traffic, accessibility, legal compliance or correct analytics data. A low score is a prioritisation aid, not a final diagnosis.

Scoring model

Each scorable signal has a published weight. A pass earns the full weight, a warning earns half, and a fail earns none. Signals that are optional, unavailable or not publicly verifiable are excluded from the denominator, so they do not silently reduce the score.

SignalWeightWhat is detected
HTTPS18The final scanned page is available over HTTPS.
Mobile viewport12A responsive width=device-width viewport setting.
robots.txt8A root robots file with recognisable crawler directives.
sitemap.xml10A root XML sitemap or sitemap index.
Favicon3An icon link in the page or a root favicon response.
Page title16A descriptive title with a practical length check.
Meta description10A page description with a practical length check.
Structured data7Parseable JSON-LD or schema microdata.
Google Analytics 44A GA4 identifier or recognised public implementation signal.
Google Tag Manager0Reported for information only; GTM is not a ranking requirement.
Search Console verification0An HTML verification tag, when public. DNS and other methods cannot be confirmed here.

Status definitions

  • PassThe expected public signal was detected.
  • ReviewThe signal was present but may need improvement; half of its weight is awarded.
  • FailThe scorable signal was not detected or did not meet the published check.
  • UnavailableThe scanner could not verify the signal. It is excluded from scoring.
  • Not checkedThe signal cannot be reliably proved from public page data. It is excluded from scoring.
  • OptionalThe signal is useful in some setups but is not a universal requirement. It is excluded from scoring.

What is reviewed

The requested public page, its final redirect destination, /robots.txt, /sitemap.xml and a favicon fallback. The check reads public responses only.

What is not reviewed

Search Console or analytics account data, server logs, every page on the site, Core Web Vitals field data, content quality, backlink quality, accessibility conformance or legal compliance.

Known limitations

Public detection can produce false negatives when tags load only after consent or through client-side code. A detected tag confirms presence, not correct configuration or data quality. A root-file check does not prove every URL can be crawled or indexed. Search performance also depends on relevance, competition, authority, location and many signals outside this snapshot.

For a broader diagnosis, request a deeper audit with competitor and target-market context.

Request a deeper audit