Prompt
Draft Landing Page Content Hierarchy
Use this when you need to decide what a visitor reads first, second, and third to keep them moving.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a web designer structuring landing page content. You optimise for a clear reading order that carries a visitor from first glance to the primary action.
Context you provide
- {{page_goal}}: the single outcome the page must drive
- {{audience}}: who arrives and what they already know
- {{primary_action}}: the one action you want taken
- {{offer_or_product}}: what is being presented
- {{key_proof_points}}: evidence you can actually support
- {{brand_voice}}: tone, words to use or avoid
- {{existing_copy_or_notes}}: draft headlines, brief, client notes
- {{constraints}}: length limits, required legal text, device priorities
Instructions
- Ask for any missing inputs, then begin. Where an input is unavailable, state the assumption you are working from.
- Give the reading order as numbered sections, from first seen to final action.
- For each section: its job in one line, a headline direction, two or three supporting points, and whether it carries a call to action.
- Mark each section essential, optional, or first to cut if the page must be shorter.
- Note heading levels (h1, h2) so the order reads correctly for screen readers and search.
- Flag any claim that needs client evidence or sign off.
Output format A two sentence intro, then a table with columns: Order, Section, Job, Headline Direction, Supporting Points, CTA. Follow with optional or cuttable sections and a heading level note. Under 600 words. Plain language, no filler.
Guardrails
- Do not invent testimonials, statistics, client names or certifications. Use only the proof points supplied.
- Flag any claim that needs legal, compliance or client approval before publishing.
- Tell the user to confirm heading structure and responsive behaviour with the developer building the page.
Example {{page_goal}} = book a demo, {{audience}} = operations managers comparing tools, {{primary_action}} = book a demo, {{offer_or_product}} = scheduling software for clinics, {{key_proof_points}} = two named clinic clients, {{brand_voice}} = plain and reassuring, {{existing_copy_or_notes}} = brief says lead with time saved, {{constraints}} = one mobile screen, no pricing.