// docs / what mykavo monitors //
How severity is decided
MyKavo scores every change from INFO to CRITICAL using a central, deterministic rules engine - not a model and not a per-check guess. The same change always produces the same severity, which is what makes the number worth acting on and what lets you filter alerts by it without missing things.
Last updated: September 20, 2026
The five levels
| Severity | Means | Examples |
|---|---|---|
| CRITICAL | The page is broken or has been removed from search. | 200 becomes 404 or 500; index becomes noindex; a critical conversion element is missing. |
| HIGH | Something important changed that probably was not intended. | Canonical tag removed or changed; title removed; analytics script disappeared; redirect destination changed. |
| MEDIUM | A meaningful change worth a look. | Title changed; a new redirect appeared; page weight up more than 20%. |
| LOW | A small change, usually benign. | Meta description edited; minor copy change. |
| INFO | Recorded for history, not worth interrupting you. | Tiny visual differences below the noise threshold. |
Why the rules are central
Severity lives in one rules engine rather than being decided inside each check. That means it is testable, it is consistent between categories, and changing how seriously MyKavo treats something is a single deliberate edit rather than a hunt through the codebase. It also means the score is explainable: there is a rule behind it you can be told about.
Visual difference is an input, not the answer
A large pixel difference does not automatically mean a high severity, and a small one does not mean a low one. A 2% visual difference that removed your checkout button matters far more than a 40% difference caused by a new hero image. Visual difference percentage feeds the severity engine alongside everything else rather than deciding it.