How to deploy a static storefront

A static storefront is a set of files that a browser can serve directly: usually HTML for pages, CSS for presentation, JavaScript for interactive details, and image assets. There is no application server assembling each page for a shopper. That makes deployment relatively simple, but it does not remove the need to choose a host, configure a domain, and check the live result.

This guide walks through the process without assuming a particular hosting provider. Provider interfaces and free-plan terms change, so use the host's current documentation for the final steps.

1. Prepare and inspect the site files

Start with the complete export—not just the homepage. Unzip it into a folder and check that it contains an entry page such as index.html, its assets, and any product or collection pages. Open the homepage locally, then follow its navigation and inspect at least one product page.

• Check that image files or embedded images load and that page links work.
• Confirm product names, prices, descriptions, contact details, and checkout links.
• Try the cart and checkout handoff. A static storefront may send customers to a payment provider or email; it does not mean the site host processes payments.
• Keep a backup copy of the original export before making manual changes.

2. Choose a static host

Static hosts serve files from a deployed directory or a connected code repository. Compare their current bandwidth, build, custom-domain, support, and usage terms against your expected traffic. A free tier can be useful for a small project, but it is not a guarantee of zero cost at every usage level.

Common deployment approaches include uploading a folder through a host's dashboard or connecting a Git repository and letting the provider publish each update. For example, consult the current documentation for Netlify, Vercel, or GitHub Pages. Those are third-party services with their own terms and setup.

3. Publish the correct directory

Follow the host's instructions to upload the unzipped site folder or connect the repository containing it. If the service asks for a publish directory, choose the directory where index.html lives. A frequent deployment mistake is publishing the parent directory or the archive itself, which leaves the host unable to find the homepage.

After the first deploy, open the temporary URL provided by the host. Check the homepage, product pages, navigation, assets, and checkout handoff there—not only on your computer. A path that worked locally can fail when the site is served from a different directory or domain.

4. Connect a domain and HTTPS

If you want a custom domain, add it in your hosting provider's dashboard and follow its current DNS instructions. DNS changes can take time to propagate. The host should also explain how it provisions HTTPS certificates; wait until the domain and certificate are reported as ready before sharing the address widely.

A domain registrar and a hosting provider are separate services, even when one company offers both. Confirm renewal prices, DNS records, certificate status, and who controls the domain account. Storza does not provide hosting, register domains, or configure DNS for an exported storefront.

5. Test the live storefront like a customer

Use a private browser window and a phone as well as a desktop. Visit the homepage directly, refresh a product page, use the site's navigation, and follow a checkout link. Test any WhatsApp contact link or email handoff with a controlled test message, and make sure your business contact information is correct.

• Check the browser address bar for HTTPS and mixed-content warnings.
• Confirm images, styles, and scripts load on nested product pages.
• Check page titles, descriptions, share previews, and the canonical site URL.
• Review the host's current backup, bandwidth, and account-recovery options.

Before you share the link

Deployment is complete when the production URL works from a clean browser and the merchant-controlled checkout handoff behaves as expected. Store updates are a separate step: make the change in your source project, export or publish the updated files, then verify the new deployment. A downloaded site does not automatically sync with the builder.