1.1 Build
Build pages your way - upload, or generate from scratch.
Upload what already works, or generate inside your templates - then test and translate without a rebuild.
Upload HTML or generate from templates
Keep the page that already converts, or scaffold from your own brand structure - not a generic block kit.
Draft and published stay separate
Preview privately, then promote atomically so visitors never see a half-updated page.
1.0
Two ways in
Most teams already have a page that works. Start from that one, keep the markup, or generate from your own templates.
Upload existing HTML
Drop a folder or zip, map the conversion goal, and publish ready to test.
Generate from templates
Structure and tokens stay yours. The model fills sections inside your brand kit.
- 01
Drop the files
HTML, CSS, JS, and assets as a folder or zip.
- 02
Map the goal
Point at the element or event that counts as a conversion.
- 03
Publish
Live on your domain, ready to test and translate.
Keep your markup. Map once, then publish ready to test.
2.0
Change markup by describing the change
Instructions are applied as a diff you can read and reject. HTML, CSS, and JS stay editable when you want full control.
AI edits stay inspectable
Proposed markup changes are a readable diff you can accept or reject before anything ships.
Code when you need it
Full HTML, CSS, and JS stay editable. AI is a shortcut, not a cage.
Prompt
Make the CTA full width on mobile and say start free trial
12
<a href="/signup" class="cta">−
Sign up14
</a>+
<a href="/signup" class="cta cta--block-sm">+
Start free trial14
</a>Readable markup diff. Accept or reject before anything ships.
3.0
Everything the page needs, in one place
Images, fonts, and scripts live with the page. Traffic assignment and event tracking start the moment you publish.
Assets ship with the page
Images per language, self-hosted fonts, and scripts with load strategy.
Live means testable
Published pages are ready for assignment and tracking with no separate integrate step.
Versioned, per language, with translated derivatives.
Self-hosted files so creative renders identically.
Registered per page with load strategy.
No indexing, no traffic assignment, shareable review link only.
On your domain, indexed, counted, ready for assignment.
4.0
Bulk link management and export anytime
See every outbound link across every page, language and variant in one table. Export static HTML, CSS and assets whenever you want - no proprietary format.
| Page | Destination | Parameters | Uses |
|---|---|---|---|
spring-offerEN | partner.example/join | utm_source=ll · cid=42 | 12 |
welcome-bonusDE | partner.example/join | utm_source=ll · cid=17 | 8 |
pricingEN | app.liftlander.com/signup | plan=growth | 5 |
Export any page as static HTML, CSS, and assets anytime. No proprietary format, no lock-in.
See what is includedFAQ
Builder questions
No. Uploaded markup is served as you provided it. LiftLander adds only the variant assignment and event hooks, and you can inspect exactly what those add.
Yes. Upload font files to the asset manager and register external scripts per page, with async and defer under your control.
It is strongest when constrained by your own template: structure, tokens and components are yours, and the model fills content. From a blank prompt, treat the output as a starting draft.
Editing is locked per page with a visible holder, and every save is versioned so you can roll back to any earlier state.
A draft is only visible via a preview link. Publishing promotes the draft atomically, so visitors never see a half-updated page.
Yes. Export static HTML, CSS and assets for any page or the whole site, at any time, on every plan.
Bring one page and see how far it goes
Free for 14 days, no card required. Larger teams can book a walkthrough instead.