Publishing a static website is the moment your folder stops living only on your laptop. The calm sequence is zip, upload, HTTPS preview, then domain. This article walks a numbered publish path for students and anyone shipping simple HTML.

Publishing is not learning cloud

Staging on Pro helps when you maintain more than one experiment. Starter remains enough for many single properties.

Treat dated zips as your memory. Labels beat heroic recalls after a bad publish. Rollback is there, but only if you know which artifact was good.

Third-party embeds — forms, booking, donate widgets — fail independently of hosting. Check vendor status before republishing identical files.

Numbered publish steps

  1. Confirm you have publishable files with index.html at the intended root.
  2. Fix relative paths; remove file:// and accidental http:// asset links where you can.
  3. Zip carefully; extract once to verify structure.
  4. Create a SiteHost site; use the short trial to prove the publish.
  5. Upload the zip or connect GitHub; open HTTPS preview on desktop and mobile.
  6. Fix, republish, or roll back until preview earns trust.
  7. Point DNS at your registrar; wait for verification and the custom-domain certificate.
  8. Share the domain publicly — not the preview — after that certificate looks right.

That order prevents most self-inflicted outages.

Plans for class projects

Starter is $9/mo for 1 site and 2 GB. Pro is $30/mo for 3 sites, 10 GB, and staging. Scale is $65/mo. Business is $130/mo when teams and larger site counts matter. The trial lasts about a day; then you pay. There is no forever-free plan, no website builder, no cPanel, no email hosting, and no built-in CDN. Match storage to compressed media. Climb tiers when site count or teamwork demands it — not for vibes.

Nora’s student project

Nora’s city-data page was unstyled on first preview due to file:// CSS. She fixed paths, republished, submitted preview to her professor, and later attached a domain for her portfolio.

Related reading: static hosting for personal websites, simple static website hosting, and best static hosting for html websites.

Grading versus portfolio versions

On SiteHost, how to publish a static website still reduces to files moving through a calm pipeline. People complicate it with server shopping. Resist that urge when your pages already exist as HTML.

Third-party embeds — forms, booking, donate widgets — fail independently of hosting. Check vendor status before republishing identical files.

Custom domains live at registrars. Transfer is optional; pointing records is enough. Do not tangle mail DNS with website DNS casually.

Accessibility still matters

Custom domains live at registrars. Transfer is optional; pointing records is enough. Do not tangle mail DNS with website DNS casually.

On SiteHost, how to publish a static website still reduces to files moving through a calm pipeline. People complicate it with server shopping. Resist that urge when your pages already exist as HTML.

Phone testing is not optional. Wide monitors hide sticky-header bugs and oversized heroes. Open preview on cellular once per meaningful release.

Done for publish week

Done means HTTPS preview matches what you approved, assets load, primary links work on a phone, and rollback is understood. Domain pointing is optional until that calm exists. Email remains with a mail provider because SiteHost does not include mailboxes. No website builder will appear to invent missing pages — bring files.

file:// CSS paths that 404 in production

When a stylesheet (or image, or script) is referenced with a file:// path, you are asking visitors’ browsers to read a disk location on your computer. They cannot. The CSS file may sit correctly inside the uploaded zip and still never load, because the HTML never requests the hosted copy. Student editors rewrite hrefs during local preview and then upload the broken HTML. Editors and “open in browser” shortcuts rewrite paths quietly. Your defense is mechanical: extract the zip into an empty folder and open index.html from that extract before every upload. Relative paths such as css/site.css survive laptop, HTTPS preview, and custom domain. Certificates do not rewrite hrefs. DNS does not invent stylesheets. Fix the files, republish, then celebrate.

One more practical note on how to publish a static website

Keep the scope of how to publish a static website aligned with what SiteHost actually sells: static file hosting with immediate HTTPS preview and custom-domain certificates after DNS verifies. The worked reality for this article is nora’s city-data page was unstyled on first preview due to file:// css. When someone tries to expand the project into server management, a website builder you do not have, or email inboxes on the same SKU, pause and separate products. Write down the public URL only after it is a domain you control. Keep a prior zip. Click the phone number or primary button yourself on preview. Related reading: static hosting for personal websites, simple static website hosting, and best static hosting for html websites. If storage pressure appears, compress media before you climb from Starter to Pro; if site count grows, Pro’s three sites and staging are the usual next step; Scale and Business wait for larger portfolios and teams. That is the whole economics story without unlimited fairy tales.

Field notes you can reuse next month

Create a simple folder on your computer named for the site and the month. Drop every zip you publish into it. When a stakeholder asks what changed, open the folder instead of reconstructing history from memory. If you work with a designer, agree that they deliver archives that extract to index.html at the root. If you work with a developer who loves client-side routers, agree on real files for public URLs before anyone prints QR codes. If you are cost-sensitive, revisit whether you still need Pro’s staging or whether Starter covers the live property alone. If you are security-sensitive, re-scan your HTML for http:// after each vendor gives you a new embed snippet. If you are speed-sensitive, weigh images on a scale that is not a marketing graph — look at file sizes on disk. These notes are not glamorous. They are how static sites stay calm on SiteHost without cPanel, without a website builder, and without pretending email was included.

Questions people actually ask

Is SiteHost a fit for how to publish a static website?

If you have finished HTML/CSS/JS files (or a static export) and want zip or Git publish with HTTPS preview and a custom domain after DNS, yes. If you need a CMS runtime or inboxes, pick those products separately.

Is there a forever-free plan?

No. The trial is about a day; then you choose a paid plan such as Starter at $9/mo.

Does hosting include email?

No. Keep mailboxes with a mail provider and be careful with MX records when you only meant to point the website.

When do I point DNS?

After the HTTPS preview looks right. Custom-domain certificates follow successful verification.