The Monitoring module periodically checks chosen URLs and reports meaningful changes: downtime, HTTP errors, HTTPS issues, Insight score regressions and new technical risks. It is early warning — not full infrastructure observability or a 24/7 uptime guarantee.
A one-off audit shows how things are now. Monitoring shows when something got worse.
Sites break for more than big releases — a CMS update, expired certificate or new marketing script is enough. The module compares results over time and flags regressions — with no promise it fixes problems or replaces DevOps.
Four steps from a URL list to a response — without checking everything by hand every day and without a full observability stack promise.
HTTP status, 4xx/5xx errors, redirects and key page responses.
Drops in Performance, SEO, Accessibility, Security and Ecology vs previous scan.
Dated events: certificate, noindex, 500 error, new technical issues.
You add the homepage and key pages. Monitoring checks availability, HTTP status and basic technical signals — on a schedule, not in real time.
Insight compares current results with previous measurements: Performance, SEO, Accessibility, Security and Ecology. You see whether something dropped after a deploy or a new issue appeared.
Meaningful changes land in an event list with date and context: 500 errors, accidental noindex, expiring certificate, score drop. Not every alert is critical — the module helps separate urgent from observational.
After a fix you return to history and check whether the issue cleared. Monitoring does not repair the site — it helps you notice sooner when attention is needed.
System status
Every monitored URL has an unambiguous status and check history. You see not just "is it up", but response times and when the status changed.
SSL certificate
Certificate validity and trust chain monitoring with warning thresholds. You get the signal early — before browsers start scaring your client's customers.
JavaScript errors
The page renders in a real browser (Playwright) and monitoring collects console errors, exceptions and failed resources. A form can look fine and not work — this catches exactly those cases.
SLA and alerts
Uptime set against your SLA threshold: above, at the limit, below. Alerts go where you work — and a report with incident history is ready for the client meeting.
No. Monitoring in Insight focuses on the website and publicly visible signals: availability, HTTP status, technical quality and analysis score changes. It does not cover server logs, databases, backend or business transactions.
No. It reports detected issues and regressions — helping you react sooner — but does not prevent outages or replace an administrator. There is no SLA or zero-downtime guarantee.
No. SEO regressions cover technical site signals — e.g. noindex, canonical, metadata. Keyword rank tracking and SERP visibility are a separate module when available on your plan.
On a schedule — per your plan and scan frequency settings. It is not per-second real-time monitoring; the module compares results between successive Insight measurements.
No. It shows events, regressions and change history — decisions and fixes stay on your side. Monitoring is early warning, not automatic rollback.
One scan shows what is worth fixing. No card, no commitment — results in about 2 minutes.
