On 54 a landing page is a static page with a form behind it: the entries land in records you can read and download, the page is served as plain HTML so it loads fast, and every version is kept so you can roll back after a bad edit.
A landing page has one job: get the visitor to do one thing. Everything else on it is in the way. The part most page builders get wrong is not the design, it is **what happens after someone fills the form** — the entries end up somewhere you cannot read, or in an inbox you cannot search, or nowhere at all.
Swipe to compare all columns →
| The usual page builder | 54 | |
|---|---|---|
| Where the signups go | An email you hope arrives, or a paid add-on | Records in your site, readable and downloadable from the admin |
| How fast it loads | A page that boots a framework first | Plain HTML and CSS, served from the edge |
| Changing the headline | Open the editor, find the block, edit, publish | Say what you want changed; the version before it is kept |
| A bad edit | Undo if you are lucky | Roll back to any earlier version in one click |
| Your own domain | Usually the first paid tier | Included in the free plan |
Written from each product's public documentation. Products change: check theirs before you decide. No prices here for the same reason.
Minutes. You describe the page and it comes back built; the slow part is you deciding what the one goal is.
Into records attached to your site. You read them in the admin and you can download them.
Yes, with the visits, the referrer and the path, per page.
You can publish one, keep the version, publish the other and compare. There is no automatic traffic split.
It is built responsive. You can also ask for a specific behaviour at phone width and check it.
Yes. Upload it or point at a web font.
Ask for it and it gets wired to the form.
Yes, from a mailbox on your own domain.
Yes, and you can make one in the studio if you do not have one.
Add pages to the same project. A landing page is not a different kind of thing here.