# Copywriting

> Use this skill when writing conversion-focused web copy — headlines, subheadlines, CTAs, body copy, microcopy, email sequences, product descriptions, and landing page copy flow using proven formulas like PAS, AIDA, and 4U.

- Skill: `ziadnagar/copywriting` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add ziadnagar/copywriting`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ziadnagar/copywriting/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- License: Complete terms in LICENSE.txt
- Author: ZiadNagar (https://skillmd.com/u/ziadnagar)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ziadnagar/copywriting

---


# Conversion Copywriting

## When to Use

- Writing headlines, subheadlines, or taglines for landing pages and marketing sites.
- Crafting calls-to-action (CTAs) that drive clicks, signups, or purchases.
- Structuring body copy for product pages, feature sections, or about pages.
- Writing microcopy for buttons, tooltips, empty states, and error messages.
- Creating email subject lines and sequences for onboarding or campaigns.
- Translating technical features into customer-facing benefits.
- Writing social proof copy — testimonials, case study excerpts, trust badges.
- Producing A/B testing variants of existing copy.

## Core Principles

1. **Clarity over cleverness** — the reader should never re-read a sentence.
2. **One idea per section** — don't stack multiple value props into one paragraph.
3. **Benefits before features** — lead with what the user gains, then explain how.
4. **Active voice, imperative mood** — "Start your free trial" not "A free trial can be started."
5. **Specificity wins** — "Saves 4 hours/week" beats "Saves time."
6. **Write for scanners** — bold key phrases, use short paragraphs, add whitespace.

## Headline Formulas

### PAS — Problem, Agitation, Solution

State the problem, twist the knife, then present your solution.

```
Problem:   "Tired of losing leads to slow follow-up?"
Agitation: "Every hour you wait, competitors close the deal."
Solution:  "Respond in under 60 seconds — automatically."
```

**Headline output:** "Stop Losing Leads to Slow Follow-Up — Respond in Under 60 Seconds, Automatically"

### AIDA — Attention, Interest, Desire, Action

Grab attention, build interest with details, stoke desire, then prompt action.

```
Attention: "What if your deploys never failed?"
Interest:  "Zero-downtime releases with automatic rollback."
Desire:    "Ship with confidence every single day."
Action:    "Start deploying →"
```

### 4U — Useful, Urgent, Unique, Ultra-specific

Score your headline against all four dimensions:

| Dimension | Question | Example |
|-----------|----------|---------|
| Useful | Does it promise a clear benefit? | "Cut onboarding time in half" |
| Urgent | Is there a reason to act now? | "Before your next sprint" |
| Unique | Does it stand apart from competitors? | "The only platform that..." |
| Ultra-specific | Are there concrete details? | "3-minute setup, zero config files" |

### Additional Headline Patterns

- **How-to:** "How to [achieve desired outcome] without [common pain]"
- **Number list:** "[Number] ways to [achieve outcome] in [timeframe]"
- **Question:** "Are you still [doing old painful thing]?"
- **Social proof:** "[Number] teams already [achieving outcome]"
- **Contrast:** "Stop [bad thing]. Start [good thing]."
- **Command:** "[Action verb] your [noun] in [timeframe]"

## Subheadline Patterns

The subheadline supports the headline by adding specificity or addressing a secondary concern.

**Pattern 1 — Expand the benefit:**
```
Headline:    "Deploy Without Fear"
Subheadline: "Automatic rollbacks, real-time monitoring, and zero-downtime releases for teams that ship fast."
```

**Pattern 2 — Address the objection:**
```
Headline:    "Analytics That Actually Make Sense"
Subheadline: "No data science degree required. Get actionable insights in plain English."
```

**Pattern 3 — Specify the audience:**
```
Headline:    "Build Forms 10x Faster"
Subheadline: "Designed for product teams who are tired of fighting their form library."
```

**Pattern 4 — Add proof:**
```
Headline:    "The Fastest Way to Ship APIs"
Subheadline: "Trusted by 2,400+ backend teams. Average integration time: 11 minutes."
```

## Body Copy Structure

### The Inverted Pyramid

Lead with the most important information, then layer in supporting details.

```
[Key benefit / most compelling claim]
[Supporting evidence or specifics]
[How it works / mechanism]
[Secondary benefits]
[Call to action]
```

### Feature-to-Benefit Translation

Always convert features into benefits using this formula:

**[Feature] so you can [benefit], which means [outcome].**

| Feature | Benefit | Outcome |
|---------|---------|---------|
| Real-time sync | Always see the latest data | Make decisions faster |
| One-click deploy | Ship without waiting on DevOps | Launch features the same day |
| SOC 2 compliance | Meet enterprise security requirements | Close bigger deals |
| Offline mode | Work without internet | Never lose progress on the go |

### Copy Length Guidelines

| Section | Recommended Length | Notes |
|---------|--------------------|-------|
| Headline | 6–12 words | Shorter is almost always better |
| Subheadline | 15–25 words | One sentence, two at most |
| Feature card | 20–40 words | Title + 1–2 sentence description |
| CTA button | 2–5 words | Start with an action verb |
| Hero paragraph | 25–40 words | One clear idea |
| Testimonial | 20–50 words | Short, specific, attributed |

## CTA Writing

### Action Verb Starters

Use strong, specific verbs instead of generic ones:

| Weak | Strong |
|------|--------|
| Submit | Get My Report |
| Click Here | See How It Works |
| Learn More | Explore the Platform |
| Sign Up | Start Building Free |
| Buy | Secure My Spot |

### CTA Formulas

- **Benefit-driven:** "Get [benefit] →" — "Get Faster Deploys →"
- **Urgency:** "[Action] before [deadline]" — "Claim Your Spot Before Friday"
- **Risk-reversal:** "[Action] — [safety net]" — "Try Free for 14 Days — No Card Required"
- **Specificity:** "[Action] in [timeframe]" — "Set Up in 3 Minutes"
- **First-person:** "Start my [benefit]" — "Start My Free Trial"

### CTA Placement Rules

1. **Primary CTA** above the fold — always visible without scrolling.
2. **Repeat the CTA** after every major content section.
3. **Use a sticky CTA** on mobile (bottom bar or floating button).
4. **Limit to one primary action** per page — secondary CTAs get muted styling.
5. **Surround CTAs with proof** — a short testimonial or stat near the button.

## Tone and Voice Consistency

### Defining Voice Attributes

Pick 3–4 adjectives that define the brand voice and use them as a filter for all copy.

| Attribute | Do | Don't |
|-----------|-----|-------|
| Confident | "This is the fastest way to ship." | "We think this might help you ship faster." |
| Friendly | "Let's get you set up." | "The user must complete the onboarding flow." |
| Direct | "Pricing starts at $29/mo." | "Our flexible pricing options begin at..." |
| Witty | "Your inbox will thank you." | "Reduce email volume significantly." |

### Voice Consistency Checklist

- [ ] Does every sentence pass the "would we say this out loud?" test?
- [ ] Are we using the same terms for the same concepts throughout?
- [ ] Is the formality level consistent from headline to footer?
- [ ] Do error messages match the same tone as marketing copy?

## Social Proof Copy

### Testimonial Formula

**"[Specific result] + [before/after contrast] + [emotional payoff]."**

**Weak:** "Great product! Highly recommend."
**Strong:** "We cut our deploy time from 45 minutes to 3 minutes. The engineering team actually looks forward to release day now."

### Testimonial Structure

```html
<blockquote>
  <p>"We cut our deploy time from 45 minutes to 3. The team actually
  looks forward to release day now."</p>
  <footer>
    <strong>Sarah Chen</strong>
    <span>VP Engineering, Acme Corp</span>
  </footer>
