Uploading HTML to hosting sounds like “drag a zip and done.” It is — when the zip is honest. Most blank previews come from how the archive was built, not from mysterious server settings. Below is a practical upload procedure, the traps to skip, and a clear picture of finished.

Before the upload button exists

Confirm you have publishable files: HTML, CSS, JavaScript, images, maybe a PDF. Open index.html from a local extract. If fonts or photos are missing on your laptop, fix paths locally first.

SiteHost accepts a zip upload or a GitHub connection. Neither path is a website builder. Neither is cPanel. You are delivering a finished file tree.

Numbered upload procedure

  1. Clean the folder. Remove RAW photos, Sketch sources, and node_modules if someone left a build project lying around. Visitors only need the finished site.
  2. Name the homepage index.html. That is what the host serves at /.
  3. Zip the right level. Select the files so that when you extract the zip, index.html is visible immediately — not inside an accidental extra folder.
  4. Create the SiteHost site and choose zip upload (or GitHub if that is already your workflow).
  5. Publish and open the HTTPS preview. Check the homepage, a second page if you have one, and an image.
  6. Only then add a custom domain and create DNS records at your registrar.

Trial lasts about a day; then pay. Starter ($9, one site, 2 GB) covers most small sites. Pro ($30, three sites, 10 GB, staging), Scale ($65), and Business ($130 for teams) are the next rungs. No forever-free plan, no email hosting, no built-in CDN.

What to skip while uploading

Skip “installing” a CMS for a site that is already HTML. Skip renting a VPS. Skip pointing DNS the same afternoon you are still swapping hero images. Skip rewriting every absolute URL by hand before you have seen the HTTPS preview — preview first, polish second.

Nested zip: the classic upload failure

Here is the failure worth a full pause. You zip the *parent* folder that contains your site folder. The archive’s top level is something like bakery-site/, and only inside that folder sits index.html. After upload, the preview root has no homepage file where the host expects it. You see 404 or a directory vibe that feels broken. The fix is boring and reliable: extract, open until you see index.html, re-zip *those* contents, upload again. Two minutes of verification on your computer saves an hour of panic.

Worked example: bakery one-pager with hours

Nora’s bakery needs a simple page: photo, address, weekday hours, and a link to an online ordering tool she already pays for. A cousin builds index.html, styles.css, and four compressed photos. Nora accidentally compresses the Desktop folder that merely *contains* bakery-final. Preview fails. She extracts, finds the nested folder, re-zips correctly, and the HTTPS preview shows Saturday hours clearly. She shares that link on Instagram Stories the same evening. Custom domain waits until Monday when she has time at the registrar. She stays on Starter because one site and light images fit 2 GB easily.

For more context on small sites and front-end projects, see where to host a small website, how to host a frontend project, and HTML hosting for small websites.

Replacing files without drama

Keep dated zip names (bakery-2026-04-02.zip). After a second publish, click the same paths again. If the new version is worse, use deploy history to roll back, then fix locally and publish once more. Rollback restores files; it does not undo a DNS mistake at the registrar.

What “done” looks like after upload

  • HTTPS preview matches the local extract
  • Hours, phone, and buttons work on a phone browser
  • You can find the exact zip that produced the live look
  • Domain (optional) is still unpointed *or* pointed only after approval
  • Nobody changed MX records while “helping” with the website

GitHub note without the jargon pile

If a developer connects GitHub, the repository should contain the same kind of publishable files you would zip — not a pile of tooling with no finished output. Upload the built site, whether the vehicle is zip or git.

Storage reality while you upload photos of croissants

Starter’s 2 GB is generous for compressed web images. It is not a place to dump every camera original. Resize before zipping. If you outgrow one small site, Pro’s 10 GB and staging help you test a redesign without touching the live bakery page.

Phone check that catches real mistakes

After every publish, open the HTTPS preview on cellular data. Café Wi‑Fi forgives slow images; a customer on the sidewalk does not. Tap the ordering link. Confirm hours wrap cleanly on a narrow screen. If a photo is huge, fix it locally and upload again — that is normal, not a failure of the host.

Ask one other person to open the link without coaching. Fresh eyes catch a wrong phone number faster than you will after staring at the page for an hour.

A calm rhythm for seasonal updates

Holiday hours change. When they do, edit the HTML (or ask whoever built it), zip, upload, preview, done. You do not rebuild a server. Keep last month’s zip so you can roll back if a rushed edit goes wrong on a Friday afternoon. That habit matters more than learning panel jargon you will never use.

Upload is packaging. Get the archive right and the host looks simple because you stopped feeding it nested folders.

Questions people actually ask

Why does my upload show a blank page or 404?

Usually index.html is nested one folder too deep, or the homepage has a different name. Extract the zip locally and fix structure before uploading again.

Can I upload individual files without a zip?

The normal SiteHost path is a zip (or GitHub). Treat the zip as your whole site snapshot so every CSS and image arrives together.

Do I need cPanel to manage uploads?

No. SiteHost does not use cPanel. You publish a zip and get an HTTPS preview.

When should I connect my bakery’s domain?

After the preview shows correct hours and photos. Pointing DNS early freezes a half-ready page onto the public name.