Long-form Landing Page Copywriting

This skill covers creating or improving one specific landing page whose primary goal is to move a reader to one clear action (purchase, start trial, book call, join waitlist, opt in).

The focus is on process, not rigid formulas. Frameworks (Pain–Dream–Fix, PAS, Why–Try–Buy, Four Forces) are lenses to mix and adapt, not step-by-step scripts.

When to Use This Skill

• User requests a landing page, sales page, or opt-in page for a specific offer
• User wants to improve or audit existing conversion copy
• User has a product, service, or course and needs persuasive long-form copy driving one primary action
• User mentions frameworks like PAS, Pain–Dream–Fix, or "sales page structure"

When NOT to Use This Skill

• Short-form copy: ads, social posts, taglines (different constraints, different rhythm)
• Brand or awareness pages: no clear CTA, goal is perception not action
• Email sequences: related techniques but different pacing and structure
• Product pages with many SKUs: those need a catalog/e-commerce approach, not single-offer persuasion
• Purely informational content: blog posts, documentation, FAQs not tied to a conversion goal

If the request is ambiguous, ask: "Is the goal to move the reader toward one specific action (buy, sign up, book a call)?" If yes, use this skill.

1. Before You Write: Context to Gather

Aim to understand the reader's world well enough that your copy feels like it was written from inside their day.

Decision rule for when to ask vs. when to proceed:

→ Must ask if you're missing any of these three:

