A landing page has one job. Not five. Not a sitemap. One job — collect signups for a waitlist, sell a workshop seat, explain a product launch, or send people to book a call. When the page tries to also be a blog, a careers center, and a documentation portal, conversion drops and hosting conversations get muddy. This guide covers hosting a one-job page, wiring third-party forms, and running campaigns without inventing fake platform features.

Define the job in one sentence

Write it down: “Get email signups for the April cohort.” or “Send mobile visitors to tap Call Now.” If you cannot finish the sentence, you are not ready to host a landing page — you are ready to argue about IA. Finish the sentence first.

Everything on the page either serves that sentence or leaves.

Files, not a builder (in this article’s world)

You (or a contractor) produce HTML/CSS/JS for the page — often a single index.html. SiteHost hosts it: upload zip or connect GitHub, HTTPS preview immediately, custom domain certificate after DNS verifies, rollback via deploy history if a headline test fails awkwardly.

SiteHost is not a website builder and not an A/B testing SaaS. You can still test by publishing version B and rolling back, or by using separate campaign subdomains/sites on higher plans. It is also not a VPS and not WordPress hosting — if you need editors in a CMS, that is a different kind of hosting.

Plans: Starter $9/mo (1 site, 2 GB) for one page property; Pro $30 (3 sites, 10 GB, staging) when campaigns multiply; Scale $65 / Business $130 for larger portfolios of sites and teams. Trial ~1 day, then paid. No forever-free plan. No email hosting. No built-in CDN (optional Cloudflare later).

Third-party forms — the usual pattern

Static hosting will not secretly email you form posts by itself like a full application server. Common pattern:

  • Form HTML on your page
  • action pointing at Formspree, Basin, Getform, or similar
  • Thank-you message or redirect they support
  • Spam protections those tools offer

Mailto: links are simpler and less reliable (depend on the visitor’s mail app). For paid ads traffic, use a real form backend.

Payment: Stripe Payment Links or similar buttons work as links — your page stays a landing page; checkout lives elsewhere. Same idea for Calendly embeds. Website hosting for consultants expands on that stack.

Campaigns and URLs

Patterns that work:

  • Dedicated domain or subdomain for a launch (launch.example.com or april.example.com)
  • UTM parameters on ads pointing at the same page
  • Separate SiteHost site on Pro+ so a campaign can die without touching the evergreen brochure

DNS for each custom name follows the same rule: records at the registrar, certificate after verification. Connect a domain to your website.

Do not transfer domains casually for a two-week campaign; pointing is enough.

Performance is part of the job

Ad traffic is impatient. Compress the hero. Limit font files. Avoid autoplay video backgrounds that eat data caps. SiteHost has no built-in CDN; optional Cloudflare can sit in front. Your biggest win is still image diet. Fast-loading website hosting.

Failure modes unique to landing pages

  • Form points to localhost or a designer’s staging endpoint. Click-test a real submission from your phone on the HTTPS preview.
  • Thank-you page 404. Include it in the zip.
  • Legal missing. Privacy blurb for email capture — short is fine; absent is risky.
  • Publishing unfinished copy to a domain already in ads. Use preview until creative sign-off; how to make a website live.
  • Mixed content from insecure embeds after HTTPS.

Example: workshop waitlist

A ceramicist runs a spring workshop. One page: photo, three bullets, price, form. Designer delivers a 800 KB zip. Ceramicist uploads on Starter, tests form signup, schedules Instagram ads aimed at the custom domain after DNS and cert are ready. Mid-campaign, price changes; new zip publishes in minutes; rollback ready if the wrong price slips. Email delivery is handled by the form provider, not SiteHost (mail hosting is not included).

When the workshop ends, the page becomes “sold out — join next list” with one publish. No server to decommission.

Example: bakery seasonal catering push

A bakery already has an evergreen brochure on Starter. For holiday catering, they add a second site on Pro with a single landing page and a form for tray orders. Ads point at catering.corneroven.example. When January arrives, they publish “see you next November” and stop ad spend. The main menu site never carried stale holiday pricing. Staging on Pro lets a partner review the catering page before DNS goes public.

When a landing page should become a larger site

If you need navigation to six service lines and a blog, you are leaving pure landing territory — see brochure and one-page website hosting and where to host a small business website. If you need WordPress editorial tools, that is a different kind of hosting.

Copy and design constraints that affect hosting less than you think

Hosting will not fix a fuzzy offer. Before upload, ensure the headline states the job, the button repeats the job, and distractions are gone. Then compress the hero. Then publish to SiteHost and test the form on HTTPS preview.

For paid campaigns, create a naming habit: local zip launch-april-v3.zip, matching note in your ads spreadsheet, and a rollback target you trust. If creative and media buyers argue, use Pro staging or a second site rather than overwriting the only URL that is receiving spend.

Legal and trust snippets worth including

Even short landers benefit from: who you are, how to contact a human, and a privacy sentence if you collect emails. Link to a fuller policy page if you have one. HTTPS helps browsers trust the transport; clear identity helps humans trust the offer. SiteHost provides the transport side on preview immediately and on your domain after DNS verifies.

Metrics you can watch without a data team

If you add analytics, watch: visits, button clicks, form starts, form completes. If forms complete on preview but not on the custom domain, suspect mixed content, ad-blocker differences, or a wrong domain in the form provider settings — not “DNS vibes.” Fix layers separately.

Launch checklist (print this)

  1. Job sentence written
  2. index.html opens locally with relative assets
  3. Hero compressed
  4. Form test succeeds on HTTPS preview
  5. Privacy sentence present if you collect email
  6. Ads still off until custom domain certificate works
  7. Rollback zip saved locally
  8. Mail / form provider confirmed separately from SiteHost

Skip any step and you are gambling with spend. Hosting is the easy part when the checklist is honest.

Questions people actually ask

Can I host only one file?

Yes — a site can be a single index.html plus assets. Root still matters.

Do I need Google Analytics?

Optional. Add the script yourself if you want it; respect privacy norms and consent rules in your region.

Is staging required for landing pages?

Nice to have (Pro). Otherwise preview URL + rollback is a workable poor man’s staging.

Will SiteHost send my newsletter?

No. Use an email tool; link from the page. SiteHost does not include email hosting.

How fast can I take a failed campaign down?

Publish a simple “campaign ended” page or roll back to a holding page. DNS can keep pointing here.