A blank white page
Pointing the host at the wrong folder is the classic cause. Vite projects build into a dist folder and Create React App into build. The host must serve the built output, not the source.
Bolt.new can build and publish a working app in minutes. Production is where the small details bite: blank pages after deploy, routes that 404 on refresh, missing environment variables, a database that pauses, and a hosting choice you cannot easily undo.
Hover to exploreHold to explore
Hover to exploreHold to exploreBolt runs your project in a browser-based environment. A live host builds it from scratch on its own servers, and anything that quietly depended on the Bolt environment shows up as a failure.
Pointing the host at the wrong folder is the classic cause. Vite projects build into a dist folder and Create React App into build. The host must serve the built output, not the source.
In single-page apps the browser handles routing. When someone reloads /pricing, the server looks for a file that does not exist. A redirect rule that serves index.html fixes it, but it has to be added.
Variables stored in Bolt are not automatically visible to your new host. They must be added there with the right framework prefix, such as VITE_, and the site rebuilt, otherwise features silently fail.
A build that works in Bolt can fail on a host with a different Node version. We pin the version so builds are repeatable.
Unused cloud databases can pause. Moving data requires exporting tables as CSV or JSON, and checking types match, as well as updating any API allow-lists that only trusted Bolt’s preview domain.
Choosing Bolt hosting first can make it difficult to move later. Where you plan to rank, sell or grow, choose the long-term home before the first publish.
The tools are all sound. The right pick depends on how the site will be maintained and what it connects to.
The quickest option. You authorise Netlify in your Bolt account, choose Netlify as the host in the project’s domain and hosting settings, then publish. You get a netlify.app address within a minute or so. It is a fair starting point for a simple site, provided you chose it before any Bolt-hosted publish.
Download the project as a ZIP, run npm install and npm run build, then upload the build output to Netlify Drop. This is fine for a one-off, but it is manual every time you change something.
Push the code to a repository and connect it to a host so every change builds and deploys automatically, with a history you can roll back. This is our default for anything that will keep changing.
If you mainly need pages, blog posts and enquiries, WordPress is easier to maintain, so we use your Bolt design as the brief. See AI-built website to a real website.
Custom domains are straightforward in principle and risky in practice if email shares the domain.
We confirm the registrar, who has the login and when it renews. Many businesses discover at this point that a former developer holds the account.
The web records change; MX, SPF, DKIM and DMARC stay put. Our DNS guide shows what each record does.
One preferred hostname, permanent redirects from the others, and a canonical tag on every page.
Certificates, mixed-content warnings, redirects and forms are checked in more than one browser, including on mobile data.
Search engines can render JavaScript, but rendering is queued and unreliable for large or slow apps, and many AI crawlers do not run scripts at all.
Each important page should have its own URL, title, description and content present in the HTML. For an app with marketing pages, we often pre-render those pages or move them to a framework that renders on the server.
Descriptive page titles, canonical URLs, crawlable links rather than click handlers, and an XML sitemap. Details in SEO for AI-built websites.
Organization, LocalBusiness, Service and FAQ markup, where accurate, helps machines connect your business, services and location. See AI visibility services.
Code splitting, optimised images and font loading are checked against Core Web Vitals, because a heavy bundle is the most common Bolt performance problem.
We handle deployment, the domain and the dull-but-vital checks, so a refresh never shows a 404 to a customer.
Build, host, domain and SSL configured and tested, with rollbacks available.
Launch guide →Netlify, a UK host or WordPress hosting, with DNS and email kept safe.
Hosting guide →Pre-rendering, metadata, sitemap and speed so important pages can rank.
Read the SEO guide →Structured data and clear facts for AI assistants.
AI visibility →An editable site with your Bolt design and a proper handover.
Explore our services →Keys, forms, database rules and dependencies checked before go-live.
Security review →
Antony Locke has built more than 100 websites and spent over a decade in design. He explains deployment in plain English, fixes the problems that break launches and leaves you with a site you can understand.
Creative Locker is a small Dorset studio. You deal with Antony from the first call to launch and beyond, not an account manager or an overseas team. He has built more than 100 websites since 2020, the studio was named Website Design Agency of the Year at the South West England Prestige Awards 2024/25, and the 170+ Google reviews are from real clients you can look up.
GitHub link, ZIP or Bolt project access. We review code, data connections and your goals.
Netlify, another host or WordPress, chosen before the first publish so you are never locked in.
Build settings, environment variables, redirects, database and forms set up and tested.
Domain, SSL, analytics and Search Console connected, with clear notes for next time.
Can’t see your question? Call 07388 210030 or email info@creativelocker.co.uk.
Publish it to a host that supports custom domains, then add the domain in that host’s settings and update DNS. The host issues HTTPS automatically. We do the DNS carefully so that email on the same domain keeps working.
Most often the host is serving the wrong folder. Vite builds to dist and Create React App to build, so the publish directory must match. Missing environment variables and a different Node version are the next suspects.
Single-page apps handle routes in the browser. The server needs a rule that returns index.html for unknown paths, such as a redirect from /* to /index.html with a 200 status.
Netlify’s own guide notes that a project already published to Bolt hosting cannot be moved to Netlify as the same project, and you would start a fresh copy. Decide before the first publish, or ask us to plan it.
Not by default if it is a client-rendered single-page app. With pre-rendering or server rendering, unique metadata and a sitemap it can perform well.
Unused cloud databases can pause, and your host will not see Bolt-stored variables. We migrate or reconnect data and update any allowed origins that only trusted Bolt’s preview domain.
Yes. For content-led sites WordPress is usually easier to run, and we use the Bolt design as the brief.
A deployment and domain job is far smaller than a rebuild. After a free call you get a fixed quote.
Send us a link, a ZIP file or just a screenshot of what you have. Antony will tell you honestly whether it is nearly ready, needs a rebuild, or is fine as it is, and give you a fixed quote with no obligation.
A short call and a clear plan. We pick the right home, fix the deploy and make sure it stays up.