Serving & output
How visitors get the file, Public Base URL, and the HTML tidy-up.
Tivlo writes HTML under wp-content/tivlo-static/ and, when Serve
static HTML directly is on, sends those files to logged-out GET/HEAD
requests. A hit includes X-Tivlo-Static: hit and WordPress can stop
cooking. Generation requests (X-Tivlo-SSG) always render live so the
exporter never photographs a photograph.
Only the HTML document is static. CSS, JS, uploads, admin, REST, AJAX, feeds, POST forms, and (by default) logged-in sessions still go through WordPress. WooCommerce cart, checkout, and account pages are never exported.
If that sounds like “half the site is still WordPress” — yes. That is the point. You freeze the brochure. You leave the cash register alone.
Static Serving
When a request is served from disk, headers, and what stays dynamic.
Public Base URL
Rewrite links when HTML lives on a different domain than WordPress.
Optimization & Assets
External CSS/JS, stylesheet bundles, and the HTML compactor.
Same origin vs another host
| Setup | Public Base URL | Who serves HTML |
|---|---|---|
| Visitors hit this WordPress install | Leave blank | Tivlo, from tivlo-static/ |
| WordPress is CMS-only; HTML is on another domain | Set to the live origin, then Full Rebuild | The static host; you deploy the export folder |
Optimization runs when files are written, not when an editor previews live WordPress. Toggle options, then rebuild so existing HTML catches up. Logged-in preview will still look “unminified.” That is your editor view, not a broken optimizer.
Skip logged-in users
That setting is on by default. Use a private window to confirm static serving. See Verify Your Export.
How is this guide?