Simple hosting is a deliberate choice: few moving parts, files you understand, and a preview link that tells the truth. For a small website, complexity is usually imported by accident — panels, installers, and app patterns you never needed. Here is who simple hosting is for, how to publish, and when to pick another product.

Who thrives on simple hosting

Side projects, small service businesses, clubs, and creators with a handful of pages. People who update by replacing a zip a few times a year. Teams that want HTTPS and a domain without a maintainer on retainer.

Who should look elsewhere

Heavy editorial CMS needs, mailbox bundles, or true custom server apps. SiteHost will not become those things if you squint.

Publish path that stays simple

  1. Finish the site as HTML (or receive it).
  2. Open index.html locally.
  3. Zip without nested parents.
  4. Upload to SiteHost.
  5. Approve the HTTPS preview.
  6. Point DNS last.

After a ~1 day trial: Starter $9 (1 site, 2 GB), Pro $30 (3 sites, 10 GB, staging), Scale $65, Business $130 for teams. No forever-free, no email hosting, no built-in CDN, no cPanel, no website builder.

Worked example: band event page on simple hosting

The Cedar Lines need a page for a Friday club show. One HTML file, poster art, and an external ticket link. Their bassist uploads to SiteHost Thursday night, shares the HTTPS preview in the band chat, fixes a misspelled venue name with a second zip, and points a subdomain Friday noon. Fans never see a control panel. The band never configures a server. When someone suggests “just put it on my VPS,” they decline — simple hosting is the point for a one-night page.

More reading: website hosting for a simple business site, website hosting for agencies, website hosting for a side project.

Failure: history-mode SPA routes with no files on disk

A well-meaning friend rebuilds the event page as a mini single-page app with clean paths like /tickets. Those paths are not files. On simple file hosting, a refresh on /tickets fails unless something rewrites requests to index.html. The band posts /tickets on Instagram Stories; half the taps 404. The fix for a small event site is almost always: use real links to index.html sections, or real small HTML files, or hash links — not framework router fashion. Simple hosting rewards simple URL shapes. Ask “what file exists for this URL?” before you announce it.

Keeping simplicity after the first publish

Name zips with dates. Roll back when a bad poster ships. Do not point the domain while the set times still change hourly. Do not merge email setup into the website night. Optional Cloudflare can wait until someone measures a real need.

Plan ladder without drama

One small site → Starter. A staging copy while you redesign the home page → Pro. Several small properties → Scale. Shared access across staff → Business. Visitors cannot see which plan you are on; they see whether the page works.

Signals you are inventing complexity

  • Installing software on a VPS for a three-section site
  • Adopting a CMS “for later” when later is imaginary
  • Changing nameservers because a blog said to
  • Treating free forever hosts as enterprise infrastructure

A simplicity checklist

  • [ ] Local extract works
  • [ ] Preview matches
  • [ ] URLs you advertise map to real files (or hashes)
  • [ ] Domain after approval
  • [ ] Mail DNS untouched
  • [ ] Backup zip stored

Simple hosting for a small website is mostly refusal: refuse nested zips, refuse fake routes, refuse mailbox confusion, refuse forever-free myths. What remains is upload, preview, domain.

Content freezes beat tool switches

Right before a launch, teams panic-buy new platforms. Simple hosting asks you to freeze copy for twenty-four hours instead. Upload once more, preview, then DNS. Switching hosts mid-panic rarely fixes a typo.

Small site, real stakes

A wrong door time on a band page wastes fans’ nights. Treat the HTTPS preview like a dress rehearsal. Have someone who did not build the page try every link. Simple systems still deserve careful humans.

Inventory of what you are not running

You are not running a database you forgot exists. You are not running a plugin inventory. You are not running mail. You are running files on SiteHost with a certificate on the preview and, later, on your domain. Write that sentence in your internal wiki so future-you does not “upgrade” into chaos.

When Pro still counts as simple

Staging is still simple: upload to staging, click around, promote or re-upload to live. It is not a second career. Use it when redesign risk is real; skip it when the change is one sentence of hours.

Questions people actually ask

Will simple hosting look cheap to customers?

Customers see design and clarity. They do not see your plan name.

Can I grow later?

Yes — higher plans, or even a different host someday. Files travel.

Is GitHub required?

No. Zip is enough for many small sites.

What about email for the band?

Use a mail provider. SiteHost does not include email hosting.