// docs / getting started //
Reading a change and deciding what to do
Every change tells you what changed, where, when, what it was before, what it is now, and how severe MyKavo thinks it is. You then either approve it - making the new state the baseline - or treat it as a regression, fix the site and rescan. Approving is not dismissing: it moves the reference point.
Last updated: September 20, 2026
What a change record contains
| Field | What it tells you |
|---|---|
| Category | Availability, visual, SEO, content, links, script, performance or conversion. |
| Severity | INFO through CRITICAL, from a central rules engine rather than a per-check guess. |
| Page | The exact URL the change was found on. |
| Previous value | What the baseline recorded - the actual old title, canonical, status code or screenshot. |
| Current value | What this scan found instead. |
| Detected at | When the scan that found it ran. |
| Evidence | For visual changes, the before and after screenshots and a pixel diff image. |
Approve, or fix
Approving a change means "this was intentional". The current state becomes the new approved baseline, the change stops appearing as open, and future scans compare against the new state. Use it after a redesign, a deliberate copy change, or a planned price update.
If a change was not intentional, it is a regression. Fix the site, then run a scan. When the page matches the baseline again the change resolves. Nothing is silently discarded - the history stays, which is what makes it possible to answer "when did this break?" weeks later.