Deploying a static website should feel like sending a finished folder to a calm place on the internet. You zip, publish, prove HTTPS preview, then attach your domain. This guide is a numbered procedure for people who want files online without renting a VPS.

Static means files

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

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

If a contractor insists you need cPanel to be legitimate, ask what task cPanel would perform that zip-plus-preview does not. Often the answer is habit.

Numbered deploy path

  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.

Plan ladder

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.

Résumé at yourname.com

Alex deploys a résumé on Starter, republishes twice for photo crop, and updates LinkedIn only after the custom domain certificate is happy.

Related reading: static hosting for small websites, static hosting without server management, and host a css website online.

After-deploy quiet checklist

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.

Starter versus Pro without peer pressure

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

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

If a contractor insists you need cPanel to be legitimate, ask what task cPanel would perform that zip-plus-preview does not. Often the answer is habit.

Done means

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.

Changing WordPress URLs before HTTPS exists

Search-replace tools and old WordPress habits push people to rewrite every link to https://yourdomain.com before DNS points and before a certificate exists on the new host. Absolute HTTPS links then fail in confusing ways; redirects loop; assets 404. Old WP mental habits linger even when the new résumé site is plain HTML. Even when your new site is plain static HTML, prefer relative links for your own files and treat HTTPS preview as canonical until SiteHost verifies DNS and issues the domain certificate. If you still run WordPress elsewhere, do not flip its site URL settings until HTTPS on the destination is real.

One more practical note on how to deploy a static website

Keep the scope of how to deploy 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 alex deploys a résumé on starter, republishes twice for photo crop, and updates linkedin only after the custom domain certificate is happy. 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 small websites, static hosting without server management, and host a css website online. 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 deploy 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.