v0 website not working? Start here
The most common reasons a v0 site or app stops working, and what fixes each one.
Updated
v0 is a bit different from the other builders. The pages it makes are usually readable by Google out of the box, so the search problems that plague Lovable and Bolt owners mostly don't apply. The trouble with v0 sites is almost always behind the page: keys, data, and payments.
Here's where to look, in the order we'd look.
Is it the preview or the deployed site?
v0 shows you a working preview inside the editor. Deploying to Vercel is a separate step, and Vercel itself has a preview version and a production version. Three places a site can live. When someone says "it works for me," they usually mean one of the first two, and the customer is looking at the third.
Open your real domain in a private window on your phone. If it's wrong there, that's the version to fix. Run the free site check against the same address to confirm Google sees it properly, which for v0 it usually does.
It works in v0 but breaks on my domain
Nine times out of ten this is a missing key. v0 projects talk to other services: a database, a payment provider, an email sender, sometimes an AI service. Each needs a key, and the key has to be added to the deployed site separately. In the preview it's there. In production it isn't, and the page fails at exactly the moment it needs that service.
You'll usually see it as a form that submits and does nothing, a page that loads empty, or a button that spins. Nothing tells you why. Adding the key is quick once you know which one it is. Finding out which one, and whether the key is safe to be where it is, is part of a Service Call.
A key is sitting in the browser
Related to the last one, and more serious. Some keys are meant to be secret. If v0 put one in the part of the site that runs in the visitor's browser, anyone who knows how to open the page's source can read it and use your account, on your bill.
This is more common than you'd think, and the site looks completely normal while it's happening. Security Lockdown moves secret keys to the server where they belong, rotates them so the old ones stop working, and checks who can read your data.
Data saves wrong, or stopped saving
Forms submit but records come back missing a field. Old entries show odd values. A page that used to work errors after an edit.
This is what happens when the code and the database stop agreeing on what the data looks like. Each v0 edit may change one side without the other. It's fixable without losing your records, but it takes someone reading both sides carefully, which is Service Call work.
Payments half work
v0 is good at the payment screen. The server-side part that confirms the payment, creates the order, and sends the receipt is often thin or missing, so money arrives with no matching order, or orders appear that were never paid for. Finish the Checkout connects both ends and runs real test purchases, including refunds.
Every change breaks something else
If asking v0 for one fix now costs you two, the project has outgrown what the tool can hold in its head. More prompts won't get you out. A Takeover puts an experienced engineer on it to steady the code and see the project through. v0 projects export cleanly, so nothing is lost.
What to send us
The live address, what you expected, what happens instead, when it started, and a link to the v0 project if you have it. We'll ask in writing before touching anything behind the page.