Did my last deploy break my site?

Updated 2026-11-01

Short answer: a build that passes only proves the code built. It doesn't prove the live site works. Deploys often break things the build never sees: a redirect, a missing page, a script error in the browser, a security header, a noindex tag left on, or a DNS record changed alongside the deploy. The way to know is to check the live site after every deploy and compare it with before.

How to check it yourself

  1. Open the live site in a private window and load your main pages, not just the home page.
  2. Open the browser console (F12) and look for red errors.
  3. Check that http and www addresses still redirect to the right place, and that the padlock shows.
  4. If DNS or hosting changed in the same deploy, check your email still sends.

What Preventionlabs shows

Run a report after the deploy. "Changed since the last report" lists every check that moved, for example from fine to a problem, so you see what the deploy changed, not just what's wrong. The report covers pages, JavaScript errors in a real browser, redirects, HTTPS, security headers, noindex tags, DNS and email records. With a read-only Cloudflare token, it also lists Cloudflare Pages deployments (when, whether the build succeeded, the branch and the commit message) and DNS changes. An AI agent can run the same check itself after each deploy, through the MCP server.

Price

Free to sign up, with 2 free reports on each domain. Then US$28 a month for 1,500 credits.

Run your first report free