Launch guide
If you are searching for how to publish base44 website projects, the final step is usually less about building and more about checking visibility, access, and the public link. Follow this sequence to move from a finished project to a dependable live site.
Quick answer
A publish problem usually has a visible symptom: the preview works, but visitors see an old version, a blank page, a sign-in wall, or an unavailable domain.
6 min readFind the cause
Start with the least disruptive checks. This order separates a simple visibility issue from a project, deployment, or domain problem before you change anything important.
If the builder preview works but the shared address does not, confirm that the latest version was actually published. A saved draft and a published version are not always the same state. Publish the current project, wait for the confirmation, and open the public address in a new private browser window.
LOOK FOR
A clear published or live confirmation, not only a successful preview.
A site can be deployed correctly while still requiring an owner session or access permission. Test the link while signed out, on a different browser, or from a phone using mobile data. If the page asks for access, review the project's visibility settings before troubleshooting the design.
ISOLATE
A private-window test removes most account-session confusion.
When the domain opens but shows a blank state, 404 page, or unexpected screen, inspect the entry route. Confirm that the intended homepage exists, that its path matches the link you are sharing, and that navigation buttons do not point to an old route. A clean homepage test is more useful than checking every page at once.
CHECK FIRST
Open the root address, then test one known internal page.
If your public site shows an older design, the latest edits may not have reached the live deployment yet. Save the project, publish again, and allow the deployment to finish before refreshing. Use a hard refresh or private window so an old browser cache does not disguise a successful update.
COMPARE
Check one unmistakable new change, such as a heading or button label.
If the platform-provided address works but your custom domain does not, the project is probably live and the remaining issue is domain configuration. Recheck the spelling, DNS records, and whether the domain is connected to the intended project. Keep the original public address available while the domain finishes updating.
SEPARATE
A working platform URL proves the site and domain are different problems.
Repair sequence
Use these three passes in order. Stop as soon as the public address works; unnecessary changes can create a second problem while you are solving the first.
Save the project, confirm the homepage is the version you want visitors to see, and use the publish action. Wait for the completion state instead of closing the builder immediately. Copy the public address only after the deployment reports that it is ready.
Open the public address in a private window while signed out. Check the homepage, one primary button, one internal route, and the mobile layout. If those work, the core deployment is healthy; if one fails, note the exact URL and message before editing.
For a stale page, publish the newest changes again and hard-refresh. For a domain issue, compare the connected domain with the address you are visiting and review the DNS configuration. Retest from a second network before announcing the launch.
Before every launch
Keep this small checklist beside your release notes. It turns publishing from a last-minute click into a repeatable handoff that another person can verify.
The homepage is complete, saved, and clearly identified as the version to publish.
RequiredDo this before opening the public link.
The public platform address has been opened in a private browser window.
RequiredTest without relying on your existing session.
The main call to action, navigation, and at least one internal route work.
RequiredRecord any broken path exactly as shown.
The current design is visible after a refresh, including one recent change.
RequiredThis catches stale deployments and cached pages.
The custom domain has been checked separately from the platform address.
OptionalRequired only when you are using a custom domain.
A phone or narrow browser view has been tested before sharing the link.
OptionalUseful for catching mobile-only layout problems.
The final public URL and launch date are recorded for future updates.
OptionalThis makes later troubleshooting much faster.
Before checks
Ready to share
Compare the project state before launch checks with the finished public presentation.
Use the launch sequence once, test the public experience while signed out, and keep the working URL as your source of truth. A clear prompt can also help you turn the next idea into a structured project before you publish it.
Build my next siteTutorial FAQ
Save the project, confirm the homepage and main routes are ready, then use the publish action in the builder. After the deployment finishes, open the public URL in a private window to verify that visitors can access the current version.
The project may still be private, restricted to your account, or available only in preview mode. Test while signed out and review the visibility settings; if the project is public but still unavailable, check the published address rather than the editor preview.
The latest edits may not have been published, or your browser may be showing a cached copy. Publish the saved project again, wait for completion, then use a hard refresh or private window and compare a clearly changed heading or button.
First confirm that the platform-provided public address works, because that separates a live project from a domain problem. Then connect the custom domain, verify the required DNS records and spelling, and allow time for the domain configuration to update before testing again.
Check the homepage, one main call to action, one internal route, and the mobile layout while signed out. Also verify that the visible content is current and that the URL you plan to share is the public address, not an editor or preview link.