AI landing page prompt: what to keep and what to change
A landing page prompt works when it states values instead of moods. Here is what a good one contains, what to keep from a page you start from, and how to build one section at a time.
· 5 min read
Ask an AI tool for "a modern landing page for my startup" and it has to guess everything: the fonts, the colours, the sections, the copy. Those guesses are why so many generated pages look alike. A prompt that holds up names the values, so there is less to guess and less to correct.
What a working page prompt contains
Every prompt Herofold writes for a live page is read from that page's built files. Its headings make a useful checklist for any page prompt, including one you write yourself:
- Role and brief: who the tool should act as, the brand, what it is, the audience, how the product uses AI and the one signature interaction.
- Page: the title, the meta description, the real headline, the navigation labels and the buttons.
- Sections, in order, each with its heading.
- Type: every font with its source, the font tokens, and the headline and body rules.
- Colour: every token with its value.
- Space, corners and breakpoints: size tokens, the radii in use and the media queries.
- Behaviour: the libraries, what the scripts do, and a still final state under prefers-reduced-motion.
- Media: real paths and pixel sizes, so your own images drop in.
- Rules and output: what not to add, the accessibility basics, and which files to return.
Here is part of Herofold's prompt for Lumen QA. Each line is a value the tool can match, not a mood it has to interpret.
## Sections, in this order
1. header#vf
2. section#hero: Users notice two things.
3. section#flags: It can tell a rendering quirk from a broken checkout.
4. section#review: From 1,204 changes to the 2 that matter.
## Type
- Headline: font 500 clamp(52px,6.9vw,104px)/.94 var(--display); letter-spacing -.035em
- Body: family var(--text); size 18px; weight 400; line-height 1.5What to keep
When you start from a finished page, its structure is the part that took the time. Keep:
- The section order and the job each section does.
- The signature interaction. On Lumen QA it is a scroll-driven product tour where the interface changes state step by step.
- The type scale, colour tokens, spacing and radii. If you want to change them, do it later, on purpose, in one pass.
- The rules: one h1, keyboard reachable controls, visible focus and tap targets of 44px or more.
Herofold's prompts also say outright: do not add effects the page does not have, such as drop shadows, glow, glass, gradient text or emoji. Keep that line in anything you send.
What to change
- The brand, the one-liner and the audience.
- How the product uses AI. Say what the system does, with what input, and what the person still decides.
- The headline and the button copy. Write them yourself, or give the tool a length and a subject.
- Numbers, quotes and logos. Every brand on Herofold is a concept, so replace them with your own before you publish.
- Photos and video, at the same paths and sizes as the originals.
Change one layer at a time: copy first, then images, then any colour or type change. If you change everything in one message, you cannot tell which instruction caused a problem. A copy pass can be as short as this:
Keep the layout, type, colours and the scroll-driven product tour as they are.
Change only the copy:
- Brand: Northdesk
- One line: A support inbox that drafts replies from your help centre.
- Headline: under 8 words, about the replies a support lead no longer writes.
- Keep "Start free trial" as the main button.
Do not add sections. Return only the files you changed.Ask for one section at a time
A whole page in one message is a long answer to get right. A section is short enough to check in a minute. Blocks are 310 single sections and components taken from live pages, each with its own prompt written to drop into a page that already exists.
Every block prompt uses the same headings: Goal, Structure, Type, Colour, Spacing and lines, Behaviour, Responsive, Accessibility, Built values (from its code.html), Content to replace, Rules and Output. When Herofold tested the format on builders with no other context, the type families, hex values, sizes, durations and whether a script is allowed all had to be said outright, so each one has its own heading.
Take Open an account in minutes, a free how-it-works section from the bilingual fintech page Daftar. Near the end, its prompt lists the parts you replace, in square brackets:
## Content to replace
- [Heading]: six to eight words, with a break
- [Steps]: three under 12 words each, in order
- [Call to action]: three words at most
- [Phone title]: one instruction under 8 wordsFill the brackets before you send the prompt, or send it as it is and give the replacements in your next message. The prompt asks for the block in one piece: the markup, one style block and a small script only if the behaviour needs one, with every class prefixed blk- and the colours and sizes in CSS variables at the top. That makes it easy to paste into a page you already have and bring into its colours.
Stacks: several blocks as one page
To build a page from sections that come from different pages, press Add to stack on each block, up to 12, then Copy page prompt. The stack prompt:
- puts the blocks in page order, navigation first and footer last;
- takes the first block's type scale, colour set and spacing as the system and brings the others into line;
- keeps one navigation, one footer, one accent colour and one h1, on the hero;
- sets sections 96 to 128px apart on desktop and 64px on a phone.
The stack is kept in your browser only. A stack that holds a Pro block needs Pro to copy.
After the first answer, keep going section by section: fix the hero, then the next section, and so on. Each request stays small and each answer is quick to check. Saving tokens explains why that also costs less, and Using a payload covers running a whole page in your tool.