conversion-copywriting
Write copy that gets a "yes" using Joanna Wiebe's research-first, Voice of Customer methodology Use when: **Writing landing pages, emails, or sales pages** that need measurable conversion results; **Starting a new copy project** and need a systematic process to follow; **Struggling with what to write** and staring at a blank page; **Wanting to prove ROI** to clients with data-backed decisions; **Improving existing copy** through validation and testing
What this skill does
# Conversion Copywriting - Data-Driven Copy That Converts > Write copy that gets a "yes" using Joanna Wiebe's research-first, Voice of Customer methodology ## When to Use This Skill - **Writing landing pages, emails, or sales pages** that need measurable conversion results - **Starting a new copy project** and need a systematic process to follow - **Struggling with what to write** and staring at a blank page - **Wanting to prove ROI** to clients with data-backed decisions - **Improving existing copy** through validation and testing - **Training yourself or your team** on professional copywriting methodology ## Methodology Foundation | Aspect | Details | |--------|---------| | **Source** | Copyhackers, Copy School | | **Expert** | Joanna Wiebe - Creator of the term "conversion copywriting," founder of Copyhackers | | **Core Principle** | "Conversion copywriting is data-driven copy that gets prospects to say yes. It's a science-based process that determines what to write and how to write it." | ## What Claude Does vs What You Decide | Claude Does | You Decide | |-------------|------------| | Structures production workflow | Final creative direction | | Suggests technical approaches | Equipment and tool choices | | Creates templates and checklists | Quality standards | | Identifies best practices | Brand/voice decisions | | Generates script outlines | Final script approval | ## What This Skill Does This skill transforms copywriting from a guessing game into a systematic, data-driven process. Instead of staring at a blank page and hoping inspiration strikes, you'll: 1. **Research first** - Find your messages in customer language, not your imagination 2. **Listen more than write** - Let Voice of Customer (VOC) data do the heavy lifting 3. **Validate before launching** - Test copy before committing fully 4. **Measure everything** - Know what's working and why The result: Copy that converts because it says what customers actually want to hear, in the words they already use. ## How to Use ### Prompt Examples ``` Guide me through the conversion copywriting process for my [landing page/email/sales page]. Start with research questions I should answer before writing. ``` ``` Help me extract Voice of Customer data from these customer reviews for my [product]. Identify the strongest messages and organize them into a hierarchy. ``` ``` I have this VOC data: [paste data]. Turn it into copy for a [page type] using the Copyhackers methodology. ``` ``` Create a wireframe outline for my [landing page] that organizes these messages: [list messages]. Include awareness stage transitions and CTA placement. ``` ``` Run the 7 Sweeps editing process on this copy: [paste copy]. Start with the Clarity Sweep and work through all seven. ``` ## Instructions ### The 3-Part Process Overview ``` ┌─────────────────────────────────────────────────────────────┐ │ 1. RESEARCH & DISCOVERY │ 2. WRITE, WIREFRAME, EDIT │ 3. VALIDATE & TEST │ │ (Biggest phase) │ (Synthesis phase) │ (Proof phase) │ └─────────────────────────────────────────────────────────────┘ ``` No phase is optional. Even if a client says "just write," you still need research. --- ### Part 1: Research & Discovery > "If research is not the biggest part of the work, 99% of the time it means you're doing it wrong." **Goal**: Find your messages in customer language—don't invent them. #### Research Checklist **Internal Sources:** - [ ] Existing website copy audit - [ ] Product pages and feature descriptions - [ ] Sales call transcripts/recordings - [ ] Customer support tickets - [ ] Chat transcripts - [ ] Email sequences currently in use - [ ] Brochures and sales materials **Customer Sources:** - [ ] Customer surveys (existing or new) - [ ] Thank-you page polls - [ ] Customer interviews (transcribed) - [ ] Review mining (Amazon, G2, Capterra, Trustpilot) - [ ] Social media comments and discussions - [ ] Forum posts and Reddit threads - [ ] Testimonials and case studies **Competitive Sources:** - [ ] Competitor website audits - [ ] Competitor reviews (especially negative ones) - [ ] Industry forums and discussions **Analytics Sources:** - [ ] Click tracking data - [ ] Heatmaps and scroll maps - [ ] Conversion funnel analysis - [ ] Exit survey data #### How to Mine VOC Data **What to look for:** 1. **Pain language** - How do they describe their problem? 2. **Desire language** - What outcome do they want? 3. **Objection language** - What's stopping them? 4. **Trigger language** - What made them start looking? 5. **Value language** - What benefits matter most? 6. **Emotional language** - How do they feel about all of the above? **How to organize:** - Tag each insight by type (pain, desire, objection, etc.) - Note the source and frequency - Identify patterns and repeating themes - Rank by strength/emotion --- ### Part 2: Writing, Wireframing & Editing #### The Writing Setup **Joanna's Split-Screen Method:** 1. Open research/VOC data on LEFT side of screen 2. Open writing document on RIGHT side 3. Search VOC data for relevant keywords 4. Copy-paste actual customer language 5. Refine into copy (don't reinvent) > "You don't sit there and just start writing. Split your screen in two and take what people are saying and put it on the page." #### The Writing Process **Step 1: Determine Awareness Stage** Where is your reader starting? | Stage | They Know | Example Headline Approach | |-------|-----------|---------------------------| | Unaware | Nothing | Lead with the problem/pain | | Problem-Aware | They have a problem | Agitate the problem | | Solution-Aware | Solutions exist | Differentiate your solution | | Product-Aware | Your product exists | Prove you're the best choice | | Most Aware | Ready to buy | Make the offer irresistible | **Step 2: Map Your Messaging Hierarchy** What messages need to appear, and in what order? 1. **Primary Message** - The one thing they must understand 2. **Supporting Messages** - Evidence that backs up the primary 3. **Objection Handlers** - Address what's holding them back 4. **Call to Action** - The specific next step **Step 3: Select Your Framework** | Framework | Best For | |-----------|----------| | PAS (Problem-Agitate-Solve) | Short copy, high problem-awareness | | AIDA (Attention-Interest-Desire-Action) | Longer sales pages | | PPPP (Picture-Promise-Prove-Push) | Visual products | | PASOP (Problem-Agitate-Solution-Outcome-Proof) | Complex solutions | **Step 4: Draft Using VOC** Take raw VOC and transform: **Raw VOC:** > "I was so frustrated with spreadsheets. Every month I'd spend 8 hours just reconciling data and I'd still find errors." **Transformed into Copy:** > "Tired of losing 8+ hours every month to spreadsheet reconciliation—only to find errors anyway?" #### The 7 Sweeps Editing Process After your first draft, run these sweeps in order: | Sweep | Focus | Key Question | |-------|-------|--------------| | **1. Clarity** | Is it clear? | Would a 12-year-old understand? | | **2. Voice** | Does it sound right? | Is this how the brand/customer talks? | | **3. Proof** | Is it believable? | Where's the evidence? | | **4. Specificity** | Is it specific? | Can I add numbers, names, details? | | **5. Stickiness** | Is it memorable? | Will they remember this tomorrow? | | **6. Emotion** | Does it make them feel? | Where's the emotional hook? | | **7. Zero** | What can I cut? | Does every word earn its place? | **Clarity is ALWAYS first.** Above everything else, copy must be clear. #### Wireframing Create a visual layout showing: - Where each message block goes - Image/video placeholders with notes - CTA placement and copy - Mobile considerations Tools: Figma, Balsamiq, Photoshop, or even Google Docs with boxes --- ### Part 3: Validation & Experimentation > "We test to validate and learn." **Goal**: Ensure you're putting the best version out before committing. #### Validation Methods | Method | Best For
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".