You should not need to become a system administrator to put a café menu online. Non-technical hosting still asks a few concrete things of you: get a zip of the finished site, recognize a working preview link, and — later — copy DNS values someone shows you on a screen. This guide uses that order on purpose: designer zip first, DNS screen later.

The only skills this path needs

  • Download a zip and upload it into a web form
  • Open links on your phone
  • Copy and paste text into your domain account when the time comes
  • Ask for help with one precise sentence when stuck

You do not need Linux, SSH, or a WordPress plugin rabbit hole. If you specifically need WordPress for editors, that is a different kind of hosting — one sentence, then back to files. SiteHost is not a VPS and not a site builder; it puts the files you already have on the internet.

Ask a designer for a zip (script included)

Copy this into an email:

Please send a zip of the finished website with index.html at the root of the zip. Paths should be relative so CSS and images work when I open index.html on my computer. Please compress large photos for the web. I will upload this to SiteHost myself.

When the zip arrives:

  1. Extract it on your computer.
  2. Open index.html in Chrome or Safari.
  3. If it looks wrong locally, send it back — do not host yet.

Details on packaging: how to upload website files.

Account → preview → breathe

Create a SiteHost account. Start a website. Upload the zip (or have a technical friend connect GitHub if that is how they work). Open the HTTPS preview immediately. That preview is your site on the internet. Send it to a partner. Celebrate small.

Custom domain can wait. Truly. How to make a website live.

Trial is about one day; then pick a paid plan. Starter is $9/mo for one site and 2 GB — the usual non-technical fit. Pro ($30) if you need three sites, 10 GB, and staging. Scale ($65) and Business ($130) exist for larger site counts, storage, and teams. No forever-free plan. No email hosting bundled. No built-in CDN — optional Cloudflare later if someone you trust recommends it.

The DNS screen — later, with a checklist

When the preview is approved and you own a domain at a registrar:

  1. In SiteHost, add the domain to your website.
  2. SiteHost shows records to create (A and/or CNAME — follow exactly).
  3. Log into the registrar where you bought the name.
  4. Find DNS settings (sometimes called “Manage DNS”).
  5. Create the records. Do not invent values.
  6. Wait for verification. Then the certificate for your domain is issued.

Do not transfer the domain unless you want a new registrar for other reasons. Pointing is enough. Guides: connect a domain to your website, how to point DNS to website hosting.

If the DNS screen feels like too much, pay the designer for a 30-minute handoff call with screen share. That is cheaper than a month of anxiety.

What you can ignore forever (for this kind of site)

  • Kernel updates
  • cPanel “Softaculous”
  • Nameserver lore beyond “paste these records”
  • CDN configuration on day one
  • Email setup inside SiteHost — email is not included; keep mail where it already works

Mistakes non-technical users can avoid

  • Buying three years of the wrong host before files exist
  • Editing DNS while the designer still changes layout daily
  • Letting a friend “just put it on my VPS real quick” without documentation
  • Assuming Instagram is a website replacement for older customers who search Google

Example: yoga studio owner

Maya receives a zip from a student who rebuilt the site for a class project. She tests locally, uploads to SiteHost on Starter, shares the preview in the teacher group chat, fixes one typo by asking the student for a new zip, then books a Saturday coffee with that student to point mayayoga.example DNS together. Email stays at Google. Maya never learns what a VPS is. Success.

How to recognize a good designer handoff

A good handoff zip opens on your computer without a tutorial. You double-click index.html, see the design, click Contact, and the photos appear. A poor handoff requires special software, includes a Figma link only, or nests five folders deep. Send it back with the script from earlier in this article. You are not being difficult; you are protecting launch day.

Ask who will make text changes after launch. If the answer is “you, with HTML,” budget a short training or keep the designer on a small retainer. If the answer is “we need a CMS,” pause — a WordPress CMS is a different kind of hosting, and SiteHost’s file path may no longer be the right aisle.

Practicing rollback while nothing is on fire

During the trial or the first paid week, intentionally publish a zip with a tiny visible typo, then roll back using deploy history. The goal is muscle memory. The first time you need rollback should not be during a radio ad. SiteHost keeps publish history of files for that reason.

Same idea with the HTTPS preview: open it on cellular data, not only café Wi‑Fi. If a form is supposed to email you, submit a test. Third-party forms are normal on static sites; confirm the provider received the test.

People who “will just handle hosting” for you

Friends and nephews can help. Keep the registrar account in the business’s email, keep the SiteHost login recoverable, and keep the master zip in a shared drive. Verbal “I got it” is not documentation. When help is good, ask them to write five bullets: where DNS was changed, which plan you are on, where files live, where mail lives, and how to publish an update.

Example: resume site for a career change

Omar is not technical. A friend builds a one-page resume site as HTML. Omar uploads the zip during the short trial, opens the HTTPS preview on his phone, and sends the link in two job applications the same afternoon. He waits until an interview is scheduled before pointing his personal domain — domain last keeps pressure low. He stays on Starter because one site and light files are enough. See host a resume website online for packaging tips.

What “support” should sound like when you ask

Vague: “The website is broken.”

Useful: “The preview shows a blank page; locally index.html works. I think I zipped the wrong folder.”

Or: “DNS still says verifying after four hours; here is a screenshot of the A record I created.”

Precise questions get precise help. SiteHost will not teach you HTML from scratch, and it will not manage a VPS for you — but it will serve a correct zip with HTTPS and, after DNS, a certificate on your domain.

A calm weekly habit

Once a week, open your live URL and check hours, phone number, and the contact form. Brochure sites fail quietly when a holiday schedule is wrong. Updating means a new zip and a publish — not a server rebuild. If that still feels like too much, schedule a quarterly half-hour with the designer and keep a checklist in your notes app.

Questions people actually ask

What if I break the site?

Use deploy history to roll back to the last good publish, then get a corrected zip.

Can my teenager manage this for me?

Yes if they follow the zip root rules and do not treat DNS like a fidget toy. Keep the registrar login yours.

Is $9/mo a lot?

For a business phone line people would pay more. For a hobby site, only you can decide. See affordable hosting for a small website.

Do I need to be on the computer when customers visit?

No. That is the point of hosting.

What does SiteHost not do?

No builder, no cPanel, no email hosting, no built-in CDN. It puts your website files online with HTTPS and domain support.