A generated landing page still has to be usable

Fast to make, easy to get wrong

An assistant can draft a whole landing page in minutes: hero, features, pricing, a call to action. It looks finished. Whether it works is decided by things the draft rarely checks: text contrast against its background, a sensible heading order, a focus outline you can see when you move through the page with a keyboard, buttons that say what they do.

Those are not polish. They decide whether a visitor using a screen reader, a keyboard or a bright phone screen outdoors can use the page at all, and they are among the things landing pages most often get wrong.

Start from something you can test

A design file has to be rebuilt in code before it does anything, and every rebuild is a chance to lose what the design got right. Starting from sections that are already implemented in plain HTML and CSS removes that step: the section you review is the section you ship.

It also makes the page testable. Contrast, heading levels, focus styles and link text can be checked against the real markup today, not described in a design note.

Let the model fill a structure, not invent one

A model asked for "a landing page" invents the structure and the copy together, and it tends to reach for the familiar: a vague headline, a features grid, three pricing tiers. Giving it a fixed set of sections and one prompt per section works better: one promise and one action for the hero, the reader's problem in their words, a few short steps for how it works, proof you actually have, and the same action again at the end.

Each prompt should also name its failure mode. A hero prompt that warns against stacking two promises, or a proof prompt that refuses invented testimonials, catches the usual mistakes before they reach the page.

Keep the tokens in one place

Colour, type, spacing and radius defined once as tokens, with the contrast of each text-and-background pair written next to it, mean a brand change cannot quietly break legibility. Changing a colour then shows its contrast immediately instead of after launch.

Putting it into practice

The Landing Page Design Kit provides seven landing sections as framework-free HTML and CSS, a token file with contrast ratios, one copy prompt per section with its failure mode, and an accessibility checklist of fourteen checks ranked by how often they fail. A worked example assembles a real page from the sections.

For copy that sounds like your company rather than every company, see calibrating a model on sentences you already published.