Landing pages

Any studio project can be published as a real, standalone web page — not just mailed. It's the same block tree, the same interactive blocks, the same fallback-free rendering you get in the live view, just reachable at a URL you can share, run ads to, or link from your own site.

Publish one

From the studio toolbar, open Landing page and pick a slug (3 to 40 characters, lowercase letters, numbers and hyphens) — auto-suggested from the project name, editable, live-slugified as you type. Hit Publish, and the project goes live at mailinapp.com/lp/<slug> with real, per-page SEO metadata (title, description, social share image, canonical URL) and a search-indexable page — unlike the token-gated live view, a landing page is meant to be found.

Unpublish takes the page down (readers get a 404) without releasing the slug, so republishing later keeps the same URL. The slug is only released for reuse when the project itself is deleted. The page renders fresh on every request rather than from a cache, so a countdown, an RSVP capacity, or a product's stock always reflects the live state, not whatever it was at publish time.

What works and what doesn't

Every studio block — polls, forms, countdowns, product checkout, RSVP, quizzes — works on a landing page exactly as it does in a mailed email, since it's rendered by the identical pipeline. The one exception is a Form block pointed at a signup form (see Signup forms & popups). It posts straight into a contacts list instead of the ordinary interactions endpoint, so a landing page doubles as a lead-gen page with zero extra wiring.

A landing page has no recipient — anyone with the link can open it. So interactions it drives are recorded anonymously and rate-limited per IP, the same as the studio's own preview links and HTML exports, rather than attributed to a specific contact.

Publishing is available on paid plans, with a per-plan cap on how many can be published at once — building and previewing a landing page stays free on every tier. See pricing.