Lovable website not working? Start here
The most common reasons a Lovable site or app stops working, and what fixes each one.
Updated
Lovable is very good at the first afternoon. You describe a site, it builds one, and it looks real. The trouble tends to show up a few weeks later, usually when a customer mentions something you couldn't see from your own screen.
This page is the short version of what we check when a Lovable owner calls. Work down it in order. Most people find their problem in the first three.
Before anything else, look from the outside
Open your site in a private browsing window on your phone, not inside Lovable. Lovable's preview is logged in as you, with your data, on your machine. Customers get none of that.
Then run the free site check. It reads your site the way Google does and takes about thirty seconds. If the first result says the page is nearly blank, skip straight to the Google section below.
It works in the preview but not on my domain
The most common call we get. A few causes, in the order we'd check them:
- You haven't published since the last change. Lovable keeps a preview and a published version. Edits land in the preview first. Open the publish menu and compare the date on the live version with your last edit.
- The domain is half connected. A custom domain needs records at the company you bought the domain from, and those can take a few hours to settle. If the site loads at your lovable.app address but not at yourbusiness.com, this is almost always it.
- Something only works for you. If a page shows your data in the preview and nothing on the live site, the app is probably reading data that only your logged-in account can see. That's a permissions problem, covered next.
Customer data: the one you can't see
Lovable projects store data in Supabase, a hosted database. The database has a setting called row level security, which decides who can read which rows. When it's off, or when the rules are written loosely, anyone who knows where to look can read or change your customer records. Everything on your screen looks fine the whole time.
You can't check this from the website itself. The free check doesn't look at it either, on purpose, because testing someone's database without permission is a crime. Signs it's worth worrying about: your app has sign-ups or stores anything about customers, you've had a warning email from Supabase, or you've never heard of row level security until now.
What fixes it is Security Lockdown. We write the access rules table by table, test them, move any secret keys out of the browser, and show you before and after.
Google can't find the site
Older Lovable projects draw the whole page in the visitor's browser. Google receives an almost empty file and has nothing to list. Newer projects render pages on the server, which Google can read, so this isn't true of every Lovable site. The free check tells you which kind you have.
If yours is the blank kind, the fix is Get Found on Google. It's not a rebuild and it doesn't change your design.
Every fix breaks something else
You ask Lovable to change one thing. It does, and two other things stop working. You ask it to fix those, and the first thing breaks again. Credits go down, the site gets worse than it was last week.
This happens to almost everyone who gets a project past a certain size. The tool can only keep so much of the code in mind at once, so each change undoes earlier work. More prompting rarely helps at this point. A Takeover hands the code to a seasoned engineer who steadies it and finishes the build, and you can keep using Lovable for small edits afterwards if you want to.
Checkout takes money but the order never shows up
Payment screens are easy to add in Lovable. The part that confirms the payment on the server, creates the order, and sends the receipt is often left out, so your payment provider and your site disagree about what happened. Finish the Checkout wires the two together and runs real test purchases.
What to send us
If you book a Service Call, the fastest start is a short note with the live address, what you expected to happen, what happens instead, and roughly when it started. Screenshots help. You don't need to explain the code. We'll ask for access in writing before we look at anything behind the page.