landing-page-copy

$npx mdskill add rampstackco/claude-skills/landing-page-copy

Write landing page copy to drive conversions

  • Identifies and addresses user pain points succinctly.
  • Deploys natural language generation for dynamic content creation.
  • Analyzes target audience data to tailor messaging effectively.
  • Delivers optimized landing pages with high conversion rates.

SKILL.md

.github/skills/landing-page-copyView on GitHub ↗
---
name: landing-page-copy
description: "Write landing page copy with attention to the hero, value proposition, social proof, objection handling, and conversion-focused CTAs. Use this skill whenever the user wants to write a landing page, sales page, hero section, or any conversion-focused web copy. Triggers on landing page, sales page, hero copy, value proposition, headline, subheadline, hero section, CTA copy, conversion copy, opt-in page, squeeze page. Also triggers when the user has a marketing campaign or product launch needing dedicated conversion copy."
category: content
catalog_summary: "Landing pages, sales pages, hero-to-CTA flow"
display_order: 4
---

# Landing Page Copy

Write copy for pages with a single conversion goal: signup, purchase, demo request, download, lead capture. Stack-agnostic.

This skill is narrower than `content-and-copy`. Landing pages exist to drive a specific action, not to inform broadly.

---

## When to use

- Writing a hero section for a homepage or product page
- Writing a sales page or long-form sales letter
- Drafting opt-in or lead-capture page copy
- Campaign-specific landing pages
- Pricing page copy
- Demo or signup CTAs

## When NOT to use

- Long-form blog content (use `content-and-copy`)
- Email sequences (use `email-sequences`)
- Brand voice definition (use `brand-voice`)
- Page design and layout decisions (use `design-standards`)

---

## Required inputs

- The product, service, or offer
- The target audience and the specific objection they bring
- The conversion goal (one specific action)
- Brand voice
- Existing customer language (testimonials, support tickets, sales calls)
- Any constraints (length, format, regulatory)

If audience is unclear or objections are unknown, run `brand-discovery` or pull from sales call recordings before writing.

---

## The framework: 7 sections

A landing page does seven things in sequence. The structure can flex (combine, reorder, expand), but the elements stay constant.

### 1. Hero

The first 3 to 5 seconds. Decides whether the visitor stays.

**Three components:**

- **Headline.** The promise. Specific, outcome-focused, free of cliche.
- **Subheadline.** The mechanism. How you deliver the promise.
- **Primary CTA.** The action. One button, descriptive label.

**Strong hero patterns:**

- **Outcome + audience + mechanism.** "Ship features 3x faster, for engineering teams who hate meetings, with our async-first project tool."
- **Pain reversal.** "Stop losing customers to slow page loads."
- **Surprising claim.** "The note-taking app that gets used. We have data."
- **Direct address.** "You have 47 unread Slack messages. Here's what to do about it."

**Weak hero patterns:**

- Generic adjective stacking ("Powerful, intuitive, scalable")
- "Welcome to our platform"
- Brand-name-only headlines ("Acme: The Future of X")
- Vague benefits ("Streamline your workflow")

### 2. Social proof (early)

Within the first scroll, prove someone else trusts you.

