Agencies and freelancers often need simple static site hosting for client microsites that should not become WordPress. This guide covers who it is for, the publish path on SiteHost, and when to steer a client elsewhere.

Who books simple site hosting

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.

Storage is a budget. Compress photos. Leave raw camera files on a backup drive, not in the web zip.

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

Publish path for client work

  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.

When to upsell a different stack

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.

Agency microsite example

An agency uses Pro staging for a client microsite, fixes http:// logos, and publishes to production after approval.

Related reading: reliable static website hosting, best place to host a static website, and html website hosting without cpanel.

Padlock QA before handoff

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

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

On SiteHost, simple static site hosting 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.

Retainer updates

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.

Business boundaries

Pick a different product when you need a full CMS with editorial roles, server-side code you maintain, or bundled email. SiteHost is for static files with preview HTTPS and domain certificates after DNS — not for every website genre on earth. Related reading: reliable static website hosting, best place to host a static website, and html website hosting without cpanel.

http images at handoff

An HTTPS page that still loads http:// images, scripts, or frames is mixed content. Browsers may block assets or show warnings even when the SiteHost certificate is perfect. The client’s old logo CDN URL was http and failed on the microsite preview. Preview HTTPS is valuable because it reveals the problem before customers see it. Search your HTML and embeds for http://, download images you care about into your project, and reference them with relative paths — or use HTTPS endpoints from vendors you trust. Do not open imaginary “SSL settings” panels on a simple static host; fix the markup and republish.

One more practical note on simple static site hosting

Keep the scope of simple static site hosting 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 an agency uses pro staging for a client microsite, fixes http:// logos, and publishes to production after approval. 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: reliable static website hosting, best place to host a static website, and html website hosting without cpanel. 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 simple static site hosting?

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.