A simple website is still a real website: pages people can open, on a link you control, with a lock icon in the browser. Hosting it does not require a control panel hobby. Zip the files, publish, confirm the HTTPS preview, then attach a domain. This guide is a numbered procedure for that kind of site — portfolios, small service pages, and similar.

Decide that “simple” is enough

Simple here means the site is made of files you can hold in a folder. No claim that your business is small forever — only that the *site* does not need a CMS on day one. If a designer already delivered HTML, you are ready. If you need non-technical staff editing fifty blog posts daily, pause and choose a different product category later; this article stays on the file path.

Numbered procedure from folder to live link

  1. Collect the finished folder. Homepage should be index.html. Styles and images should use relative paths that work when you open the file locally.
  2. Strip junk. Remove design sources and oversized originals. Keep web-ready images.
  3. Zip at the correct level so extracting reveals index.html immediately.
  4. Create a SiteHost site and upload the zip (GitHub is fine when the repo holds the same publishable output).
  5. Open the HTTPS preview on more than one device. Click every menu item once.
  6. Stop. Celebrate. Domain can wait until the work samples look right.
  7. Add the domain in SiteHost, create the DNS records at your registrar, leave mail alone, wait for verification.

What to skip

Skip cPanel tours. Skip website builders that rebuild a site you already paid to design. Skip forever-free hosts that inject branding you will outgrow next month. Skip VPS “flexibility.” SiteHost trial is about a day, then paid plans: Starter $9 (1 site, 2 GB), Pro $30 (3 sites, 10 GB, staging), Scale $65, Business $130 for teams. No email hosting. No built-in CDN.

Nested folder failure (worth memorizing)

The failure that burns portfolio launches: you zip the parent directory, so index.html sits inside an extra folder inside the archive. The preview does not show your case studies. You assume hosting is broken. Extract the zip on your desktop. If you must click into a folder before you see index.html, re-zip the inner contents. Upload again. This single habit prevents most first-publish confusion.

Worked example: freelance designer portfolio

Alex finishes a four-page portfolio: home, work, about, contact. Contact uses a third-party form. Images are WebP. Alex compresses from the wrong parent folder the first time — classic nested zip — and the HTTPS preview 404s. After re-zipping contents, the preview looks identical to the local extract. Alex sends that link in two proposals Friday afternoon without waiting on DNS. Monday, with a signed project inbound, Alex points alexdraws.example and keeps Gmail for mail. Starter is enough for one portfolio and 2 GB. When Alex later adds a second site for a side studio brand, Pro’s three-site allowance and staging become useful for testing a redesign.

Useful neighbors: best place to host an HTML website, how to upload website files, and host a photography website online.

What “done” looks like for a simple site

  • Every portfolio image loads on a phone
  • Form test submission arrives where you expect
  • HTTPS preview (and later the domain) match
  • You know how to publish a new case study zip next month
  • You did not promise clients an email inbox that the web host does not provide

Staging when “simple” still deserves a rehearsal

On Pro and above, staging lets you upload a risky redesign without replacing the live portfolio during a pitch week. Promote only when the new work page feels right. Rollback on the live site remains your safety net for bad publishes.

Keeping a simple site honest over time

Once a quarter, open the live URL and check that case studies still represent work you want. Replace screenshots that show outdated UI. Simple hosting stays simple when updates are just new zips — not server rebuilds. Optional Cloudflare is a later conversation about speed and caching, not a launch blocker.

When simple hosting is the wrong aisle

You need heavy server-side apps, email inboxes, or a drag-and-drop builder with no files at all. Say that out loud and pick those products elsewhere. For a designer portfolio made of HTML, CSS, and images, SiteHost’s path is the straight line: files, zip, HTTPS preview, domain last.

A weekly five-minute habit

Open your live link once a week. Check that the contact form still delivers a test. Confirm case study links are not pointing at retired Dribbble shots. When something drifts, fix the files, zip, upload — same procedure as launch day. Simple hosting stays pleasant when you treat updates as ordinary, not as emergencies that require a “server guy.”

Talking to clients about how the site is hosted

Plain language helps: “Your site is a set of files on SiteHost. I upload a zip when we change work samples. You own the domain at the registrar. Email is separate.” That speech prevents clients from expecting cPanel logins or mailbox setup from the web host. It also makes handoffs cleaner if they hire someone else later.

Host the simple site like a craftsperson: clean package, clear preview, calm DNS.

Questions people actually ask

Is a four-page portfolio “too simple” for real hosting?

No. Simple is a compliment when it loads fast and looks intentional. Paying $9 on Starter for a clean portfolio beats a free URL you do not own.

Should I use GitHub instead of zip?

Only if you already live in git and the repo contains publishable files. Zip is enough for many freelancers.

Can my clients edit text themselves?

Not inside SiteHost as a website builder. They need you (or a CMS elsewhere). Be honest about that during sales calls.

Why did my first upload show nothing?

Most often a nested zip. Extract, confirm index.html at the top, re-upload.