Bolt website not working? Start here
The most common reasons a Bolt site or app stops working, and what fixes each one.
Updated
Bolt builds fast and deploys with one click, which is exactly why the problems are easy to miss. The site is live before you've had a chance to find out what's missing.
Here's the list we work through with Bolt owners. Start at the top.
Open it the way a customer would
Close Bolt. Open your live address in a private window on your phone. A surprising number of problems only exist outside the editor, because the editor is running a local copy with your settings loaded.
Run the free site check while you're at it. Bolt sites are built in a way Google often can't read, and the check will tell you in thirty seconds whether that's true of yours.
The page is blank when someone refreshes or follows a link
The home page loads, but if a visitor refreshes on another page, or clicks a link you sent them to a specific page, they get a blank screen or a "page not found" message.
This is the single most common Bolt complaint, and it isn't you. Bolt builds the kind of site where the browser handles all the page changes. The hosting company needs to be told to hand every address to the site instead of looking for a file that doesn't exist. It's a small configuration change on the hosting side. If you'd rather not go hunting for it, it's part of what a Service Call sorts out on day one.
It worked yesterday and now it doesn't
Check two things first:
- Did you redeploy after a change? Bolt's preview updates as you type. The live site only changes when you deploy again.
- Did a key expire or get removed? Bolt projects often talk to other services, like a database, a payment provider, or an email sender. Each one uses a key. If a key lives in the editor but wasn't copied to the deployed site, the live version silently fails at exactly the point where it needs that service.
If neither of those is it, the problem is probably happening out of sight. Bolt projects rarely report errors anywhere you'd see them. A customer hits a blank screen and nobody finds out. Part of a Service Call is adding error reporting, so the next failure reaches you before it reaches a customer.
Google can't see the site
Because Bolt draws the page in the visitor's browser, Google usually receives an empty shell with no title, no description, and no text. The site looks perfect to you and doesn't exist to a search engine.
The free check will confirm it. The fix is Get Found on Google, which makes the pages arrive as real content and then sorts the titles and settings page by page. Your design stays as it is.
Customer data might be open
If your Bolt app has sign-ups, a contact list, orders, or anything else about real people, it's storing that somewhere, usually a hosted database. Access rules decide who can read it. Bolt doesn't always write them, and when it does, it tends to write them loosely.
You can't tell from the outside, and we won't test it without your written permission. Security Lockdown writes and tests the rules, moves secret keys out of the browser, and gives you a before-and-after you can keep.
Tokens are disappearing and the site isn't getting better
Each fix costs tokens. Each fix breaks something. You're paying to stand still.
Past a certain size, Bolt loses track of its own code, so every change undoes an earlier one. This is normal and it's where most owners finally call someone. A Takeover puts a developer on the code to steady it and finish the job. You can export your project from Bolt, so your work isn't lost.
Payments go through but orders don't
A checkout screen is easy. The part that confirms the charge on the server and turns it into an order with a receipt is the part that gets skipped. Finish the Checkout connects the two and runs real test purchases, including the refund path.
What to send us
The live address, what you expected, what happens instead, and when it started. If you have the Bolt project link, include it. We'll ask in writing before we look behind the page.