Prompt: Write Landing Page Copy

A prompt for landing page copy structured around one offer and one action, with proof points instead of vague claims.

The prompt

You are a conversion copywriter writing landing page copy for {{PRODUCT OR SERVICE}}.

Objective: Write the hero section and three supporting sections for a landing page whose single goal is {{PRIMARY GOAL — e.g. get a free trial signup}}.

Context: The visitor arrives from {{TRAFFIC SOURCE — e.g. a paid search ad for "team scheduling software"}}, so they already know roughly what the product does. The strongest proof point available is {{PROOF POINT — e.g. used by 40 independent coffee shops}}.

Constraints:
- Headline: under 12 words, states the outcome, not the feature
- Subheadline: under 25 words
- Exactly 3 supporting sections, each with a heading under 8 words and 1–2 sentences of body copy
- One call-to-action button label, repeated identically at the top and bottom
- Do not state a customer count, rating or statistic other than the proof point supplied

Output format: Return Markdown with a "# Headline", a subheadline line, the CTA button label on its own line, then three "##" supporting sections, then the CTA button label again on its own line.

Before finishing, check there are exactly 3 supporting sections, the CTA label is identical in both places it appears, and no statistic beyond the supplied proof point is used.

Example

Input

PRODUCT OR SERVICE: Shiftline, a team scheduling app for small retail teams
PRIMARY GOAL — e.g. get a free trial signup: start a 14-day free trial
TRAFFIC SOURCE — e.g. a paid search ad for "team scheduling software": a paid search ad for "staff rota software"
PROOF POINT — e.g. used by 40 independent coffee shops: used by 40 independent coffee shops to build their weekly rotas

Output

# Build the week's rota in minutes, not evenings

Shiftline turns your team's availability into a finished weekly rota, so managers stop losing evenings to spreadsheets.

Start your free trial

## Less time on the weekly rota
Build next week's rota in one place, instead of piecing it together from messages, notes and a spreadsheet every week.

## Made for small retail teams
Shiftline is built around how small retail teams actually schedule their staff, not around large enterprise workforce planning.

## Trusted by independent coffee shops
Shiftline is used by 40 independent coffee shops to build their weekly rotas.

Start your free trial

Why it works

Naming the traffic source lets the copy skip re-explaining what the product is and go straight to the outcome, matching visitor intent.
Fixing the section count at three prevents the scattershot page that tries to cover every feature instead of one clear case.
Restricting statistics to the single supplied proof point stops the model inventing customer counts or ratings that don't exist.

Why the basic version fails

“Write landing page copy for our product” tends to produce a features list dressed up as sections, a headline that describes the product rather than the outcome, and at least one invented statistic (“trusted by thousands”) that nobody supplied.

What this prompt fixes

Naming the traffic source means the copy can assume some existing context instead of re-explaining the product from scratch. Fixing the section count at exactly three stops the page sprawling into a features list, and restricting the copy to the one supplied proof point keeps every claim defensible.

Tips per model

Gemini does well when given an explicit output schema like the one here — it otherwise tends to add extra sections beyond the three requested.
Claude is reliable at keeping the CTA label identical top and bottom; check this manually if you switch models.
If the headline still reads like a feature (“Scheduling software for retail teams”), push the model to state the outcome for the visitor instead (“Build the week’s rota in minutes”).