**Forms:**
- Customer logos (recognizable beats unknown)
- Quantitative trust signal ("Over 10,000 teams")
- One strong testimonial with name and role
- Press mentions (logos of where you've been featured)

**Placement:** Right below the hero, before the visitor invests in reading more.

### 3. Problem / promise

Establish that you understand the visitor's situation.

**Pattern:**
- 1 to 3 paragraphs naming the specific problem
- Use the visitor's language (mined from research, not your marketing language)
- Stop before you sell. Resonate first.

**Test:** Read the problem section aloud. Does the target audience nod? If they don't, you don't understand them yet.

### 4. Solution / mechanism

How you solve the problem. The "what we actually do" section.

**Effective structure:**
- One headline summarizing the solution
- 3 to 5 specific features or capabilities, each with a 1-2 sentence explanation
- Each feature framed as the benefit it produces, not the technical detail
- Visual support (screenshots, illustrations, video clips)

**Failure mode:** Listing features without translating to outcomes. "Real-time collaboration" is a feature. "Edit together without copying-pasting from email" is the outcome.

### 5. Proof and detail

The expanded social proof and case studies section.

**Components:**
- 1 to 3 detailed case studies (specific customer, specific outcome, specific numbers)
- Multiple testimonials with attribution
- Specific data points (usage stats, success metrics, growth)
- Awards, certifications, or third-party validation

The deeper proof section is where committed visitors convert. Skim-readers won't make it here, but the ones who do are ready to buy.

### 6. Objection handling

Anticipate the reasons people say no. Address them directly.

**Common objection types:**
- **Price.** "Is this worth it?"
- **Time.** "Will this take forever to set up?"
- **Trust.** "Will this actually work for my situation?"
- **Risk.** "What if I commit and it's wrong?"
- **Comparison.** "How is this different from [competitor]?"
- **Implementation.** "Can my team handle the change?"

**Handling formats:**
- **FAQ section.** Structured, scannable.
- **Comparison table.** Vs. competitors or vs. alternatives.
- **Risk reversal.** Money-back guarantee, free trial, no-contract terms.
- **Proof of effort needed.** "Setup takes 5 minutes, not 5 weeks."

### 7. Final CTA

The closer. Re-state the offer. Re-state the action.

**Strong final CTAs:**
- Repeat the primary CTA from the hero (consistency)
- Frame in terms of the visitor's situation ("Get your team set up in 5 minutes")
- Remove friction ("No credit card required")
- One action only (avoid offering 5 alternatives that paralyze decision)

**Avoid:**
- Multiple CTAs competing for attention at the bottom
- New offers introduced only at the bottom (visitor is now confused)
- Long forms that ask for more information than needed for the action

---

## The CTA itself

Buttons matter. Treat the button copy as a whole-page-worth of attention.

**Strong CTA patterns:**

- **Action + outcome.** "Start your free trial," "Get my pricing," "Send me the guide"
- **First-person.** "Show me how" outperforms "Show you how"
- **Specific.** "Book a 15-minute demo" beats "Contact us"
- **Low-friction.** "Free trial, no credit card" reduces commitment cost

**Weak CTAs:**
- "Submit" (functional but lifeless)
- "Click here" (no value statement)
- "Learn more" (vague; about what?)
- "Get started" (started doing what?)

---

## Workflow

1. **Confirm the offer.** What exactly is being offered? At what price (if any)? What does the visitor get?
2. **Confirm the audience and objection.** Specific segment. The specific worry they bring.
3. **Mine the language.** Customer testimonials, support tickets, sales calls. Use real customer phrases.
4. **Draft the hero.** Headline, subheadline, CTA. Test 5 to 10 variations.
5. **Build the structure.** All 7 sections in order. Sections can combine for shorter pages.
6. **Draft sections.** Section by section. Don't polish until the structure is sound.
7. **Edit for friction.** Remove every word that doesn't earn its place. Landing pages do not have words to spare.
8. **Test the CTA.** Read the page aloud. By the end, is the visitor's next action obvious?
9. **Pre-publish:** check links, spell-check, mobile preview, SEO basics if SEO is a goal.

---

## Failure patterns

- **Hero that explains instead of sells.** "We're an X for Y" is description. "Get X without Y" is sell.
- **Feature lists with no outcomes.** Features without benefits read as a spec sheet.
- **Generic testimonials.** "Great product!" is worth less than nothing. "We cut onboarding time from 2 weeks to 4 days" is gold.
- **Multiple competing CTAs.** Pick one primary action. Everything else is noise.
- **Walls of text.** Visitors scan. Use short paragraphs, bullet lists, and visual breakpoints.
- **No social proof.** Trust is the first hurdle. Without proof, the rest of the page does not earn the chance to be read.
- **Mismatched headline and CTA.** Hero promises X, CTA asks for Y. Visitor confused.
- **Writing for everyone.** "Our solution works for any business" appeals to no one. Specificity converts.
- **Ignoring mobile.** Most visitors are on mobile. Test the page at 375px first.

---

## Output format

Default output is a structured markdown document for the page, with each section labeled. The markdown is ready to import into the CMS or hand to design.

Structure:

```markdown
# [Page Title]

## SECTION: Hero
- Headline: [text]
- Subheadline: [text]
- Primary CTA: [button text]
- Supporting cue: [optional, e.g., "No credit card required"]
- Hero visual notes: [if any]

## SECTION: Social proof (early)
- Logo bar: [list customer/press logos]
- Trust statistic: [if any]

## SECTION: Problem / promise
[2 to 3 paragraphs]

## SECTION: Solution
- Headline: [text]
- Feature 1: [headline + description]
- Feature 2: [headline + description]
- Feature 3: [headline + description]

## SECTION: Proof
- Case study 1: [customer, outcome, numbers]
- Testimonials: [list]
- Data points: [list]

## SECTION: Objection handling
- FAQ: [questions and answers]
- OR Comparison table: [vs alternatives]
- OR Risk reversal: [guarantee, terms]

## SECTION: Final CTA
- Headline: [text]
- Final CTA button: [text]
- Supporting cue: [optional]

## Variants for testing
- [Alternate headlines]
- [Alternate CTAs]
- [Alternate proof framings]
```

---

## Reference files

- [`references/hero-formulas.md`](references/hero-formulas.md) - Patterns and formulas for hero headlines.
- [`references/objection-library.md`](references/objection-library.md) - Common objections by category, with handling strategies.

More from rampstackco/claude-skills

SkillDescription
ads-creative-developmentHow to produce ad creative that converts at performance scale. Hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms. Triggers on ad creative, ad design, hook patterns, ad video pacing, creative testing, ad variations, creative refresh, creative fatigue, refresh ad creative, video ads for Meta, TikTok creative, LinkedIn ad creative, ad asset library. Also triggers when a team is producing creative at scale, planning a creative test cycle, or auditing why creative is not converting.
ads-performance-analyticsHow to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media dashboard, attribution analysis, ROAS vs LTV, multi-platform reconciliation, ad incrementality, geo holdout, conversion lift study, ghost bidding, paid media reporting, board-deck paid media metrics, blended CAC, MMM, MTA, last-click attribution. Also triggers when a marketer is about to scale, kill, or rebudget a campaign based on platform metrics, or when reconciling platform reports against warehouse revenue.
after-action-reportRun a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.
ai-content-collaborationHow humans and AI compose in content workflows. Where AI legitimately participates, where humans must own, hybrid workflow patterns, voice ownership preservation, the AI slop problem, disclosure and transparency, team calibration, and the ethics of intellectually honest AI-assisted content production. Triggers on AI content workflow, AI-assisted writing, hybrid content production, AI in editorial, AI slop, AI disclosure, AI usage policy, AI content ethics, voice preservation with AI, team AI calibration. Also triggers when content feels generic despite quality tools, when team AI usage has drifted into inconsistency, or when a regulated or trust-sensitive context requires explicit AI policy.
analytics-strategyDesign measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement. Triggers on analytics strategy, measurement plan, event taxonomy, tracking plan, KPI framework, dashboard design, north star metric, attribution model, conversion tracking, GA4 setup, Mixpanel setup, analytics audit. Also triggers when the user has data but no clear way to use it, or wants to make decisions but doesn't know what to track.
art-directionDirect visual and creative work for campaigns, photography, illustration, video, and branded experiences. Use this skill whenever the user wants to brief a photographer, direct illustrators, plan a creative campaign, develop visual concepts, write a creative direction document, or evaluate creative work for fit. Triggers on art direction, photo brief, photography brief, illustration brief, campaign concept, creative concept, visual direction, mood board, look and feel, visual treatment, video direction. Also triggers when the user has approved brand identity but needs to extend it into specific creative deliverables.
backup-and-disaster-recoveryPlan and run backups, set recovery objectives, and run disaster recovery drills. Use this skill when defining RPO/RTO targets, designing backup architecture, deciding what to back up and how often, planning for full-region or platform outages, or running a restoration drill. Triggers on backup, restore, RPO, RTO, disaster recovery, DR, business continuity, what if the database is gone, what if our hosting goes down, recovery drill, ransomware planning. Also triggers when an incident reveals a gap in restoration capability.
beta-program-managementRunning closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional feedback loops, clear graduation criteria). Triggers on beta program, alpha test, beta cohort, beta participant, beta feedback, beta to GA decision, design partner, early access program, closed beta, open beta, RC release. Also triggers when a feature is approaching launch and the team needs structured pre-GA validation, when prior betas produced noise rather than signal, or when the team has soft-launched before but wants more structured feedback this time.
brand-archetype-systemApply pre-composed aesthetic archetype defaults to jumpstart brand design work covering color, typography, layout, voice, and imagery direction. Use this skill whenever the user wants a starting point for brand visual and verbal direction, references a brand they want to design near (for example 'something like Stripe' or 'editorial like Linear'), needs to converge faster from many directions to one, or wants known-good defaults for a specific industry vertical. Triggers on archetype, design archetype, brand archetype, near to (brand), in the style of, similar aesthetic, design starting point, brand template, vertical-typical, industry-typical. Also triggers when the user has a brief and wants to map it to a known aesthetic family rather than design from first principles.
brand-discoveryRun upstream brand discovery covering audience research, competitive landscape, category dynamics, problem space, and positioning territory exploration. Use this skill at the very start of a brand or website project when the user needs to understand who they're for, who they compete with, what the audience actually needs, and where the brand could plausibly stand. Triggers on brand discovery, audience research, market research, competitive scan, category research, customer research, who is this for, who are we, positioning research, intake, kickoff. Also triggers when a creative brief is requested but the upstream inputs (audience, competitors, problem space) are not yet clear.