“Publish” is a sharper word than “upload.” Upload moves bytes. Publish is the moment those bytes become the version strangers will see on a given address. Drafts, previews, custom domains, and rollbacks only make sense when you keep that distinction clear. This guide is for people who already have website files and want a calm publish ritual — not a server to administer.

Publish vs draft (without a fancy CMS)

On a file-hosted site, your draft is usually the copy on your computer (or a branch in git) that you have not sent to the host yet. The published version is whatever SiteHost is currently serving on the preview URL and, later, on your custom domain.

There is no SiteHost website builder with a “Save draft” button inside a page editor. You edit files locally — or your designer does — then you publish a zip (or push via GitHub). That constraint is simplifying: one pipeline, fewer mysterious staging toggles.

Skip this if you need non-technical staff to log into WordPress and write blog posts daily. A WordPress CMS is a different kind of hosting. This article assumes you publish by shipping files.

Preview URL vs custom domain

After you publish on SiteHost, you get a preview URL with HTTPS immediately. That address is real hosting. Share it with a co-founder. Open it on cellular data. It is the right place to argue about headline copy.

A custom domain (yourshop.com) is a name you attach afterward. DNS must verify before the certificate for that name is issued. Until then:

  • Preview remains the trustworthy place to test.
  • The bare domain may not resolve, or may still point at an old host.
  • Do not announce the domain on flyers until DNS and HTTPS on that name check out.

People often treat “not on my domain yet” as “not published.” Wrong. Published-on-preview is already online. Domain is branding and memorability. Deep dives: how to make a website live, connect a domain to your website.

A publish sequence you can reuse

  1. Freeze a local zip (or commit) you could recreate tomorrow.
  2. Publish to SiteHost.
  3. Walk the preview checklist: home, inner pages, images, mobile nav, contact links, form thank-you path if any.
  4. If broken, roll back via deploy history, fix locally, publish again.
  5. Only when preview is acceptable, update DNS (or leave DNS alone if it already points here and you are replacing files only).
  6. After DNS verifies, confirm HTTPS on the custom domain and re-run the checklist there once.

Notice DNS is optional in early publishes. Replacing files on an already-pointed domain is normal later — still use preview habits if you have staging on Pro, or publish carefully during low-traffic hours if you do not.

Rollback is part of publishing, not an emergency-only button

Every publish should be reversible. SiteHost keeps deploy history of files so a bad evening upload does not strand you. Practice rollback once on purpose during the trial (~1 day) so you know where the control lives before a launch-week mistake.

Rollback restores files. It does not:

  • Undo a DNS change at your registrar
  • Fix mixed-content warnings from third-party http:// embeds
  • Recover an email inbox (email is not included with SiteHost)

Label your local zips with dates so you know what a rolled-back release *was*. The host remembers releases; your brain still wants filenames.

Staging vs production thinking on small plans

Starter ($9/mo, 1 site, 2 GB) is one live website — perfect for a single brochure. Pro ($30, 3 sites, 10 GB, staging) is where freelancers often keep a client preview as a separate site or use staging workflows before swapping. Scale ($65, 10 sites, 30 GB) and Business ($130, 30 sites, 100 GB, teams) expand capacity when you run many properties.

You do not get a built-in CDN or cPanel. Optional Cloudflare can sit in front later for caching and extra controls; it is not required to publish. SiteHost is for putting a website online, not for renting a raw server.

Failure modes tied to the publish moment

  • Publishing unfinished work to a domain already in print. Prefer preview until copy is done; or publish late at night and be ready to roll back.
  • Two people uploading different zips. Decide who owns the master folder. Colliding publishes are social problems, not DNS problems.
  • Changing DNS and files in the same five minutes. If something breaks, you will not know which layer failed. Serialize changes.
  • Assuming “Publish” sends email newsletters. It does not. Publishing updates website files only.

Example: café menu refresh

The café site has been live on cafename.com for months. Monday’s specials changed. The owner edits menu.html locally, zips the site, publishes, and spots that the allergen note vanished. They roll back, restore the note, publish again. Customers on the custom domain saw a short blip of the incomplete menu — next time the owner tests a full extract locally before publishing, or uses a second Pro site as a staging copy to send to the chef first. Same files skill; better ritual.

For brochure patterns generally, see brochure and one-page website hosting.

What success looks like

You can answer “what version is live?” with a date and a zip name. You know the difference between preview and domain. You have rolled back once without panic. You are not patching Linux. That is a complete publish practice for non-technical site owners.

Team publishes without trampling each other

If two people can upload, appoint one owner of the master folder. Date your zips. Announce in chat before publishing to a domain that already receives traffic. Use Pro staging when redesigns get contentious.

Publish is complete only after a human clicks the preview (or domain) and checks the paths that make money — contact, menu, book, buy. SiteHost rollback is your seatbelt; seatbelts work best when buckled before the crash, which is why a practice rollback during week one is worth ten minutes.

Questions people actually ask

Is the preview URL good enough for clients?

Yes for review. For public marketing, use your custom domain once DNS and HTTPS on that name are ready.

How long does a publish take?

Usually quickly after the zip uploads. Always verify in the browser rather than trusting a progress tick alone.

Can I unpublish completely?

You can roll back to a previous file set or replace the site with a simple “closed” page you prepare. Ask support or check account settings if you need the site removed entirely when you cancel — plans are paid after the short trial.

Does GitHub publish differently than zip?

The end state is still files on the host. GitHub is a delivery method. Clean project structure still matters.

Why would I pay if I only publish twice a year?

Because the site must answer browsers every day between publishes. Hosting is uptime and HTTPS, not a fee per upload. Starter at $9/mo matches infrequent updates to a small site.