Incidents with Evidence, Not Guesswork

Sitewatch detects six incident types: REDIRECT_LOOP and UNAVAILABLE (classified as Critical), ASSET_MISSING and ASSET_MIME_MISMATCH (High), and HOST_DRIFT and NON_HTML_PAGE (Medium). Each type includes specific evidence fields relevant to that failure.

Each incident includes the failure type, severity, affected asset URL, HTTP status code, and page URL. Depending on the type, you also get redirect chain details (each hop, final host, loop detection), expected vs actual content type, and a body prefix of the response. Every status transition is logged in the event timeline.

Retention varies by plan: Free retains incident data for 14 days, Starter for 30 days, and Pro for 90 days. All plans include the same evidence fields and fix checklists.

When a scheduled or on-demand check runs and no longer detects a previously open incident, Sitewatch automatically resolves it. The event timeline records the resolution with the associated check ID and timestamp, giving you a clear record of when the fix took effect.

Each incident type comes with a tailored remediation guide. For example, a REDIRECT_LOOP incident walks you through identifying the loop source, checking server configuration, and verifying the fix. These checklists help team members resolve issues even without deep technical knowledge of the specific failure.

Yes. Public reports let you generate a token-based shareable URL for any incident or group of incidents. Recipients see full evidence without needing to log in. You can optionally add password protection, set expiry dates, or revoke access at any time.

Bundle reports let you group 2-10 related incidents into a single shareable link. Add a business impact statement for context, set an optional expiry date, and send one link to your client instead of forwarding individual alerts. Ideal for weekly client reviews or post-deploy summaries.

Yes. The incident detail page shows all evidence, the event timeline, and the fix checklist in a clear format. For external sharing, generate a public report link — recipients see the full evidence without a Sitewatch account. Bundle multiple incidents into a single report and add business impact context before sharing.