Deploy verification
"Deploy Succeeded" Is Not the Same as "Site Works"
Every deploy is a risk. A green CI build only tells you the code compiled — not that your site actually works in production. Sitewatch verifies after every deployment with a structured pass/fail/degraded verdict and a before/after comparison showing exactly what changed. No Playwright scripts, no flaky E2E suites — just paste a webhook URL and get a verified report within seconds of every ship.
- Structured pass/fail/degraded verdict after every deploy
- Before/after asset diff showing exactly what changed
- Zero-config webhook — paste a URL and you're done
Deploy completed
3:42 PM
Verification checks running
14 checks across 6 pages
Asset diff calculated
2 changed, 0 missing
Verdict: pass
2 non-breaking changes
Why deploy verification
Know your deploy actually worked — not just that it shipped
Pass/fail/degraded verdict
Every deploy gets a structured verdict — pass, fail, or degraded — so your team knows immediately whether the release is healthy without reading through logs.
Before/after diff
See exactly what changed between the previous and current deploy: new assets, removed scripts, changed bundles, modified headers — all in a single comparison view.
Zero-config webhook
Paste one webhook URL into your CI/CD platform. No test scripts to write, no browser automation to maintain, no flaky E2E suites to babysit.
Works with any CI/CD platform
Vercel, Netlify, GitHub Actions, GitLab CI, Bitbucket Pipelines — anything that can fire a POST request triggers a verification report.
Incidents tagged with deploy context
When a deploy causes breakage, the resulting incident is automatically tagged with the deploy that triggered it — giving your team instant root cause context.
CDN propagation delay handling
Configure a delay between deploy completion and verification check so CDN caches have time to propagate. No false positives from stale edge nodes.
10
Deploy hooks on Pro plan
4+
CI/CD platforms supported
Before/after
Asset diff on every deploy
How it works
From deploy to verified verdict in four steps
Deploy fires webhook
Your CI/CD platform sends a POST request to your Sitewatch deploy hook URL the moment the deploy completes.
Verification checks run
Sitewatch waits for the configured propagation delay, then runs a full check suite across all monitored pages — assets, scripts, headers, performance, and more.
Before/after compared
The current check results are compared against the pre-deploy baseline. New, changed, and removed assets are identified and classified.
Verdict delivered
A structured pass/fail/degraded verdict is generated and pushed to your alert channels — Slack, email, webhook, or dashboard — with the full diff attached.
The difference
Deploying blind vs. with deploy verification
| Feature | Without deploy verification | With Sitewatch |
|---|---|---|
| How you learn something broke | User reports or next scheduled check | Structured verdict within seconds of deploy |
| Debug context | Dig through logs and deploys manually | Before/after diff with deploy tagged to incident |
| Time to detect | Minutes to hours | Under 60 seconds post-deploy |
| Effort required | Write and maintain E2E test scripts | Paste one webhook URL — zero config |
How you learn something broke
Debug context
Time to detect
Effort required
FAQ
Frequently asked questions
A deploy verification report is a structured summary generated after every deploy. It includes a pass/fail/degraded verdict, a before/after comparison of assets and checks, and links to any incidents created as a result of the deploy.
Sitewatch keeps a baseline snapshot of your site's assets, scripts, headers, and performance metrics. After a deploy triggers a new check, the results are compared against the baseline. You see exactly what was added, removed, or changed — including bundle hashes, missing files, and new scripts.
Deploy verification works with Vercel, Netlify, GitHub Actions, and any platform that can send a POST request to a webhook URL — including Bitbucket Pipelines, GitLab CI, CircleCI, and custom scripts.
Deploy hooks are the trigger mechanism — they fire a check when your deploy completes. Deploy verification reports are the output — the structured verdict and before/after diff generated from those checks. You need deploy hooks enabled to get verification reports.
The Starter plan includes 3 deploy hooks with 50 triggers per day. The Pro plan includes 10 deploy hooks with 200 triggers per day. Each hook can target a different site or environment, and every trigger generates a full verification report.
Explore more