Monitoring
Between audits, Horavo keeps watching.
An audit is a snapshot. Monitoring covers the time in between: score trends against benchmark bands, polite probes that catch incidents within hours, and a changelog that ties score movement to what changed on the store.
A trend line, with something to compare it to.
Every run saves all thirteen category scores, so the trend chart starts working from your second audit. A p25–p75 band built from anonymised stores shows where you stand. Those are real aggregates with a minimum sample size, not an invented benchmark.
- General Setup91, up from 82
- SEO74, up from 66
- AEO58, up from 41
- Internal Links83, up from 71
- Search & navigation71, up from 63
- Performance61, up from 60
- Images & media64, up from 55
- Accessibility79, up from 65
- CRO66, up from 52
- Catalog72, up from 68
- Compliance & trust68, up from 61
Sample data · scores are 0–100 per category, per run.
- Storefront reachableok
- No site-wide noindexok
- robots.txt not blockingok
- Sitemap presentok
- TLS certificateexpires in 9 days
- Catalog sizeok
The incidents that can't wait for the next audit.
A theme update that flips on a site-wide noindex costs rankings by the day. Watch probes run politely on their own schedule, confirm twice before opening an incident, and alert you when something that matters breaks, then again when it's back.
When a score moves, see what moved it.
Each run fingerprints the theme, the third-party scripts and the navigation. When something changes between runs, it lands in the store's changelog next to the score movement, so “Performance dropped four points” arrives with a likely cause attached.
- May 12Theme updated: Dawn 12.1 → 13.0−4 Performance
- May 9New script: judge.me reviews widget+3 CRO
- May 2Main navigation restructured+2 Search & navigation
Everything monitoring covers
- Score history per category, from the very first run
- A p25–p75 benchmark band from anonymised stores, never an invented number
- A percentile chip on every score tile
- Store Watch probes on their own schedule, independent of audits
- Incidents open and resolve with alerts: downtime, password wall, noindex, robots blocking, missing sitemap, catalog shrink, slowness, TLS expiry, theme changes
- Run diffs: fixed, new and persisting findings between any two runs
- Preview vs live: audit an unpublished theme or a password-protected store
- Recurring audit schedules: cadence, day, hour, category subset
- A weekly digest email with scores and the current plan
- Shareable, redacted report links (print one if you need a PDF)
Your store changes every week. Know what it cost.
Audit once for the board. Keep monitoring on for the trend, the incidents and the changelog.