</blockquote>
```

### Case Study Excerpt Pattern

```
[Company name] faced [specific problem]. After switching to [product],
they achieved [quantified result] in [timeframe].
```

### Social Proof Placement

- **Logo bar** — immediately below the hero section.
- **Testimonial cards** — after the features section.
- **Stat callouts** — embedded within body copy ("Join 10,000+ teams").
- **Case study links** — near the bottom, before the final CTA.

## Email Subject Lines

### High-Performing Patterns

| Pattern | Example | Why It Works |
|---------|---------|--------------|
| Curiosity gap | "The one metric most teams ignore" | Creates open loop |
| Personalization | "[Name], your setup is 80% done" | Feels direct |
| Urgency | "Offer expires in 6 hours" | Time pressure |
| Social proof | "Why 500 teams switched this week" | Bandwagon effect |
| Question | "Is your CI pipeline slowing you down?" | Mirrors internal dialog |
| How-to | "How to cut deploy time by 90%" | Promises value |
| Negative framing | "Stop making this onboarding mistake" | Loss aversion |

### Subject Line Rules

1. Keep under 50 characters for mobile visibility.
2. Front-load the most important word.
3. Avoid ALL CAPS and excessive punctuation.
4. Test emoji use — it lifts open rates in some segments, hurts in others.
5. Never mislead — the email body must deliver on the subject line promise.

## Microcopy

### Button Labels

- Use first-person when appropriate: "Start my trial" vs "Start your trial."
- Include the benefit: "Download the guide" vs "Download."
- Specify what happens next: "Continue to payment" vs "Next."

### Tooltip Copy

- Maximum 15 words.
- Explain *why*, not just *what*: "Connects to Slack so your team gets instant alerts" vs "Slack integration."

### Empty States

Turn empty states into onboarding moments:

```
Heading:  "No projects yet"
Body:     "Create your first project to start tracking deployments."
CTA:      "Create a Project →"
```

### Error Messages

Follow this structure: **[What happened] + [Why] + [What to do next].**

```
✗ "Something went wrong."
✓ "We couldn't save your changes because the file is too large. Try compressing it below 10 MB."
```

### Loading States

- Use progressive messaging for long waits:
  - 0–3s: spinner only.
  - 3–8s: "Crunching the numbers..."
  - 8s+: "Almost there — this usually takes about 15 seconds."

## SEO Copywriting Basics

### On-Page Copy Checklist

1. **Title tag** — primary keyword near the front, under 60 characters.
2. **Meta description** — includes keyword, compelling reason to click, under 155 characters.
3. **H1** — one per page, contains the primary keyword naturally.
4. **Subheadings (H2–H3)** — incorporate secondary and long-tail keywords.
5. **Body copy** — keyword appears naturally 2–4 times per 500 words.
6. **Image alt text** — descriptive, includes keyword when relevant.
7. **Internal links** — anchor text uses target keywords for linked pages.

### SEO Copy Rules

- Write for humans first, search engines second.
- Never keyword-stuff — if it sounds forced, rewrite.
- Use synonyms and related terms (semantic relevance > exact match).
- Answer the search intent directly in the first paragraph.

## A/B Testing Copy Variants

### What to Test

| Element | Variable | Example |
|---------|----------|---------|
| Headline | Benefit vs. feature | "Save 4 hours/week" vs "Automated reporting" |
| CTA | Action vs. benefit | "Sign up" vs "Get my dashboard" |
| Social proof | Stat vs. testimonial | "10,000+ users" vs "Rated 4.9/5" |
| Urgency | With vs. without | "Start free trial" vs "Start free — 3 days left" |
| Length | Short vs. detailed | One-liner vs. paragraph explanation |

### Testing Process

1. Change **one variable** at a time.
2. Run for at least **2 full business cycles** (typically 2 weeks minimum).
3. Need a minimum of **100 conversions per variant** for significance.
4. Document the winner and the margin — build an institutional copy playbook.

## Templates

### Hero Section Copy

```
Eyebrow:     [Category or social proof — e.g., "Trusted by 5,000+ teams"]
Headline:    [Primary benefit in 6–12 words]
Subheadline: [Expand the benefit + address the key objection in 15–25 words]
Primary CTA: [Action verb + benefit — e.g., "Start Building Free"]
Secondary:   [Lower-commitment option — e.g., "See how it works"]
```

### Feature Description (Card)

```
Icon/Visual: [Relevant icon or illustration]
Title:       [Feature name as a benefit — e.g., "Instant Rollbacks"]
Description: [1–2 sentences: what it does + why it matters to the user]

