Deploy Hooks
Deploy Hooks — Catch Breakage the Moment You Ship
Build output
bundlesHow it fails — The build renames or drops a file, so the page asks for something that no longer exists.
How Sitewatch detects it — Checks every file the page references immediately after the release lands.
CDN cache
propagationHow it fails — The CDN keeps serving the previous version, so some visitors get old code and some get new.
How Sitewatch detects it — Waits for propagation, then re-checks, so a stale cache is not mistaken for a broken deploy.
Critical pages
journeysHow it fails — The homepage survives the release and checkout does not, which nobody notices until sales stop.
How Sitewatch detects it — Verifies each important page separately on every deploy, not just the front door.
Redirects
routingHow it fails — A routing change sends visitors in circles or lands them somewhere unexpected.
How Sitewatch detects it — Follows the full path after each release and reports loops or wrong destinations.
Page output
integrityHow it fails — The release quietly changes what the page renders without technically breaking anything.
How Sitewatch detects it — Compares the page against the last good deploy and flags what changed.