Landing-page prompts for Claude and ChatGPT

Start with the decision, then ask for the page

A good landing page prompt gives an assistant the information a designer and copywriter would ask for: audience, offer, evidence, constraints, and the desired action. A style description alone cannot supply those facts.

Use the prompts below as separate stages. Replace every bracketed field before running them. If you do not know an answer, ask the assistant to identify the gap instead of filling it with invented details.

Prompt 1: clarify the offer

Help me define a landing page offer for [business].
My audience is [specific people]. They struggle with [problem].
I can provide [real service or product].
The action I want is [enquiry / waitlist / demo / quote request].
Ask up to five questions that would change the page materially.
Then summarize the audience, offer, evidence, objections, and next step.
Label assumptions. Do not write the page yet.

This is useful when the product exists but the page feels unfocused. Review the summary before moving on. The brief worksheet gives you a reusable place to keep the answers.

Prompt 2: write the first draft

Use this approved brief: [paste brief].
Write a landing page with one headline, a short explanation,
three concrete benefits, relevant evidence, a process section,
answers to the main objections, and one primary action.
Use plain language appropriate to [audience].
Only use these verified facts: [facts].
Mark missing evidence as a question for me. Do not invent reviews,
customer counts, results, certifications, prices, or availability.

Read the copy without the design. Can a potential customer explain what is being offered and what happens after clicking? Resolve that before requesting visual polish.

Prompt 3: design and build

Turn the approved copy into a responsive landing page.
Brand inputs: [colors, type preferences, logo, authorized images].
Visual reference: [describe the qualities, not a request to copy a site].
Prioritize readable text, visible focus, labelled fields, good contrast,
and a usable mobile layout. Respect reduced-motion preferences.
Use real content throughout and no fake customer proof.

For Pageree, create one HTML document with inline CSS and JavaScript.
Use the supported asset and form workflows from the connected tools.
Save a private draft and show me the preview before publishing.

Avoid asking for a dozen competing visual styles. A clear hierarchy and a relevant illustration usually help more than decoration applied to every section.

Prompt 4: repair one problem

Inspect this page: [URL or supplied HTML].
The problem is [specific symptom].
Identify the smallest change that addresses it.
Explain the evidence, edit the existing page, and show a draft.
Preserve working form behavior and verified business facts.
Do not publish until I approve the change.

Give the assistant the actual symptom: the mobile button is off-screen, a label is missing, or a form does not reach the inbox. “Make it convert better” leaves too much room for unsupported guesses.

Prompt 5: review before publishing

Review the draft against the approved brief.
Check factual claims, the primary action, mobile readability,
keyboard access, form labels, error and success states, destination
configuration, title, description, canonical URL, and share image.
Separate issues you observed from checks that require a live test.
List unresolved questions. Do not claim a test passed without evidence.

Keep the workflow under your control

An assistant can draft content and call connected tools, but the quality of the inputs still matters. Review business facts and the public result. A private preview is not proof that the published form delivers correctly.

Use the prompt generator to assemble a first brief locally in your browser, then follow the Claude guide or ChatGPT guide for the actual publishing workflow.