Example:
  Title:       "One-Click Rollbacks"
  Description: "Deployed a bug? Roll back to any previous version in
               seconds — no SSH, no scripts, no stress."
```

### Pricing Page Copy

```
Plan Name:    [Simple, clear — "Starter", "Pro", "Enterprise"]
Price:        [$XX/mo — annual price shown, monthly available]
Tagline:      [Who this plan is for — "For small teams getting started"]
Feature List: [5–8 bullet points, benefit-oriented]
CTA:          [Matches the plan — "Start Free" / "Upgrade to Pro" / "Contact Sales"]
Badge:        [Optional — "Most Popular" on the recommended tier]
```

### Email Sequence (Onboarding)

```
Email 1 — Welcome (Day 0):
  Subject: "Welcome to [Product] — here's your first step"
  Body:    Thank them, set expectations, link to one quick-win action.

Email 2 — Quick Win (Day 1):
  Subject: "Set up [key feature] in 2 minutes"
  Body:    Walk through one valuable action with a screenshot or GIF.

Email 3 — Social Proof (Day 3):
  Subject: "How [Company] cut their [metric] by [%]"
  Body:    Short case study, link to full story, soft CTA.

Email 4 — Overcome Objection (Day 5):
  Subject: "The #1 question new users ask"
  Body:    Address the most common hesitation, link to help docs.

Email 5 — Conversion (Day 7):
  Subject: "Your trial ends in 7 days — here's what you'll lose"
  Body:    Recap value delivered, show usage stats, hard CTA to upgrade.
```

### Product Description

```
Opening:     [What it is + who it's for in one sentence]
Key Benefit: [The single most compelling reason to care]
How it Works:[3-step summary — simple, visual, scannable]
Proof:       [Stat, testimonial, or comparison]
CTA:         [Clear next step]
```

### About Page Narrative

```
Section 1 — Origin:    "We built [Product] because [personal pain point]."
Section 2 — Mission:   "We believe [vision for the future]."
Section 3 — Traction:  "[Metrics, milestones, customer count]."
Section 4 — Team:      "We're [team size] people in [locations], obsessed with [craft]."
Section 5 — Values:    "[3–4 values with one-line explanations]."
Section 6 — CTA:       "Join us" or "See what we're building."
```

## Anti-Patterns

- **Jargon overload** — "Leverage our synergistic platform to optimize cross-functional workflows." Write in plain language.
- **Passive voice** — "Reports are generated automatically" → "Generate reports automatically."
- **Weasel words** — "Helps you potentially save time" → "Saves you 4 hours a week."
- **Feature-dumping** — listing every feature without explaining why anyone should care.
- **Buried CTAs** — if the user has to hunt for the button, the copy has failed.
- **Generic testimonials** — "Great product!" is worthless. Require specifics.
- **Inconsistent tone** — switching between formal and casual within the same page.
- **Ignoring the fold** — putting the most important copy where no one will scroll to see it.
- **Clever-but-unclear headlines** — wordplay that makes the writer smile but confuses the reader.
- **Missing proof** — making bold claims without data, quotes, or examples to back them up.