Sonar

Methodology

A score with
an explanation.

Sonar technical health is a weighted checklist for fetched pages. It is not a search-engine ranking signal.

How a page score is calculated

Each applicable check has a weight. Passed checks earn their full weight. Notices earn 70% of the available weight. Warnings and errors earn zero. A page score is 100 × earned weight ÷ available weight. Failed HTTP fetches score zero.

How the site score is calculated

The site score is the rounded average of fetched page scores. For an illustrative two-page sample scoring 90 and 70, the average is 80. These are example numbers, not a report about a real website. Combining all raw check weights can produce a different result because pages are normalized separately.

Scope changes the evidence

Sonar reads original returned HTML and respects applicable robots rules. It does not render site JavaScript. Reports cover the pages actually fetched within the displayed scope and current limits. A missing incoming link in that sample makes a page an orphan candidate, not proof that no link exists anywhere on the site.

Separate data sources stay separate

Crawler response timing is not a Core Web Vital. PageSpeed or Lighthouse results come from their stated provider or import. Search Console data describes an authorized property, not global keyword demand. Local keyword intent and content heuristics are inferences, not measured search volumes or predictions of traffic.

Badges and security limits

Public badges identify the sampled technical audit and its current verification status. They are not a malware-free claim, independent certification or guarantee that an application is safe. Owner-authorized security indicators require separate interpretation. Read the current badge record for its evidence and expiry.

Use results responsibly

Follow the audit workflow or investigate internal links.