Landing Page Copy Writer
Write a full landing page where every section has one job and earns the next scroll.
Writes complete landing page copy section by section, from hero to close, with a stated job and scroll trigger per block, wireframe notes for design, and a flag on the section most likely to lose the reader.
Ready-to-use prompt
The prompt
Copy it as-is, then swap the bracketed placeholders for your own details before running it.
Role: You are a conversion copywriter writing a single landing page.
Context:
- Offer and price: {{offer}}
- Traffic source and what that visitor just clicked: {{traffic_source}}
- Audience awareness stage, unaware through most aware: {{awareness}}
- Primary conversion action: {{cta}}
- Proof assets, testimonials, numbers, logos, screenshots: {{proof}}
- Objections you hear repeatedly: {{objections}}
- Brand voice: {{voice}}
Task: Write the page section by section. For each section return:
1. Section name and its single job
2. The headline
3. The body copy, written not described
4. The scroll trigger, the reason the reader continues
5. A wireframe note: what appears visually beside this copy
Required sections: hero, problem restatement, the shift, how it works in three steps, proof, objection handling, offer detail, final close. Add or remove sections only if the awareness stage demands it, and say why.
Rules:
- The hero must match the message on the ad or link the visitor clicked.
- One idea per section, if a section carries two, split it.
- No section may repeat a claim already made, escalate instead.
- Every proof element must be attached to the specific claim it supports.
- The CTA wording must stay identical everywhere on the page.
- Separate publishable copy from editorial notes and unresolved inputs.
- Mark unsupported facts with lowercase snake_case placeholders; list publication blockers at the end.
- Specify mobile reading order when a wireframe places evidence beside copy.
Finish with: the section most likely to lose the reader, and a rewritten alternative for it.Estimated results
Editor's note
Why this prompt matters
Landing pages fail between sections more often than within them. Each block reads acceptably, nothing obviously contradicts, and yet the page has no argument — it is a stack of assertions the reader can abandon at any point without feeling they missed anything. This prompt writes to a different specification: one idea per section, an explicit job for each, and a stated reason the reader continues. It also anchors the hero to the traffic source, because the most expensive copy problem on most landing pages is that the page and the ad feeding it are selling different things.
Anatomy
Prompt engineering breakdown
Role
Context
Goal
Constraints
Output format
What you'll get
Expected output
Scenario and editorial choice
Illustrative offer: a downloadable project-quote worksheet for freelance designers. Visitors clicked “Stop forgetting revision work in your quotes.” They recognise the problem, so keep the problem section short. Assume an annotated worksheet screenshot is supplied; price remains {{price}} until verified.
Hero
Job: Confirm the clicked promise.
Headline: Put revision work in the quote—not outside it.
Copy: Map the work around your design deliverables before you send a price. Get a worksheet for turning project scope into an itemised quote.
CTA: Get the worksheet
Scroll trigger: Which parts of a project are easiest to leave unpriced?
Wireframe: Show the revision-planning area beside the copy.
Problem restatement
Job: Make the omission recognisable.
Headline: The deliverable isn’t the whole job.
Copy: Feedback calls, revision rounds and handoff preparation belong in your estimate too. Leave them unnamed, and your client cannot see what the price includes.
Scroll trigger: Introduce a different starting point.
Wireframe: Contrast a deliverables-only list with a fuller scope outline.
The shift
Job: Explain the approach.
Headline: Define the boundaries before calculating the total.
Copy: Start with what is included, what is excluded and what would require a new quote.
Scroll trigger: Show how that becomes a usable draft.
Wireframe: Three labelled scope fields.
How it works
Job: Make the process tangible.
Headline: Build your quote in three passes.
| Step | Copy | |---|---| | Map | List deliverables and supporting work. | | Estimate | Assign time and your own rates. | | Review | Check assumptions before sharing your quote. |
Scroll trigger: Let visitors inspect the actual worksheet.
Wireframe: Numbered panels following the worksheet’s order.
Proof
Job: Demonstrate the mechanism, not an unverified result.
Headline: See where assumptions become visible.
Copy: This annotated preview shows the fields for included work and exclusions.
Scroll trigger: Address fit.
Wireframe: Legible screenshot with those fields highlighted; no earnings claims.
Objection handling
Job: Resolve the pricing concern.
Headline: Your rates stay yours.
Copy: The worksheet organises your estimate; it does not choose your rates.
Scroll trigger: Clarify the purchase.
Wireframe: Expanded question-and-answer block.
Offer detail
Job: State the exchange.
Headline: Download the project-quote worksheet.
Copy: Price: {{price}}. Confirm file format and delivery details before publication.
Scroll trigger: Invite a decision.
Wireframe: Compact purchase summary.
Final close
Job: Prompt action.
Headline: Have a project to quote?
Copy: Start with its scope.
CTA: Get the worksheet
Scroll trigger: None; this is the decision point.
Wireframe: One button.
Likely dropout and alternative
The abstract shift section risks losing readers. Test: “Write ‘two revision rounds included’ before entering a price.” This makes the method concrete without promising a result.
Under the hood
Why this prompt works
Requiring a scroll trigger per section is what turns the output into a page rather than a document. It forces each block to end owing the reader something, which is the actual mechanism behind long pages that get read. The awareness-stage input then reorders everything correctly: a most-aware visitor who wanted the offer and got a problem-restatement section leaves, and no amount of good writing in that section repairs it. Attaching proof to specific claims rather than pooling it in a testimonial band keeps the evidence doing work where doubt appears.
Model fit
Best AI models for this prompt
ChatGPT
Best default. Holds a long multi-section structure across one pass without dropping blocks.
Claude
Strongest on one-idea-per-section discipline and on honest proof handling.
Gemini
Useful when you paste the ad copy driving traffic so message match can be checked directly.
When to use
- Drafting a campaign landing page after the offer and ad message are approved.
- Rebuilding a page whose hero contradicts its incoming ad.
- Investigating a conversion drop after analytics confirms the traffic is relevant.
- Preparing section-level copy and visual requirements for a designer.
When not to use
- Writing a long-form sales argument; choose a sales-page structure first.
- Refining an otherwise effective page; use a conversion copy audit.
- Lacking traffic-source information; inspect campaign links first.
- Making regulated claims without qualified human review.
- Establishing customer objections or results; use interviews, support records and verified data.
Get more from it
Pro tips
- 1
Set awareness from the clicked message; most-aware visitors need the offer sooner, not a longer problem story.
- 2
Keep scroll triggers, but label internal transition notes separately from publishable copy.
- 3
Supply real proof; use {{missing_proof}} rather than invented testimonials or results.
- 4
Test the flagged weak section’s rewrite while keeping surrounding sections unchanged.
- 5
Paste the exact ad headline and destination promise into {{traffic_source}}.
- 6
Provide literal button text in {{cta}}; check every occurrence before handoff.
- 7
For a second pass, request a claim-by-section map; replace repeated benefits with mechanism, evidence or purchase detail.
Don't ship this
Common mistakes
✗ A hero that does not match the ad the visitor clicked.
Fix — Supply the traffic source and enforce message match in the hero.
✗ Repeating the same claim in three sections.
Fix — Require escalation; a repeated claim reads as having nothing more to say.
✗ Different CTA wording in each section.
Fix — Lock one CTA phrase across the page.
People also ask
Frequently asked questions
Q.How much does the awareness stage change the output?
Substantially. A most-aware visitor wants the offer in the hero and treats a problem-restatement section as a delay, while an unaware visitor needs that section before anything else lands. Set it accurately.
Q.What is a scroll trigger?
The reason the reader continues past a section — an open question, an incomplete comparison, a promise the next block pays off. Without them a page is a stack of statements the reader can leave at any point.
Q.Should I use this for a long sales page?
Plan the argument first with the sales page structure prompt, then use this to write the sections. Long pages need a belief sequence before they need copy.