Agencies need inventory, not mythology

Agency teams ship client microsites, campaign pages, and brochure rebuilds on tight calendars. Static website hosting for agencies works when each deliverable is a folder of prebuilt files and each client expects HTTPS, a custom domain, and a way to roll back a bad Friday deploy. StaticHost matches that shape: zip or GitHub artifact upload, HTTPS preview immediately, DNS next, certificate after verification. It will not run npm or Hugo on the server. It will not provide mailboxes, a built-in CDN product, cPanel, or forever-free hosting after a short trial. Monthly plans are Starter $9 (1 site, 2 GB), Pro $30 (3 sites, 10 GB, staging), Scale $65 (10 sites, 30 GB), and Business $130 (30 sites, 100 GB, teams).

If your pitch deck promises WordPress editing, server-rendered apps, or “any URL loads the SPA,” pick a different product. nginx configuration here is try_files $uri $uri/ =404—no soft SPA fallback to index.html.

Who on the team touches the host

  • Producers share HTTPS preview links before DNS is touched.
  • Designers/devs upload zips with index.html at the archive root.
  • Account leads care about staging on Pro+ so counsel and brand can review without clobbering production.
  • Ops deletes campaign sites after teardown windows so Scale does not become a junk drawer.

The publish ritual is boring on purpose: build locally, upload output, verify preview, then DNS, then cert. See also portfolios for static sites, choosing a static hosting provider, and HTML website hosting.

Publish path agencies should standardize

  1. Generator or export runs in CI or on a laptop—never “on StaticHost.”
  2. Artifact is dist, public, _site, or a hand-built folder; never node_modules.
  3. Zip contents so the homepage is not nested under an extra directory.
  4. Deploy to staging (Pro+) or preview; collect feedback; redeploy.
  5. Promote the known-good tree to production; attach client DNS; wait for verification and certificate.
  6. Record teardown dates for temporary campaigns; use deploy history when a hotfix goes sideways.

Standardizing this in a one-page runbook beats reinventing hosting policy per account manager.

Worked example: student class project as agency practice

An agency apprentice ships a class project: a five-page HTML site about local transit, graded on semantic markup and accessibility. The same workflow they will use for clients applies. They build locally in VS Code, compress images, zip with index.html at root, and upload to a Starter site during the short trial or a paid seat the studio already owns.

HTTPS preview lets the instructor review without the student pointing a personal domain yet. After the grade lands, the apprentice can attach a cheap domain, create DNS records, and wait for the certificate—learning the correct order before a paying client is in the loop. The project has no PHP, no email inbox requirement, and no client-side router that expects unknown paths to rewrite. When the semester ends, deleting the site frees a slot on Pro or Scale for real client work.

That rehearsal matters: agencies fail when juniors first meet DNS on a launch day with ads already spending.

Failure to avoid: changing WordPress URLs before HTTPS exists

Agencies migrating brochure sites off WordPress sometimes run a search-replace to https:// while the static rebuild (or the interim host) still has no working certificate on the vanity domain. Browsers then show padlock failures, mixed signals in Search Console, and half-updated content in the database if they are still on PHP during transition.

On StaticHost the safe sequence for a static rebuild is different: publish files to HTTPS preview first, confirm assets load, only then point DNS, and only after verification expect the custom-domain certificate. If you are still on WordPress elsewhere, do not rewrite siteurl to HTTPS on a hostname that cannot terminate TLS yet. Finish TLS, then rewrite. Treating URL replacement as a step that can outrun certificate reality creates emergency weekends. StaticHost will not run WordPress at all—so if you stay on WP, stay on a PHP host and sequence HTTPS properly there; if you leave WP, leave the database behind and ship HTML files with relative or HTTPS-ready absolute URLs tested on preview.

When agencies should buy something else

Buy a PHP host for WordPress retainers. Buy a functions platform when the microsite is secretly an app. Buy mail from a mail vendor. Buy a CDN product if procurement requires a CDN SKU checkbox—StaticHost does not include one. Buy forever-free Pages for internal sandboxes if policy allows and $0 forever is mandatory.

Stay on StaticHost when the commercial need is many static properties, staging discipline, and reversible file deploys. Quote Scale ($65) when the calendar implies eight microsites; quote Business ($130) when seats and thirty-site inventory matter. Do not quote “unlimited.”

Client-facing language that prevents scope fights

Say: we host prebuilt files; we build in our pipeline; preview is HTTPS before DNS; certificates follow verification; routing returns 404 for missing files; email and CDN are separate. Do not say: unlimited bandwidth mythology, free forever, or “it works like Netlify redirects.” File-oriented honesty keeps retainers calm.

Inventory math without soft lies

Count every microsite that still answers on a hostname. Campaign leftovers from last quarter count. Client “temporary” pages that never died count. If the real number is eleven, Scale ($65) is the honest quote—not Starter with creative sharing. Storage follows the same honesty: Business at 100 GB exists for media-heavy books, not because every brochure needs it. Compress before you escalate tiers. Delete before you escalate tiers. The product’s ceilings (1/3/10/30 sites, 2/10/30/100 GB) are the commercial contract; pretending otherwise creates invoice surprises mid-retainer.

Pair teardown calendars with ad flight end dates. When the flight ends, remove the site or park a single “campaign closed” HTML file if legal needs a residual URL—still a file, still within =404 rules for everything else.

FAQ

Which plan fits a five-client static book?

Often Pro ($30) if each client is one site and you need staging; Scale ($65) when site count approaches ten.

Can StaticHost build our Hugo theme on upload?

No. Run Hugo locally or in CI; upload the output directory only.

Why do client deep links 404 after we migrated an SPA?

No index.html fallback. Emit real HTML paths or hash routes, or use a platform that sells SPA rewrites.

Is agency email included on Business?

No plan includes mailboxes. Use a mail vendor regardless of tier.