AI Landing Page Prompts with a Clear Build Brief
A landing page has one primary job: help a specific visitor decide whether to take the next step. Your AI brief should connect each section to that decision instead of asking for a list of fashionable effects.
UI Discovery editorial · Updated
How to use this guide
Write the offer before the layout
Name the audience, the problem, the result and the next action in plain language. If the offer is unclear, adding a bento grid will not clarify it. Decide whether the CTA starts a demo, opens a form or navigates to a product; give the builder a real destination or a labelled demo state.
Use only proof you can support
Provide approved testimonials, figures and customer logos separately. When none exist, show the product workflow or an original demonstration. Do not ask a model to fill a trust section with invented businesses or performance claims.
Review the whole reading sequence
Read the page from hero to final CTA at a phone width. Each section should answer a new question rather than repeat the headline. Keep terms and important limitations near the relevant offer, and ensure image-heavy sections still communicate with images unavailable.
Original prompt to adapt
An editorial starting brief, not a benchmarked model output. Replace fictional content and review the result before publishing.
Build a landing page for a fictional shared reading-list app for small design teams. The audience is teams that lose references in chat. The primary CTA is 'Explore the demo' and should navigate to a clearly labelled local demo. Structure the page as: one-sentence value proposition, sample collection preview, three workflow steps, collaboration details, sample pricing with billing period, FAQ and final CTA. Use original copy and explicitly labelled fixture content. Do not invent customer logos, testimonials or usage statistics. Reuse this project's components and typography. At 390px and desktop widths, preserve readable text, visible keyboard focus and a single dominant CTA per section. Avoid layout shifts by reserving image space.
A focused follow-up
Review each section against the visitor's questions. Remove repeated benefit claims, clarify the demo destination and keep pricing assumptions visible beside the CTA.
Review checklist
- Every CTA has a real destination or a labelled demo response.
- Claims are supplied by the product owner or explicitly marked as examples.
- The mobile reading order matches the visual hierarchy.
Continue with real references
- Landing page examples →
Study offer-to-section sequencing.
- Pricing page references →
Compare how plans, billing periods and limitations are explained.
Common questions
Can I use this prompt unchanged?
Use it as a starting brief. Replace fictional content, inspect the reference links and adapt constraints to your project. These are original editorial prompts, not benchmarked model outputs.
What should I check before publishing?
Every CTA has a real destination or a labelled demo response. Claims are supplied by the product owner or explicitly marked as examples. The mobile reading order matches the visual hierarchy.