Landing pages are single-purpose on purpose. Static hosting matches that focus: ship the page, measure the campaign, take it down or revise with a new zip. This guide covers who it is for, the publish path, and when another product fits better.
Who ships landing pages this way
If a contractor insists you need cPanel to be legitimate, ask what task cPanel would perform that zip-plus-preview does not. Often the answer is habit.
Phone testing is not optional. Wide monitors hide sticky-header bugs and oversized heroes. Open preview on cellular once per meaningful release.
Storage is a budget. Compress photos. Leave raw camera files on a backup drive, not in the web zip.
Publish path for campaign speed
- Confirm you have publishable files with
index.htmlat the intended root. - Fix relative paths; remove
file://and accidentalhttp://asset links where you can. - Zip carefully; extract once to verify structure.
- Create a SiteHost site; use the short trial to prove the publish.
- Upload the zip or connect GitHub; open HTTPS preview on desktop and mobile.
- Fix, republish, or roll back until preview earns trust.
- Point DNS at your registrar; wait for verification and the custom-domain certificate.
- Share the domain publicly — not the preview — after that certificate looks right.
That order prevents most self-inflicted outages.
When a landing page needs another stack
If a contractor insists you need cPanel to be legitimate, ask what task cPanel would perform that zip-plus-preview does not. Often the answer is habit.
Phone testing is not optional. Wide monitors hide sticky-header bugs and oversized heroes. Open preview on cellular once per meaningful release.
Storage is a budget. Compress photos. Leave raw camera files on a backup drive, not in the web zip.
Docs-folder export used as a lander
Storage is a budget. Compress photos. Leave raw camera files on a backup drive, not in the web zip.
If a contractor insists you need cPanel to be legitimate, ask what task cPanel would perform that zip-plus-preview does not. Often the answer is habit.
Treat dated zips as your memory. Labels beat heroic recalls after a bad publish. Rollback is there, but only if you know which artifact was good.
Do not point DNS early
Storage is a budget. Compress photos. Leave raw camera files on a backup drive, not in the web zip.
If a contractor insists you need cPanel to be legitimate, ask what task cPanel would perform that zip-plus-preview does not. Often the answer is habit.
Treat dated zips as your memory. Labels beat heroic recalls after a bad publish. Rollback is there, but only if you know which artifact was good.
Measuring without a CMS
If a contractor insists you need cPanel to be legitimate, ask what task cPanel would perform that zip-plus-preview does not. Often the answer is habit.
Phone testing is not optional. Wide monitors hide sticky-header bugs and oversized heroes. Open preview on cellular once per meaningful release.
Storage is a budget. Compress photos. Leave raw camera files on a backup drive, not in the web zip.
Tear-down and rewrite
Phone testing is not optional. Wide monitors hide sticky-header bugs and oversized heroes. Open preview on cellular once per meaningful release.
Custom domains live at registrars. Transfer is optional; pointing records is enough. Do not tangle mail DNS with website DNS casually.
If a contractor insists you need cPanel to be legitimate, ask what task cPanel would perform that zip-plus-preview does not. Often the answer is habit.
DNS before the lander is ready
Pointing DNS before the HTTPS preview looks right mixes two failure domains. Packaging mistakes, bad zips, and copy errors become indistinguishable from propagation delay. Campaign ads started while preview still showed placeholder headlines. Keep the preview private until humans approve layout, links, and embeds. Then change records at your registrar, wait for SiteHost verification, and confirm the certificate on the custom name. Ads, Google Business profiles, and printed materials should follow that confirmation — not lead it.
One more practical note on static hosting for landing pages
Keep the scope of static hosting for landing pages aligned with what SiteHost actually sells: static file hosting with immediate HTTPS preview and custom-domain certificates after DNS verifies. The worked reality for this article is a team exports a documentation folder and uses the intro page as a campaign lander, testing preview fully before dns for the campaign hostname. When someone tries to expand the project into server management, a website builder you do not have, or email inboxes on the same SKU, pause and separate products. Write down the public URL only after it is a domain you control. Keep a prior zip. Click the phone number or primary button yourself on preview. Related reading: easy static website hosting, website hosting for a one page website, and one page website hosting. If storage pressure appears, compress media before you climb from Starter to Pro; if site count grows, Pro’s three sites and staging are the usual next step; Scale and Business wait for larger portfolios and teams. That is the whole economics story without unlimited fairy tales.
Field notes you can reuse next month
Create a simple folder on your computer named for the site and the month. Drop every zip you publish into it. When a stakeholder asks what changed, open the folder instead of reconstructing history from memory. If you work with a designer, agree that they deliver archives that extract to index.html at the root. If you work with a developer who loves client-side routers, agree on real files for public URLs before anyone prints QR codes. If you are cost-sensitive, revisit whether you still need Pro’s staging or whether Starter covers the live property alone. If you are security-sensitive, re-scan your HTML for http:// after each vendor gives you a new embed snippet. If you are speed-sensitive, weigh images on a scale that is not a marketing graph — look at file sizes on disk. These notes are not glamorous. They are how static sites stay calm on SiteHost without cPanel, without a website builder, and without pretending email was included.
Questions people actually ask
Is SiteHost a fit for static hosting for landing pages?
If you have finished HTML/CSS/JS files (or a static export) and want zip or Git publish with HTTPS preview and a custom domain after DNS, yes. If you need a CMS runtime or inboxes, pick those products separately.
Is there a forever-free plan?
No. The trial is about a day; then you choose a paid plan such as Starter at $9/mo.
Does hosting include email?
No. Keep mailboxes with a mail provider and be careful with MX records when you only meant to point the website.
When do I point DNS?
After the HTTPS preview looks right. Custom-domain certificates follow successful verification.