A brochure website explains who you are, what you offer, and how to reach you. It rarely needs a CMS on day one. Hosting should feel like publishing a polished PDF that happens to be HTML: zip the files, get an HTTPS preview, connect a domain when the copy is approved. Here is who that fits, the publish path, and when to choose another product.

Who brochure hosting is for

Consultants, clinics, trades, studios, and professionals with a handful of static pages. Updates are occasional — new photo, new phone number, new service blurb — delivered as a fresh zip.

Who should look elsewhere

Newsrooms, membership communities, or teams that need in-browser editing for dozens of people. Also anyone who wants a website builder with no files. SiteHost is file hosting, not a builder, not cPanel, not a VPS class.

Publish path

  1. Gather HTML, CSS, JS, images into a clean folder.
  2. Confirm index.html opens offline with working menus.
  3. Zip at the correct level.
  4. Upload to SiteHost.
  5. Review on the HTTPS preview across phone and desktop.
  6. Add the domain at SiteHost; create DNS at the registrar; leave MX alone.

Trial about one day; then Starter $9 (1 site, 2 GB), Pro $30 (3 sites, 10 GB, staging), Scale $65, Business $130 for teams. No forever-free plan. No email hosting. No built-in CDN.

Worked example: resume-style brochure at yourname.com

Riley’s consulting brochure is basically an extended resume online: positioning statement, selected clients (with permission), services, and a contact form embedded from a third party. Riley uploads to SiteHost on Starter, shares the HTTPS preview with a former manager, adjusts one client name spelling via a new zip, then points rileyconsults.example. The brochure does not include mailboxes — Microsoft 365 already holds mail. Customers see HTTPS on the custom domain after DNS verifies.

Continue with host a landing page online, landing page hosting service, static hosting for landing pages.

Failure: changing WordPress URLs before HTTPS exists

Brochure owners escaping an old WordPress site sometimes paste database search-replace instructions into their week: force HTTPS URLs before any HTTPS site exists on the new host. Links break; admin redirects spiral. On SiteHost’s file path, upload static HTML (exported or rebuilt), use the HTTPS preview as ground truth, and only then set absolute links to https://yourdomain if you need them. Do not perform WordPress URL rituals against a folder of files that never had a WordPress admin. Wait for real HTTPS before rewriting URLs to HTTPS.

Brochure content that stays host-friendly

Prefer compressed images of offices and teams. Link out to scheduling tools instead of inventing a booking stack on the web host. Keep PDFs small. Avoid shipping node_modules. Avoid history-mode apps for a five-section brochure.

Staging for tone-sensitive copy

Legal and brand reviews benefit from Pro staging: try a bolder headline privately, keep the live brochure stable, then publish the approved zip. Rollback covers mistakes either way.

Cost honesty for brochure sites

Most stay on Starter. Pro appears when you also run campaign landing sites. Scale and Business are for volume and teams — not for prestige. Paying after a short trial beats forever-free branding on a client-facing brochure.

Operations notebook (five lines)

  1. Latest zip location
  2. SiteHost login owner
  3. Registrar
  4. Mail provider
  5. Who may publish

Brochure hosting fails socially when those five are tribal knowledge.

A brochure site earns trust with clarity. Host it with the same clarity: files, preview, domain, separate mail.

Questions people actually ask

How many pages count as a brochure?

A handful. If you are building a magazine, rethink the CMS question.

Can I host PDFs with the site?

Yes — keep them reasonably sized inside the zip.

Do I need email on the same host?

No. SiteHost does not include email hosting. Keep mail separate.

When do I point DNS?

After stakeholders approve the HTTPS preview — not during active copy fights.