A small website still deserves a grown-up home: HTTPS, a path to your own domain, and a bill you can explain on one line. “Where to host” should be a short decision, not a spreadsheet of forty logos. Use criteria, know what the host will not do, and pick based on how you actually publish — usually a zip of files.
Size is about the site, not your ambition
Small means a handful of pages, a landing page, or a brochure. Traffic can still matter on a sale weekend. What stays small is the *stack*: HTML, CSS, JavaScript, images. You are not asking for a managed WordPress village or a server you patch at midnight.
Decision criteria that cut the noise
Upload model. Can you hand them a zip and get a site? If every path forces a builder, leave.
Preview discipline. HTTPS preview before DNS keeps public names clean.
Plan clarity. Monthly price, site count, storage — written in numbers.
Boundaries. Email? CDN? Free forever? Prefer honest no’s over fuzzy yes’s.
Escape hatch. Files you can download and move beat proprietary lock-in.
What this host is
SiteHost takes website files, publishes them, and gives you an HTTPS preview immediately. Connect a domain when the page is ready. No cPanel. No website builder. Short trial (~1 day), then Starter $9 (1 site, 2 GB), Pro $30 (3 sites, 10 GB, staging), Scale $65, or Business $130 for teams. No forever-free plan. No email hosting. No built-in CDN.
What this host is not
Not a mailbox provider. Not a VPS. Not WordPress care-and-feeding. Not a place to learn Linux. If you need those, buy those products — separately, on purpose.
Worked example: weekend sale campaign page
A housewares shop wants a one-page sale for Saturday and Sunday: hero, three product cards, coupon code, and a button to checkout on their existing shop platform. The page is HTML from a freelancer. They need it online Thursday for staff review and public Friday night. They pick SiteHost on Starter, upload the zip, and circulate the HTTPS preview in Slack. Friday they fix a wrong coupon character, re-upload, and only then point a subdomain. Checkout stays on the shop; this host only serves the campaign brochure. After the weekend they replace the zip with a “sale ended” note so old links do not promise deals.
Neighboring guides: website hosting for non-technical users, best place to host a simple website, how to host CSS and JavaScript files.
Failure: expecting email mailboxes from web hosting
Small-business owners often assume “hosting” includes hello@yourshop inboxes. It frequently does not — and on SiteHost it does not. If you point website DNS and casually reset everything at the registrar, you can break mail while the sale page looks perfect. Keep mail at Google Workspace, Microsoft 365, or another mail host. When you add site records, change only what the web host lists. Treat email as a second subscription with its own renewal line on your budget sheet.
Comparing “cheap” without lying to yourself
A free host “costs” attention: branding, sleep policies, surprise limits, and awkward client conversations. Starter at $9 is boring in a good way. Pro at $30 buys staging when you test next month’s campaign without touching the live page. Scale and Business wait until you outgrow small.
How non-technical teams still succeed
Ask the freelancer for a zip with index.html at the root. Upload. Preview on a phone. Domain last. That is the whole publish culture. Optional Cloudflare can appear later if a consultant suggests it for caching — it is not a launch gate.
Red flags while shopping
- “Unlimited” everything with no storage number
- Bundled email you did not ask for, priced vaguely
- No way to upload existing HTML
- Pressure to transfer domains before preview works
- Panels that assume you want Softaculous and WordPress for a one-page sale
Seasonal sites without permanent clutter
Small sites often live for a weekend or a quarter. Hosting them on SiteHost still makes sense: upload, run the campaign, then replace with a quiet “thanks” page or remove the subdomain later. Keeping deploy history helps if someone asks what ran last Black Friday. You do not need a permanent CMS for a temporary story.
Talking to freelancers about hosting choice
Say: “Please deliver a zip that opens locally. I will host on SiteHost. Do not install WordPress. Do not put mailboxes on the web host. Leave me DNS instructions only for the site.” Clear scope prevents freelancers from building a stack you cannot maintain.
Bandwidth anxiety vs image weight
People fear traffic more than they fear a 4 MB hero image. For a small sale page, compress first. SiteHost is not promising a global CDN in the box; if you later want Cloudflare in front, that is an optional layer after the page already works. Launch correctness beats premature edge networks.
Where you host a small website should feel calm. Files in, preview out, domain when ready — and mail kept safely to the side.
Questions people actually ask
Is Starter enough for a sale landing page?
Usually yes: one site and 2 GB covers compressed images and a single page.
Can the sale page and my shop share one host?
They can share a domain with a subdomain for the campaign while checkout stays elsewhere. Hosting the brochure and running the cart can be different systems.
Do I need staging?
Nice on Pro if you iterate creatively. For a one-weekend page, a careful zip and rollback may be enough.
Will visitors get HTTPS?
Yes on the preview immediately; on your domain after DNS verifies and the certificate is issued.