My app worked yesterday. How do I know an update didn't break it?

A 10-minute check to run after every update to your site or app, in plain English: what to click, what usually breaks, and how to put the old version back.

· 6 min read · No tech skills needed

This guide in other languages: Deutsch

Open the live site the way a new customer would, in a private window and on your phone, and do the few things people come for: sign up, log in, pay, send a form. If those work and no page is blank, you can be fairly sure the update didn't break anything important. The catch is doing this after every single update, so it's worth writing the check down once and then automating it.

Why an update breaks things that worked

Developers call publishing a new version a "deploy". Every time you press Publish in Lovable or Bolt, or your developer pushes a change, the version your visitors see is replaced. A few things make that riskier than it looks:

  • AI tools rewrite whole files. You ask for a new button colour, and the tool also "tidies up" the sign-up form next to it. The change you asked for works; the one you didn't ask for is the one that broke.
  • The preview isn't the live site. The editor preview runs in a different setup from your real address. Settings like keys for payments or email are often filled in for one and missing in the other.
  • Your own browser hides problems. Browsers keep a copy of pages you've visited (that's the cache) and stay logged in. You may be looking at yesterday's version, or skipping the exact login step that broke.
  • Something outside your code changed. A card on your AI or email provider expired, a free usage limit ran out, a key was replaced. Nothing was "updated", but the site stops working all the same.

None of these show up as an error on your screen. The site loads, looks fine, and one important button quietly does nothing.

The 10-minute check after every update

Write down the three to five things your site must always be able to do. For a shop that's "see products, add to cart, pay". For an app it's usually "sign up, log in, do the main thing". Then, after each update:

  1. Open the real address in a private window. Not the editor preview. In Chrome that's "New Incognito window", in Safari "New Private Window". It starts with no saved copy of your site and no login, like a new visitor.
  2. Wait for the page to finish loading. A white page, a spinner that never stops, or a page with no text is a broken build. You'll know within ten seconds.
  3. Do your must-work actions for real. Sign up with a new email address (with Gmail you can add +test1 before the @ and it still arrives in your inbox). Log in. Add something to the cart. Send the contact form. Then check the result arrived where it should: the confirmation email, the new user in your dashboard, the message in your inbox.
  4. Click through the main pages. Home, pricing, contact, login, and anything in the top menu. Look for pages that say "404" or "not found", and for images that don't load.
  5. Repeat the main action on your phone, on mobile data. Turn off Wi-Fi. Phones show problems computers hide: a menu that won't open, a button off the edge of the screen, a payment page that doesn't fit.
  6. Check the link preview. Paste your site's link into a chat with yourself on WhatsApp, Telegram or Slack. The title, description and picture should still be yours, not a template's.
  7. Look at the error log (optional, one minute). On a computer, right-click the page, choose "Inspect", then the "Console" tab. This is the browser's error log. Red lines mean something failed. You don't have to understand them: copy them and give them to your developer or AI tool.

If everything passes, you're done until the next update. If something fails, don't start fixing yet.

Something broke: put the old version back first

Rolling back means making the previous, working version live again. It's almost always faster than fixing the problem under pressure, and your customers stop running into it while the fix is being worked out.

  • Lovable keeps every change as a version. Open the History panel, pick the last version that worked and choose Revert, as described in Lovable's version history guide. Then check which version carries the Published label and publish again if needed. The same guide notes that reverting restores your code, not your database data, so anything users saved since then stays.
  • Vercel has Instant Rollback on the project's overview page. Read Vercel's Instant Rollback instructions before you need it: after a rollback, new changes stop going live automatically until you undo the rollback, which surprises people the next day.
  • Other builders and hosts (Bolt, Replit, Netlify and others) also keep earlier versions. Find where yours lives today, while nothing is on fire.

Once the old version is back, ask for the fix with a message like this. It gives your developer or AI tool what it needs, and stops it from "improving" other things on the way:

My live site at [your site address] broke after the last update.

What I see: [white page / error message / the button does nothing].
Where: [page address], on [phone / computer], in a private window.
When it started: right after [the change you asked for].
Red lines from the browser console: [paste them, or "none"].

Please:
- Tell me which part of the last change most likely caused this.
- Fix only that, with the smallest change possible. Don't redesign
  or reorganise anything else.
- Tell me exactly what to click to check that it works again.

Then run your 10-minute check again on the fixed version before you call it done.

Make the next update less risky

  • One change per update. If you ask for five things at once and something breaks, nobody knows which of the five did it.
  • Keep your must-work list where you'll see it. A note on your phone is enough. The check only works if it's the same every time.
  • Check even after "tiny" changes. A text edit can rebuild the whole site.
  • Bookmark a known-good version. Lovable lets you mark versions in its history; most hosts let you find the last working deploy by date.
  • Ask what else a change touches. Add "List every file you changed and why" to your request. If the list is longer than you expected, ask why before you publish.
  • Don't publish right before you go offline. If something breaks at 11 p.m. on a Friday, it stays broken until Monday.

Get told automatically when an update breaks something

The manual check works, but only on the days you remember it. And when you publish ten times a day with an AI builder, nobody remembers it every time.

ScanYourSite's deploy check does the outside part for you. It notices each new version of your site on its own, from the outside, so there's nothing to install or connect in Lovable, Bolt, Replit, Vercel, Netlify or your own server. Within minutes of an update it checks that:

  • the site still answers and isn't sending an error;
  • the page isn't blank and actually draws on screen;
  • all the site's files load, with none missing after the update;
  • no new errors appear in the browser's error log when the page loads;
  • no secret key, like a payment or AI key, slipped into the new files every visitor downloads.

It stays quiet when the update is fine and writes only when something breaks: in Telegram, by email, or in Slack or Discord. It never touches your site or rolls anything back. You decide what to do, or hand its message to your AI tool.

The deploy check is part of Pro: $19 a month for three sites, with a full check every day and a check every five minutes that the site is up. On Pro, once you've confirmed the domain is yours, you can also add a few important pages, such as your login or checkout page, and the words each one should show. It doesn't log in or fill in forms for you, so step 3 above, really signing up or paying, stays your job.

To see what it looks at before paying anything, run the free check: no sign-up, about a minute, at https://scanyoursite.app/?check=yourdomain.com with your own domain in it. A free account then checks one site every week and sends you a weekly email summary.

Check your own site in a minute

Free, no sign-up. One report in priority order: what to fix, explained in plain words, with ready-made fixes to hand to whoever runs your site or paste into your AI tool.

Free, no sign-up. The basic check makes only the requests an ordinary browser would.

Check after every deploy