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
- Confirm the offer. What exactly is being offered? At what price (if any)? What does the visitor get?
- Confirm the audience and objection. Specific segment. The specific worry they bring.
- Mine the language. Customer testimonials, support tickets, sales calls. Use real customer phrases.
- Draft the hero. Headline, subheadline, CTA. Test 5 to 10 variations.
- Build the structure. All 7 sections in order. Sections can combine for shorter pages.
- Draft sections. Section by section. Don't polish until the structure is sound.
- Edit for friction. Remove every word that doesn't earn its place. Landing pages do not have words to spare.
- Test the CTA. Read the page aloud. By the end, is the visitor's next action obvious?
- Hand off with a post-import checklist. The deliverable is a markdown document, not a built page, so step 9 is not something you perform: it is a list you attach for whoever builds the page. Spell-check the copy yourself, then hand over the rest. Every destination URL resolves. Mobile preview of the built page. SEO basics if SEO is a goal. If the page is already built and you are revising it in place, run the checklist yourself instead of handing it over.
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:
# [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, or state the gap per the data-availability rule]
- 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]
If required data is unavailable
This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.
Reference files
references/hero-formulas.md - Patterns and formulas for hero headlines.
references/objection-library.md - Common objections by category, with handling strategies.
1---2name: "landing-page-copy"3description: "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. Use `cro-optimization` instead when the page already exists and the ask is to lift its conversion rate through testing rather than to write the copy."4metadata:5 source: https://skillmd.com/skills/slipcast-dev/landing-page-copy6---78# Landing Page Copy910Write copy for pages with a single conversion goal: signup, purchase, demo request, download, lead capture. Stack-agnostic.1112This skill is narrower than `content-and-copy`. Landing pages exist to drive a specific action, not to inform broadly.1314---1516## When to use1718- Writing a hero section for a homepage or product page19- Writing a sales page or long-form sales letter20- Drafting opt-in or lead-capture page copy21- Campaign-specific landing pages22- Pricing page copy23- Demo or signup CTAs2425## When NOT to use2627- Long-form blog content (use `content-and-copy`)28- Email sequences (use `email-sequences`)29- Brand voice definition (use `brand-voice`)30- Page design and layout decisions (use `design-standards`)3132---3334## Required inputs3536- The product, service, or offer37- The target audience and the specific objection they bring38- The conversion goal (one specific action)39- Brand voice40- Existing customer language (testimonials, support tickets, sales calls)41- Any constraints (length, format, regulatory)4243If audience is unclear or objections are unknown, run `brand-discovery` or pull from sales call recordings before writing.4445---4647## The framework: 7 sections4849A landing page does seven things in sequence. The structure can flex (combine, reorder, expand), but the elements stay constant.5051### 1. Hero5253The first 3 to 5 seconds. Decides whether the visitor stays.5455**Three components:**5657- **Headline.** The promise. Specific, outcome-focused, free of cliche.58- **Subheadline.** The mechanism. How you deliver the promise.59- **Primary CTA.** The action. One button, descriptive label.6061**Strong hero patterns:**6263- **Outcome + audience + mechanism.** "Ship features 3x faster, for engineering teams who hate meetings, with our async-first project tool."64- **Pain reversal.** "Stop losing customers to slow page loads."65- **Surprising claim.** "The note-taking app that gets used. We have data."66- **Direct address.** "You have 47 unread Slack messages. Here's what to do about it."6768**Weak hero patterns:**6970- Generic adjective stacking ("Powerful, intuitive, scalable")71- "Welcome to our platform"72- Brand-name-only headlines ("Acme: The Future of X")73- Vague benefits ("Streamline your workflow")7475### 2. Social proof (early)7677Within the first scroll, prove someone else trusts you.7879**Forms:**80- Customer logos (recognizable beats unknown)81- Quantitative trust signal ("Over 10,000 teams")82- One strong testimonial with name and role83- Press mentions (logos of where you've been featured)8485**Placement:** Right below the hero, before the visitor invests in reading more.8687### 3. Problem / promise8889Establish that you understand the visitor's situation.9091**Pattern:**92- 1 to 3 paragraphs naming the specific problem93- Use the visitor's language (mined from research, not your marketing language)94- Stop before you sell. Resonate first.9596**Test:** Read the problem section aloud. Does the target audience nod? If they don't, you don't understand them yet.9798### 4. Solution / mechanism99100How you solve the problem. The "what we actually do" section.101102**Effective structure:**103- One headline summarizing the solution104- 3 to 5 specific features or capabilities, each with a 1-2 sentence explanation105- Each feature framed as the benefit it produces, not the technical detail106- Visual support (screenshots, illustrations, video clips)107108**Failure mode:** Listing features without translating to outcomes. "Real-time collaboration" is a feature. "Edit together without copying-pasting from email" is the outcome.109110### 5. Proof and detail111112The expanded social proof and case studies section.113114**Components:**115- 1 to 3 detailed case studies (specific customer, specific outcome, specific numbers)116- Multiple testimonials with attribution117- Specific data points (usage stats, success metrics, growth)118- Awards, certifications, or third-party validation119120The deeper proof section is where committed visitors convert. Skim-readers won't make it here, but the ones who do are ready to buy.121122### 6. Objection handling123124Anticipate the reasons people say no. Address them directly.125126**Common objection types:**127- **Price.** "Is this worth it?"128- **Time.** "Will this take forever to set up?"129- **Trust.** "Will this actually work for my situation?"130- **Risk.** "What if I commit and it's wrong?"131- **Comparison.** "How is this different from [competitor]?"132- **Implementation.** "Can my team handle the change?"133134**Handling formats:**135- **FAQ section.** Structured, scannable.136- **Comparison table.** Vs. competitors or vs. alternatives.137- **Risk reversal.** Money-back guarantee, free trial, no-contract terms.138- **Proof of effort needed.** "Setup takes 5 minutes, not 5 weeks."139140### 7. Final CTA141142The closer. Re-state the offer. Re-state the action.143144**Strong final CTAs:**145- Repeat the primary CTA from the hero (consistency)146- Frame in terms of the visitor's situation ("Get your team set up in 5 minutes")147- Remove friction ("No credit card required")148- One action only (avoid offering 5 alternatives that paralyze decision)149150**Avoid:**151- Multiple CTAs competing for attention at the bottom152- New offers introduced only at the bottom (visitor is now confused)153- Long forms that ask for more information than needed for the action154155---156157## The CTA itself158159Buttons matter. Treat the button copy as a whole-page-worth of attention.160161**Strong CTA patterns:**162163- **Action + outcome.** "Start your free trial," "Get my pricing," "Send me the guide"164- **First-person.** "Show me how" outperforms "Show you how"165- **Specific.** "Book a 15-minute demo" beats "Contact us"166- **Low-friction.** "Free trial, no credit card" reduces commitment cost167168**Weak CTAs:**169- "Submit" (functional but lifeless)170- "Click here" (no value statement)171- "Learn more" (vague; about what?)172- "Get started" (started doing what?)173174---175176## Workflow1771781. **Confirm the offer.** What exactly is being offered? At what price (if any)? What does the visitor get?1792. **Confirm the audience and objection.** Specific segment. The specific worry they bring.1803. **Mine the language.** Customer testimonials, support tickets, sales calls. Use real customer phrases.1814. **Draft the hero.** Headline, subheadline, CTA. Test 5 to 10 variations.1825. **Build the structure.** All 7 sections in order. Sections can combine for shorter pages.1836. **Draft sections.** Section by section. Don't polish until the structure is sound.1847. **Edit for friction.** Remove every word that doesn't earn its place. Landing pages do not have words to spare.1858. **Test the CTA.** Read the page aloud. By the end, is the visitor's next action obvious?1869. **Hand off with a post-import checklist.** The deliverable is a markdown document, not a built page, so step 9 is not something you perform: it is a list you attach for whoever builds the page. Spell-check the copy yourself, then hand over the rest. Every destination URL resolves. Mobile preview of the built page. SEO basics if SEO is a goal. If the page is already built and you are revising it in place, run the checklist yourself instead of handing it over.187188---189190## Failure patterns191192- **Hero that explains instead of sells.** "We're an X for Y" is description. "Get X without Y" is sell.193- **Feature lists with no outcomes.** Features without benefits read as a spec sheet.194- **Generic testimonials.** "Great product!" is worth less than nothing. "We cut onboarding time from 2 weeks to 4 days" is gold.195- **Multiple competing CTAs.** Pick one primary action. Everything else is noise.196- **Walls of text.** Visitors scan. Use short paragraphs, bullet lists, and visual breakpoints.197- **No social proof.** Trust is the first hurdle. Without proof, the rest of the page does not earn the chance to be read.198- **Mismatched headline and CTA.** Hero promises X, CTA asks for Y. Visitor confused.199- **Writing for everyone.** "Our solution works for any business" appeals to no one. Specificity converts.200- **Ignoring mobile.** Most visitors are on mobile. Test the page at 375px first.201202---203204## Output format205206Default 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.207208Structure:209210```markdown211# [Page Title]212213## SECTION: Hero214- Headline: [text]215- Subheadline: [text]216- Primary CTA: [button text]217- Supporting cue: [optional, e.g., "No credit card required"]218- Hero visual notes: [if any]219220## SECTION: Social proof (early)221- Logo bar: [list customer/press logos]222- Trust statistic: [if any]223224## SECTION: Problem / promise225[2 to 3 paragraphs]226227## SECTION: Solution228- Headline: [text]229- Feature 1: [headline + description]230- Feature 2: [headline + description]231- Feature 3: [headline + description]232233## SECTION: Proof234- Case study 1: [customer, outcome, numbers, or state the gap per the data-availability rule]235- Testimonials: [list]236- Data points: [list]237238## SECTION: Objection handling239- FAQ: [questions and answers]240- OR Comparison table: [vs alternatives]241- OR Risk reversal: [guarantee, terms]242243## SECTION: Final CTA244- Headline: [text]245- Final CTA button: [text]246- Supporting cue: [optional]247248## Variants for testing249- [Alternate headlines]250- [Alternate CTAs]251- [Alternate proof framings]252```253254---255256## If required data is unavailable257258This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.259260---261262## Reference files263264- [`references/hero-formulas.md`](references/hero-formulas.md) - Patterns and formulas for hero headlines.265- [`references/objection-library.md`](references/objection-library.md) - Common objections by category, with handling strategies.266