Incident Reports
Incidents with Evidence, Not Guesswork
When something breaks, "what happened?" needs a real answer — not a shrug. Every Sitewatch incident is a complete record: what broke, which pages it affected, how serious it is, and a step-by-step fix. It's written so your team can act on it immediately — or hand it straight to a client.
- Every incident sorted by type and seriousness, automatically
- A full timeline, from detection through to resolution
- A step-by-step fix, tailored to what actually broke
01Why it matters
Every incident tells the full story
Know exactly what failed
Every incident is sorted into a clear type — a missing file, a redirect loop, a page that moved, an outage — so you know what failed and why at a glance, not after an hour of digging.
Step-by-step fix checklists
Each incident comes with a tailored fix guide. Your team knows exactly what to do next, even without deep technical context on the specific failure.
See where a redirect went wrong
When a redirect breaks, Sitewatch shows the full path a visitor takes and pinpoints the loop — so you can trace exactly where it went wrong.
A complete timeline
Every step — from detection to confirmation to resolution — is logged with timestamps and reasons. A clear audit trail you can show anyone.
Ranked by seriousness
Incidents are auto-ranked Critical, High, or Medium. A page stuck in a redirect loop or fully down is Critical; a missing file is High; a smaller issue is Medium — so your team fixes the right thing first.
Resolution tracked automatically
When the next clean check confirms the issue is gone, the incident resolves itself. The timeline records exactly when the fix took effect, giving you a clear before-and-after.
Reports written for you
When an incident resolves, Sitewatch generates a client-ready report with the timeline, evidence, and resolution — no manual writing required.
Client or technical version
Choose a client-facing summary (plain-English, focused on business impact) or a technical version with the full evidence — depending on who's reading.
Branded PDF export
Export any incident report as a PDF with your agency logo and colors. Share with clients by email or attach it to your project tools.
6
Incident types documented
Up to 90 days
Data retention
100%
Incidents with evidence
02Comprehensive evidence
What every incident record contains
Failure details & evidence
- The exact type of failure — a missing file, a redirect loop, a page that moved, an outage
- The specific file or page that failed, and how it failed
- The full redirect path, with the loop pinpointed when there is one
- The page where the failure was detected
- A fingerprint that keeps one problem from creating duplicate incidents
Timeline, severity & remediation
- How serious it is — Critical, High, or Medium
- A timeline logging every step, from detection to resolution, with timestamps and reasons
- The exact check that caught it, so you can trace the context
- A fix checklist tailored to what actually broke
- Automatic resolution when a clean check confirms the issue is gone
03Shareable reports
Share evidence with anyone — no login required
Single incident reports
Generate a private share link for any incident. Recipients see the full story — what failed, which pages, the timeline, and the fix — without needing a Sitewatch account.
Bundle reports
Group 2–10 related incidents into one report link. Send a client a single link covering everything found this week instead of forwarding individual alerts.
Business impact context
Add a short business-impact note before sharing, so the recipient understands the stakes — not just the technical details.
Access control
Set an expiry date or revoke access instantly. Control who sees what, and for how long. Expired links show a clear "report unavailable" message.
04Automatic documentation
From detection to documented evidence
- 01
Issue detected
Sitewatch catches a broken file, a redirect loop, a page served the wrong way, a page that moved, or an outage during a scheduled or on-demand check.
- 02
Incident created with evidence
An incident is created with the details: the affected page, exactly what failed, and how serious it is — sorted and ranked automatically.
- 03
Fix checklist attached
A tailored fix guide is attached based on what broke, giving your team a clear path to resolution without guessing.
- 04
Resolution tracked automatically
When the next clean check no longer finds the issue, the incident resolves itself. The timeline records when the fix took effect.
Stop guessing what broke
Free plan with 7-day data retention. Every incident documented automatically. No credit card required.
05Why Sitewatch
Sitewatch incidents vs generic uptime alerts
| Scenario | Generic uptime alerts | Sitewatch |
|---|---|---|
| What failed | "Site is down" | Named failures: a missing file, a redirect loop, a page that moved, and more |
| Event timeline | Single alert timestamp | Full history of every step, with timestamps and reasons |
| Seriousness | Manual tagging | Auto-ranked Critical, High, or Medium |
| Detail of what broke | None | The exact pages and files that failed, and how |
| How to fix it | None | A fix checklist tailored to what broke |
| Resolution tracking | Manual close | Auto-resolved when a clean check confirms the fix |
What failed
- Generic uptime alerts:
- "Site is down"
- Sitewatch:
- Named failures: a missing file, a redirect loop, a page that moved, and more
Event timeline
- Generic uptime alerts:
- Single alert timestamp
- Sitewatch:
- Full history of every step, with timestamps and reasons
Seriousness
- Generic uptime alerts:
- Manual tagging
- Sitewatch:
- Auto-ranked Critical, High, or Medium
Detail of what broke
- Generic uptime alerts:
- None
- Sitewatch:
- The exact pages and files that failed, and how
How to fix it
- Generic uptime alerts:
- None
- Sitewatch:
- A fix checklist tailored to what broke
Resolution tracking
- Generic uptime alerts:
- Manual close
- Sitewatch:
- Auto-resolved when a clean check confirms the fix
06FAQ
Frequently asked questions
Sitewatch catches six kinds of failure. A redirect loop or a full outage is treated as Critical; a missing file or a file served the wrong way is High; a page that has moved or returns the wrong kind of content is Medium. Each type includes the specific evidence relevant to that failure.
Each incident includes what failed, how serious it is, the specific file or page affected, and where it was detected. Depending on the failure, you also get the full redirect path (with the loop pinpointed), what was expected versus what was served, and a sample of the response. Every step is logged in the 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 and fix checklists.
When a scheduled or on-demand check runs and no longer finds a previously open incident, Sitewatch resolves it automatically. The timeline records the resolution with the exact check and timestamp, giving you a clear record of when the fix took effect.
Each incident comes with a tailored fix guide. A redirect-loop incident, for example, walks you through finding the source of the loop, checking the 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 private share link for any incident or group of incidents. Recipients see the full story without logging in. You can optionally add password protection, set an expiry date, or revoke access at any time.
Bundle reports let you group 2–10 related incidents into a single shareable link. Add a business-impact note 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 page shows all the evidence, the timeline, and the fix in a clear format. For external sharing, generate a public report link — recipients see the full story without a Sitewatch account. Bundle several incidents into one report and add business-impact context before sharing.
07Explore more