Brochure sites and one-pagers are the workhorses of local commerce: enough information to trust you, not so much structure that nobody maintains it. Choosing between a single scrolling page and a few linked pages is a content decision first and a hosting decision second. Hosting stays simple either way if you already have the files.
One-page vs multi-page — choose on purpose
One-page works when your story is short: who you are, what you offer, proof, contact. Navigation jumps to sections via anchors. Visitors on phones scroll more than they hunt menus.
Multi-page works when sections get long or need shareable URLs (“send me your pricing page”). Typical small set: Home, Services, About, Contact.
Hosting does not care which you pick. Both are files. SiteHost serves them after a zip upload or GitHub connect. HTTPS preview is immediate; custom domain SSL follows DNS verification. Rollback covers mistaken publishes.
Skip building a twelve-page sitemap “because real businesses have twelve pages.” Empty pages harm trust. A bakery with three honest pages outperforms a shell of twelve “Coming soon” stubs.
Contact patterns that fit file hosting
- Tap-to-call links (
tel:+1...) - Mailto links (simple; uneven on phones)
- Third-party form endpoints embedded in HTML
- Links to chat tools you already pay for
SiteHost does not include email inboxes. Forms that must notify you need an external form service or a mailto fallback. Host a landing page online details form wiring. Test a submission the same day you publish — forms that look pretty but never arrive are worse than a phone number in plain text.
Maps embeds without breaking the page
Paste the embed snippet from your maps provider into the HTML where the map should live. Then:
- Check that the embed uses HTTPS
- Confirm it is not wildly tall on mobile
- Keep NAP text next to the map — crawlers and humans like text, not only a widget
- Avoid three different address spellings across pages
If the embed fails, the page should still list the address in plain HTML. Graceful degradation is a brochure virtue. On a one-pager, put the address near the call-to-action so someone who never scrolls to the map still finds you.
What SiteHost includes and excludes for brochures
Includes: file hosting, HTTPS preview, custom domain after DNS verifies, deploy history/rollback, plans from Starter ($9/mo, 1 site, 2 GB) upward through Pro ($30, 3 sites, 10 GB, staging), Scale ($65, 10 sites, 30 GB), Business ($130, 30 sites, 100 GB, teams).
Excludes: website builder, cPanel, email hosting, built-in CDN. Optional Cloudflare if you want it later. Short trial (~1 day), then paid — no forever-free plan, no nonprofit coupon. No VPS access and no WordPress tutorial: if editors need a CMS, that is a different kind of hosting.
SiteHost is for people who want a website online, not a server to manage. Website hosting without server management.
Maintenance calendar (realistic)
| Cadence | Task |
|---|---|
| Anytime hours change | Update HTML, publish, spot-check |
| Seasonal | Swap hero photo; compress first |
| Yearly | Confirm domain renewal at registrar; confirm WHOIS contact mail works |
| After bad publish | Roll back, then fix |
If nobody in the business will touch HTML, retain the designer for small change orders or keep a PDF “menu” you replace as a whole file. The cheapest hosting plan in the world still fails if hours on the site are wrong every Sunday night.
Example: physiotherapist clinic
One-page site: services list, insurance notes, map embed, book-online button to a scheduling tool. Files total 1.2 MB. Hosted on Starter. When a new therapist joins, a paragraph is added and republished. The clinic does not need Scale. They do need consistent NAP with Google Business Profile — website hosting for local business.
Example: neighborhood bakery
A three-page brochure — Home, Menu, Catering — with a PDF allergen sheet. The owner downloads a zip from the designer, opens index.html on a laptop, uploads to SiteHost, and shares the HTTPS preview in the family group chat. Someone spots that Saturday hours are wrong. A corrected zip publishes in minutes; deploy history sits ready if the second try is worse. Only then do they point corneroven.example DNS. Customers never saw the wrong hours on the public domain. Email stays at the registrar. That is the whole operating model.
When the brochure should grow up
Add a blog only with a plan to write. Add ecommerce only with a real cart tool. Add staff logins only with an app platform. File hosting remains a great home for the marketing shell even when specialized tools handle the heavy verbs.
If editors demand WordPress, use WordPress hosting — a different kind of hosting — rather than pretending a static brochure is a CMS.
Writing for scanners, not novel readers
Brochure visitors skim. Lead with the service and the area you serve. Put proof near the top — a short testimonial, a photo of the actual shop, a certification that matters. Hide the company history below the fold unless your brand *is* the history.
One-pagers should still use clear headings so someone jumping via anchor links knows where they landed. Multi-page sites should reuse the same header and footer so NAP never drifts between pages. Inconsistency is how you get “the site says 5, Google says 6” support calls from your own customers.
If you publish a PDF menu or rate sheet, link it prominently and date it inside the PDF. Replace the file with the same filename when possible so old links still work, or update every button that pointed at a dated name.
Accessibility is part of brochure quality
You do not need a perfect audit to improve basics: readable contrast, alt text on meaningful images, buttons that are real buttons, tap targets large enough for thumbs. Map embeds should not trap keyboard users if you can help it — at minimum, offer the address in text. Hosting HTTPS helps trust; readable pages help humans.
SiteHost will serve accessible and inaccessible HTML equally. The craft is in the files you upload. When a designer delivers a zip, ask them whether contrast and mobile tap targets were checked — a five-minute conversation that prevents quiet lost customers.
When to split a brochure into a campaign page
If you run a seasonal offer, a separate landing page (or a second site on Pro) keeps the evergreen brochure calm. Point ads at the campaign URL. When the offer ends, publish a closed state rather than leaving stale pricing live. That operational habit matters more than which plan logo is on the invoice.
A campaign page can live as a second folder published as its own site, or as a path inside the same site if your structure already supports it. Either way, decide before you buy ads. Preview the offer page on a phone, submit the form once, and only then spend money driving traffic.
Preparing files so hosting stays boring
Boring is the goal. Confirm index.html sits at the root of what you zip. Use relative paths for CSS and images. Compress the hero before upload. Open the HTTPS preview and tap every menu item. Domain and DNS come last — see connect a domain to your website when you are ready.
SiteHost’s short trial (~1 day) is enough to prove the upload path. Build and polish locally first so trial day is not your design week.
Questions people actually ask
Are one-pagers bad for SEO?
Not inherently. Thin content is bad. A clear one-pager with real information can rank for local queries. Duplicate doorway pages are the problem, not scrolling.
Can I host a PDF brochure instead of HTML?
You can upload a PDF, but HTML is friendlier on phones and for accessibility. Many businesses offer both.
Do I need staging for a four-page site?
Optional. Preview + rollback often suffice. Pro adds staging when you want a safer review lane.
What image size should the team hero be?
Large enough to look sharp on a laptop, small enough to load on cellular — often under a few hundred KB after compression.
Should the contact page be separate?
If the form is long or you run ads to “Contact,” a separate URL helps. Otherwise a section can be enough.