1. The offer (what's being sold)
2. The audience (who's reading)
3. The primary CTA (what action the page wants)

→ State assumptions and draft for everything else (pricing details, traffic source, objections, voice-of-customer). It's faster to revise a draft than to interrogate the user through multiple rounds.

When you do ask, ask one question at a time. For example:

"Before I draft—what's the primary action you want readers to take: purchase, book a call, or start a free trial?"

Once you have offer + audience + CTA, begin drafting and flag assumptions inline (e.g., "Assuming traffic is mostly from paid ads—adjust if organic/referral").

Essential context

• Offer: what's being sold and the core promise.
• Audience: who is reading (role, situation, environment).
• Main job of the page: one primary CTA.

Extremely helpful if available

• Pricing: roughly how it's priced (if relevant to the page).
• Traffic source: ads, search, email, referrals, etc.
• Voice-of-customer (VoC): reviews, support tickets, emails, survey responses.
• Common objections and hesitations.
• Specific outcomes customers have achieved.
• Their own phrases for pains and wins.

If voice-of-customer data is missing, you may infer plausible language from the problem and audience, but make it easy for the user to later swap in real quotes.

2. Core Principles

Keep these in mind throughout the process:

1. Reader is the protagonist

   • Default subject of your sentences: "you", not the product.
   • Product is a supporting character that helps them get what they want.

2. One page, one job

   • Everything on the page should support one primary decision.
   • Secondary / step-down CTAs are allowed, but they exist to support the main job, not compete with it.

3. Frameworks as lenses, not chains

   • Pain–Dream–Fix, PAS, and Why–Try–Buy help you think:
     • Pain / Problem: their struggle now
     • Dream / Desired outcome: what progress looks like
     • Fix / Solution: how the offer bridges that gap
   • You can bend or reorder sections when it serves clarity and persuasion.

4. Four Forces of progress
   As you write, consider four forces acting on the reader:

   • Push: current pain pushing them to change
   • Pull: attraction of a better future
   • Anxiety: fears and uncertainties about the new solution
   • Habit: comfort and friction of staying with the status quo
     Strong pages increase push and pull, reduce anxiety, and challenge habit.

5. Concrete > abstract

   • Concrete scenes beat vague claims.
   • Make readers think "that is exactly what my Monday looks like."

6. Clarity over cleverness

   • Clear beats cute.
   • If a clever line obscures the message, rewrite it.

3. Research & Voice-of-Customer

When the user has raw customer language, use it heavily. If not, infer and label.

From whatever input you have, extract:

• Pains

  • What specific situations hurt?
  • What are they tired of? Embarrassed by? Afraid of?

• Dreams

  • What outcome would make them say "this was worth it"?
  • What does a good day look like after things are working?

• Current habits & alternatives

  • What are they doing instead of using this product (other tools, DIY, doing nothing)?

• Objections & anxieties

  • Price, time, learning curve, trust, fit, "this won't work for me," "my team won't use it."

• Trigger moments

  • What happens right before they start looking for this kind of solution?

You'll recycle this language in your hero, pain sections, proof, objections, and CTAs.

4. Planning the Page (Flexible Skeleton)

Start by sketching a loose outline. You can adjust order and emphasis as you learn more.

A simple adaptable skeleton:

1. Hero: who it's for + core struggle or promise
2. Pain: vivid scenarios, consequences, and angles on the problem
3. Dream: what life looks like when the job is done
4. Fix: introduce the offer as the bridge from pain to dream
5. Proof & "Why us": testimonials, stories, credibility, differentiators
6. Offer details: what they get, how it works, what happens after they say yes
7. Pricing & value framing
8. Objections & FAQs (anxieties + habit of the present)
9. "Is this for you?" qualifiers
10. Final call-to-action

You can drop in additional sections (e.g. origin story, comparison charts, bonus breakdowns) where they serve the argument.

5. Writing Workflow

Follow this process when drafting a new page.

5.1 Quick summary & assumptions

At the top of your response, briefly note:

• Offer & audience
• Primary CTA
• Traffic / context
• Key assumptions (if any)

This keeps later decisions coherent.

5.2 Draft the outline

Turn the skeleton into a page-specific outline:

• Adjust headings to match the product and audience.
• Note where CTAs will appear (you'll refine them later).

If the user wants collaboration, show the outline and invite comments; otherwise, use it as your internal map.

5.3 Write the hero section

Aim to earn a "that's me" reaction.

Include:

• Pre-headline (optional): call out audience or context.

  For freelance developers juggling too many projects…

• Headline: capture a sharp pain or compelling outcome.

  "Stop guessing which project will blow up this week."

• Subhead: clarify what the offer does and promise the bridge.

  Track capacity, see risks early, and keep every client in the loop—without another bloated PM tool.

• Short supporting copy: 1–4 sentences or bullets that build on pain and hint at the dream.

• Above-the-fold CTA: simple, concrete action (e.g. Start a 14-day trial, Book a 20-minute walkthrough), with optional microcopy to reduce risk (e.g. No credit card).

5.4 Develop the Pain sections

Stay in their world longer than feels comfortable.

• Describe 2–4 specific scenarios where the problem shows up.

• Use sensory details and time markers sparingly but meaningfully.

  It's Thursday at 4:52pm. Your inbox says 67 unread. Three clients are asking, in different words, "Are we going to hit the deadline?"

• Surface consequences:

  • Emotional (stress, embarrassment)
  • Practical (lost revenue, wasted time)
  • Strategic (missed opportunities)

Avoid pitching the product or telling them what they "should have done." You're there to understand, not judge.

5.5 Paint the Dream

Now show the job done.

• Write 1–2 short "after" scenes that map directly from the pains.

  You open your dashboard. Every project shows a clear status. You already know which one needs attention today—and which ones are safely on track.

• Include emotional payoffs:

  • Relief, calm, focus, confidence, pride, regained time.

• Avoid fantasy. The dream should feel like a plausible next chapter, not a different universe.

5.6 Introduce the Fix (the offer)

Only now (unless the user's context demands a different order) bring in the product.

• Name the offer and restate the core promise in reader terms.
• Explain the mechanism: how this practically bridges pain to dream.
• Contrast briefly with alternatives and DIY:
  • Not to trash them, but to clarify where this shines (speed, ease, completeness, expertise).

Structure ideas:

• "Here's how it works" (3–5 steps)
• "What you get" (modules, features, deliverables)
• For each item: what it is → what it does → why it matters to them.

5.7 Proof, objections, and CTAs

Proof

• Place testimonials and case snippets near the claims they support.
• Prioritize stories that mirror the reader's starting point and desired outcome.
• When you invent placeholders, label them clearly so the user can swap in real quotes later.

Objections & anxieties

• Turn top 3–7 objections into FAQ-style questions.
• Answer with empathy first, then explanation, then gentle nudge toward action.

  "What if my team won't use this?" → acknowledge past tool fatigue → show how this fits their existing habits → give a simple first step.

CTAs as a chain

Think of the page as a series of supported invitations:

• Early CTA: for returning or already-warm visitors.
• Mid-page CTA: after core proof or product tour.
• CTA after objections: for people who just needed reassurance.
• Optional low-commitment CTA (guide, mini-course, waitlist) near the bottom for those not ready to fully act.

Match each CTA's surrounding copy to the likely mindset at that scroll depth.

5.8 Final polish

Do a pass focused on:

• Flow: does each section naturally lead to the next?
• Clarity: any sentences you have to re-read, rewrite.
• Specificity: swap vague claims for concrete examples.
• Brevity: remove any sentence that doesn't strengthen the argument.

6. Concrete vs Abstract (Examples Across Copy Types)

Aim for language readers can picture instantly. Abstract claims slide off; concrete scenes stick.

Headlines

Abstract (weak)

"Improve your project efficiency and reduce miscommunication."

Concrete (strong)

"Stop starting Monday with five different versions of the plan and no one sure which one is current."

Why it works: The concrete version puts the reader in a specific moment (Monday), with a specific mess (five versions), feeling a specific frustration (no one's sure). They recognize it.

Testimonials & Proof

Weak placement & content:

"Great product! Really helped our team." — J.S., Marketing Manager

(Placed in a generic "What Our Customers Say" section at the bottom)

Strong placement & content:

After the section explaining how the dashboard surfaces at-risk projects:

"We caught a scope creep issue two weeks before it would've blown the deadline. That one save paid for a year of the tool." — Jenna S., Ops Lead at Redwood Agency

[If placeholder: label as (TESTIMONIAL PLACEHOLDER — swap for real quote about early risk detection)]

Why it works: The testimonial appears right after the relevant claim, includes a specific outcome (two weeks, one year ROI), and names a relatable role. It does the work of proof, not just decoration.

CTAs with Surrounding Copy

Weak CTA block:

Ready to get started? > [Sign Up]

Strong CTA block (mid-page, after product walkthrough):

You've seen how the dashboard works. You've seen how alerts catch problems early.

The next step is to try it with your own projects—no credit card, no 45-minute onboarding call.

Start a 14-day trial → > Set up takes under 5 minutes. Cancel anytime.

Why it works: The copy before the button summarizes what the reader just learned (dashboard, alerts), names the action clearly (try it with your projects), and reduces anxiety (no credit card, fast setup, cancel anytime). The CTA earns the click rather than just asking for it.

Quick Reference: Weak → Strong Patterns

Use this table as a quick gut-check when reviewing drafts.

7. Inaction, Habit, and Alternatives

Remember: often the main competitor is doing nothing or sticking with the clunky workaround.

• Acknowledge DIY and status quo honestly:
  • "You could keep tracking this in spreadsheets and chats…"
• Show where the offer changes the game:
  • Speed, reduced cognitive load, fewer errors, shared visibility, expert guidance.
• Offer a smaller step when appropriate:
  • Lite plan, free resource, low-friction trial, strategy call.

This respects the reader's autonomy while gently tilting the decision.

8. Auditing & Rewriting Existing Pages

When the user provides existing copy or a URL, consider this workflow:

1. Summarize the current page

   • Who it appears to target
   • What it's selling
   • How it's structured
   • Primary CTA

2. Diagnose issues

   • Is the product the protagonist?
   • Is the pain underdeveloped or too generic?
   • Is proof thin or misplaced?
   • Are anxieties ignored?

3. Suggest structural changes

   • Propose a revised section order using the flexible skeleton.
   • Explain briefly why changes help (e.g. "moves proof closer to big claim").

4. Rewrite key sections

   • Almost always: hero, first pain section, first CTA block.
   • Then as needed: product introduction, pricing/value, FAQ.

5. Show before/after examples

   • For a few representative snippets, show "Old → New" so the user can see your reasoning and extend the pattern.

9. Quality Considerations

Before delivering your draft or recommendations, scan through these:

• Consider whether the headline describes the reader's world, not just the product's features.
• Consider whether the reader is the main character in most sentences ("you" rather than the product name).
• Consider whether the page spends enough time in Pain and Dream before leaning heavily into Fix (unless context demands otherwise).
• Consider whether vivid details are directly tied to the reader's problem, desired outcome, or the way the offer works.
• Consider whether the copy uses concrete, picturable scenarios instead of generic claims.
• Consider whether CTAs appear at several logical points along the scroll, each supported by nearby copy.
• Consider whether the most important anxieties (time, cost, fit, risk, learning curve) are named and addressed explicitly.
• Consider whether the DIY / "do nothing" alternative is acknowledged and fairly contrasted with the offer.
• Consider whether the page would still sound unique if you swapped in a competitor's logo (if yes, make it more distinctive).
• Consider whether the tone feels like a helpful expert guiding a decision, not a hypey salesperson pushing everyone to say yes.

10. Style & Output Format

Unless the user specifies otherwise:

• Use clear, conversational language.
• Prefer second person ("you") and plain verbs.
• Avoid:
  • Hype, false urgency, or unrealistic claims.
  • Complex nested layouts; imagine a simple single-column page.
• Aim for:
  • Respectful persuasion grounded in the reader's reality.
  • Copy that can be easily adapted into HTML or CMS blocks.

When asked to critique or improve, focus on diagnosis + prioritized changes + rewritten key sections rather than rewriting everything by default.