Availability and trust
Homepage and priority-page availability, HTTPS behavior, certificate status, redirect consistency, and visible browser trust signals.
A website can pass an audit and still regress after a redesign, plugin update, DNS change, content release, or form edit. Security Watch checks agreed public signals on a recurring schedule and reports what is new, fixed, recurring, or accepted.
The baseline is agreed after an audit or onboarding review so monitoring stays relevant to the website and its business goal.
Homepage and priority-page availability, HTTPS behavior, certificate status, redirect consistency, and visible browser trust signals.
Robots directives, sitemap availability, selected canonical signals, priority metadata, and page-status changes that can affect discoverability.
Public form availability, important calls to action, agreed navigation routes, and obvious changes that may interrupt inquiries or purchases.
The report is designed to help an owner decide whether to observe, fix, or escalate a change.
| Status | Meaning | Client action |
|---|---|---|
| New | A monitored signal changed or a new public risk appeared since the previous review. | Review the evidence and approve remediation or deeper investigation. |
| Fixed | A previously recorded issue is no longer visible in the scheduled public check. | Keep the evidence as a verified improvement. |
| Recurring | An issue returned after being fixed or remains present across review periods. | Investigate the release, process, or ownership causing the regression. |
| Accepted | The owner has documented a known limitation or deferred change. | Monitor the risk and review the decision at the agreed date. |
The entry plan is intentionally clear so the client knows what is monitored and what requires a custom scope.
The homepage plus a small agreed set of priority pages, forms, and buyer paths.
Scheduled comparison of public availability, certificate, DNS basics, headers, index controls, and selected page signals.
A concise report of changes, evidence, business relevance, and recommended next action.
Recurring public monitoring should not be confused with continuous security operations or managed hosting.
The service does not provide continuous threat detection, emergency response, or around-the-clock analysts.
Incident investigation, cleanup, forensics, and recovery require a separate qualified response engagement.
We do not change DNS, hosting, code, plugins, or forms without a separate owner-approved scope.
Security Watch works best after the initial condition of the domain and website has been documented.
We will review the public scope and confirm whether the $99 baseline or a custom monitoring plan fits.