Landing pages are temporary; hosts should not be confusing

A static landing page is a focused file set: headline, proof, CTA, maybe a pixel. Where you host it should optimize for fast publish, HTTPS preview for stakeholders, clean teardown, and no surprise platform features you must learn under deadline.

StaticHost hosts finished files—HTML, CSS, JavaScript, images, fonts, and generator output. You build locally or in CI you control. The platform does not run npm, Hugo, or Jekyll for you. Upload a zip of the site root or connect GitHub to a tree that already contains those files. HTTPS is available on the preview hostname immediately; custom-domain certificates issue only after DNS verifies. nginx is effectively try_files $uri $uri/ =404 with no SPA fallback to index.html. There is no email product and no bundled CDN product. Plans: Starter $9/mo (1 site, 2 GB), Pro $30 (3 sites, 10 GB, staging), Scale $65 (10 sites, 30 GB), Business $130 (30 sites, 100 GB, teams). Short trial (~1 day); no forever-free tier.

Pair with hosting for a small static website, host a campaign landing page, and host a static landing page.

What this host is for landing pages

A release valve for HTML you already exported from Figma-to-code, a static generator, or hand markup. Staging on Pro helps legal review. Deploy history helps when the wrong price sneaks into production. Separate site slots keep a flash sale from living inside your evergreen marketing tree.

What this host is not

Not an A/B testing suite. Not a marketer’s email ESP. Not WordPress landing-page plugins. Not a place to import a database. Not unlimited experiment subdomains beyond your plan’s site caps. Not a promise that invented client-side routes will rewrite to index.html.

Decision criteria

  • Speed. Hours matter—file upload beats learning a new IaC module mid-campaign.
  • Review. Preview URLs without DNS reduce registrar tickets mid-campaign.
  • Isolation. Prefer one site per campaign when you may delete it later.
  • Compliance copy. Staging slots (Pro+) beat editing live.
  • Post-campaign. Artifact portability: your zip leaves with you.
  • Pixels and forms. Third-party scripts and form endpoints are fine; server-side mail is not provided.

Worked example: personal blog home page

Strange but common: your “landing page” is the home of a personal blog you use to collect newsletter signups—a single static home with a CTA to an external ESP, not a full CMS.

You host the home (and maybe a few posts as static HTML) on StaticHost. The ESP holds subscribers. You do not need WordPress. You do not need a VPS. Preview the home, then attach the domain. Starter ($9) covers it.

If the blog later grows into heavy documentation, revisit structure—but the landing/home hosting decision remains file-first. Keep / as a real index.html with the CTA; do not invent /signup as a client route without a file.

Failure: skipping a database dump on a WordPress move

Marketers sometimes “convert” a WordPress landing page to static by copying theme files and media, then pointing DNS at StaticHost—without exporting post/page content from the database. The PHP files do not run. The pages are empty shells. The campaign URL goes dark for real content while DNS looks “successful.”

If you are leaving WordPress for a static landing page, export the copy first, rebuild as HTML, then host. A database dump belongs in a WordPress migration between PHP hosts—not on StaticHost. Skipping it is fatal in either story; on static hosts it fails closed because there is nowhere to import the dump.

Do not rename WordPress site URLs toward the new domain before the static HTML exists. You will break the old page and still have nothing new to show.

Choosing under a deadline

Ask: Do I have HTML now? Do I need the host to build? Do I need mail? Do I need SPA fallback? If the answers are yes, no, no, no—StaticHost is a clean “where.” If any answer flips, change host class instead of forcing features.

Keep a launch checklist sticky note: preview CTA, preview legal footer, preview pixel network calls, then DNS, then cert, then paid traffic. Skipping ahead is how “simple landing page hosting” becomes a weekend incident.

Questions people actually ask

Can I host many campaign pages at once?

Yes within plan site limits—Pro 3, Scale 10, Business 30—or host paths under one site if you accept shared lifecycle.

Is preview enough for client sign-off?

Usually yes. Share HTTPS preview; cut DNS after written approval.

Will StaticHost send the campaign email?

No. Use your ESP. The landing page is files only.

What about forever-free landing hosts?

They exist for experiments. StaticHost is paid ($9+) after a short trial for commercial predictability—not free forever.