Built it with Bolt.new? Check every page for the mobile, speed, SEO and security gaps that AI builds quietly ship — before your first visitor does.
Varies — Bolt writes the stack, so check which one you got. Bolt.new scaffolds whatever the prompt implied: often a Vite + React SPA, sometimes Next.js, occasionally plain static files. That matters more than anything else on this page, because a Vite SPA serves crawlers an empty shell and a Next.js app does not. Check before assuming.
Bolt's strength is that it writes and runs a whole project in the browser, in one pass. Its weakness is the same thing: a single pass produces code nobody has read, wired to handlers nobody has clicked, on a stack you did not choose.
The failures we see on Bolt builds cluster differently from other AI builders. There is less missing-metadata and more genuinely broken behaviour — buttons bound to nothing, forms that post to a route that was never written, console errors on first paint that block the rest of the script.
So the Bolt scan leans on what happens when you actually drive the site, not just on what the HTML says.
These are the launch-blockers we actually find on Bolt builds, roughly in order of how often they come back positive — each with the specific change that clears it.
A one-pass build frequently produces a handler that was scaffolded and never implemented, or a form posting to an endpoint that does not exist. Nothing looks wrong: the button depresses, the form clears, and the submission goes nowhere.
The fix: We click through your interactive elements in a real browser and report every control that produced no navigation, no network request and no DOM change.
An uncaught error early in the bundle stops everything after it from running. The page still renders its static markup, so it looks alive while half the interactivity is dead — and this is the single most common Bolt defect we see.
The fix: We collect the browser console on load and report each error with the file and line, ordered by what they block.
Whether Bolt gave you Vite or Next.js completely changes what a crawler receives, and the answer is not visible from the running site. People optimise for the wrong problem constantly here.
The fix: We fetch your page the way a crawler does and show you the raw HTML that came back, so you can see whether your content is in it before you change anything.
Lorem ipsum, TODO, "Your headline here", and stub pages left in the nav. Bolt generates a complete-looking site including the parts you were meant to replace, so these ship more often than with builders that leave obvious blanks.
The fix: We surface every placeholder string and stub route we find, with the URL each one is on.
Generated projects rarely include an image pipeline. Full-resolution PNGs get referenced directly, and third-party scripts land in <head> without defer, which pushes out your Largest Contentful Paint.
The fix: We run real Google Lighthouse against your live URL and report LCP, CLS and TBT with the specific files responsible for each.
Paste your Bolt link and get a free Launch Score with your top problems.
Unlock the report for $12 (₹299 in India) — we scan every page and write the fixes for Bolt.
Paste the fixes into Bolt, say "repair it", and re-scan to confirm. Done.
The short version, if you would rather do it by hand. Everything here is something you can verify yourself in a few minutes.
The Bolt preview runs inside a WebContainer with the dev server's tolerances. Production is a static build behind a real CDN, so missing environment variables, case-sensitive import paths and dev-only proxy rules all surface for the first time at deploy. We scan the deployed URL, which is where those show up.
Request your page with JavaScript disabled, or read the raw HTML rather than DevTools' DOM. If your headline text is in that HTML you are server-rendered; if you see an empty root div, you are a SPA and crawlers get the empty version first.
Yes — that is one of the checks Bolt builds most often fail. We drive the page in a real browser and flag controls that produced no navigation, no network request and no change to the DOM when clicked.
Usually yes. An uncaught error stops every script queued behind it, so the visible damage is rarely where the error is. A page that looks fine with a dead analytics tag and a dead checkout button is the normal shape of this bug.
The free Launch Score covers your home page with no signup. Driving every page, clicking the interactive elements and writing the Bolt-specific fixes is the paid report, from $12 (₹299 in India).