A Bolt preview works but its Netlify site fails

1. Confirm the hosting provider in Bolt.

   Open the gear menu, choose All project settings and inspect Domains & Hosting. Read the selected provider without switching it. If this project uses Bolt hosting, this Netlify-specific check does not apply to that published address.

2. Follow the actual published link.

   Read the website link shown by Bolt’s publish flow and open it in a new tab. Compare it with the Netlify project you are inspecting. Record the project and hostname so an older test site is not mistaken for the current deployment.

3. Inspect what Netlify received.

   In that Netlify project, open Deploys and select the relevant deploy. Read its deploy details and log. For a source-based build, compare its build command and revision; for a manual upload, verify that the uploaded output came from the current completed build.

4. Compare the failed live request.

   On the Netlify page, open Chrome Inspect and Network, then repeat one failing action. Compare its request destination with the action in Bolt preview. Record whether the deployed page is missing an asset or calling a backend that was never deployed there.

WORKSThe confirmed Bolt-to-Netlify deployment completes the same intended test action.

BROKENThat deployment lacks the expected output, backend or production configuration.

Ranked in the order to investigate, not by claimed frequency.

1. The wrong hosting project is being inspected.

   Return to the project connected to the published URL. Correct settings there only after confirming it is the intended destination; do not create another site simply because the current link is confusing.

2. An older or incomplete build was uploaded.

   Run the app’s actual build procedure and publish the resulting output through the established workflow. Verify the deployment includes the changed page or asset rather than trusting the editor’s current state.

3. Preview relies on configuration or a backend absent in production.

   Use the Netlify environment procedure for context and scope differences. Deploy any required backend to a supported runtime and point the published frontend at it; uploading browser files does not create a running server.

• The available hosting-switch flow depends on the project’s current publishing state. Diagnose the existing deployment before planning a provider migration.
• A manually uploaded artifact may have no source build log at Netlify. In that case inspect the local or builder build result that produced the artifact instead of inventing a missing server build.

When to stop and hand it over

Hand over if you cannot trace the public URL back to one Bolt project and one Netlify deployment, or if a required backend has no production home. Provide the provider selection, URL and the redacted failed request with the artifact’s build evidence.