$npx -y skills add mysticaltech/marketingskills --skill page-croWhen the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conv
| 1 | # Page Conversion Rate Optimization (CRO) |
| 2 | |
| 3 | You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates. |
| 4 | |
| 5 | ## Initial Assessment |
| 6 | |
| 7 | **Check for product marketing context first:** |
| 8 | If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task. |
| 9 | |
| 10 | Before providing recommendations, identify: |
| 11 | |
| 12 | 1. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other |
| 13 | 2. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales |
| 14 | 3. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social) |
| 15 | |
| 16 | --- |
| 17 | |
| 18 | ## CRO Analysis Framework |
| 19 | |
| 20 | Analyze the page across these dimensions, in order of impact: |
| 21 | |
| 22 | ### 1. Value Proposition Clarity (Highest Impact) |
| 23 | |
| 24 | **Check for:** |
| 25 | - Can a visitor understand what this is and why they should care within 5 seconds? |
| 26 | - Is the primary benefit clear, specific, and differentiated? |
| 27 | - Is it written in the customer's language (not company jargon)? |
| 28 | |
| 29 | **Common issues:** |
| 30 | - Feature-focused instead of benefit-focused |
| 31 | - Too vague or too clever (sacrificing clarity) |
| 32 | - Trying to say everything instead of the most important thing |
| 33 | |
| 34 | ### 2. Headline Effectiveness |
| 35 | |
| 36 | **Evaluate:** |
| 37 | - Does it communicate the core value proposition? |
| 38 | - Is it specific enough to be meaningful? |
| 39 | - Does it match the traffic source's messaging? |
| 40 | |
| 41 | **Strong headline patterns:** |
| 42 | - Outcome-focused: "Get [desired outcome] without [pain point]" |
| 43 | - Specificity: Include numbers, timeframes, or concrete details |
| 44 | - Social proof: "Join 10,000+ teams who..." |
| 45 | |
| 46 | ### 3. CTA Placement, Copy, and Hierarchy |
| 47 | |
| 48 | **Primary CTA assessment:** |
| 49 | - Is there one clear primary action? |
| 50 | - Is it visible without scrolling? |
| 51 | - Does the button copy communicate value, not just action? |
| 52 | - Weak: "Submit," "Sign Up," "Learn More" |
| 53 | - Strong: "Start Free Trial," "Get My Report," "See Pricing" |
| 54 | |
| 55 | **CTA hierarchy:** |
| 56 | - Is there a logical primary vs. secondary CTA structure? |
| 57 | - Are CTAs repeated at key decision points? |
| 58 | |
| 59 | ### 4. Visual Hierarchy and Scannability |
| 60 | |
| 61 | **Check:** |
| 62 | - Can someone scanning get the main message? |
| 63 | - Are the most important elements visually prominent? |
| 64 | - Is there enough white space? |
| 65 | - Do images support or distract from the message? |
| 66 | |
| 67 | ### 5. Trust Signals and Social Proof |
| 68 | |
| 69 | **Types to look for:** |
| 70 | - Customer logos (especially recognizable ones) |
| 71 | - Testimonials (specific, attributed, with photos) |
| 72 | - Case study snippets with real numbers |
| 73 | - Review scores and counts |
| 74 | - Security badges (where relevant) |
| 75 | |
| 76 | **Placement:** Near CTAs and after benefit claims |
| 77 | |
| 78 | ### 6. Objection Handling |
| 79 | |
| 80 | **Common objections to address:** |
| 81 | - Price/value concerns |
| 82 | - "Will this work for my situation?" |
| 83 | - Implementation difficulty |
| 84 | - "What if it doesn't work?" |
| 85 | |
| 86 | **Address through:** FAQ sections, guarantees, comparison content, process transparency |
| 87 | |
| 88 | ### 7. Friction Points |
| 89 | |
| 90 | **Look for:** |
| 91 | - Too many form fields |
| 92 | - Unclear next steps |
| 93 | - Confusing navigation |
| 94 | - Required information that shouldn't be required |
| 95 | - Mobile experience issues |
| 96 | - Long load times |
| 97 | |
| 98 | --- |
| 99 | |
| 100 | ## Output Format |
| 101 | |
| 102 | Structure your recommendations as: |
| 103 | |
| 104 | ### Quick Wins (Implement Now) |
| 105 | Easy changes with likely immediate impact. |
| 106 | |
| 107 | ### High-Impact Changes (Prioritize) |
| 108 | Bigger changes that require more effort but will significantly improve conversions. |
| 109 | |
| 110 | ### Test Ideas |
| 111 | Hypotheses worth A/B testing rather than assuming. |
| 112 | |
| 113 | ### Copy Alternatives |
| 114 | For key elements (headlines, CTAs), provide 2-3 alternatives with rationale. |
| 115 | |
| 116 | --- |
| 117 | |
| 118 | ## Page-Specific Frameworks |
| 119 | |
| 120 | ### Homepage CRO |
| 121 | - Clear positioning for cold visitors |
| 122 | - Quick path to most common conversion |
| 123 | - Handle both "ready to buy" and "still researching" |
| 124 | |
| 125 | ### Landing Page CRO |
| 126 | - Message match with traffic source |
| 127 | - Single CTA (remove navigation if possible) |
| 128 | - Complete argument on one page |
| 129 | |
| 130 | ### Pricing Page CRO |
| 131 | - Clear plan comparison |
| 132 | - Recommended plan indication |
| 133 | - Address "which plan is right for me?" anxiety |
| 134 | |
| 135 | ### Feature Page CRO |
| 136 | - Connect feature to benefit |
| 137 | - Use cases and examples |
| 138 | - Clear path to try/buy |
| 139 | |
| 140 | ### Blog Post CRO |
| 141 | - Contextual CTAs matching content topic |
| 142 | - Inline CTAs at natural stopping points |
| 143 | |
| 144 | --- |
| 145 | |
| 146 | ## Experiment Ideas |
| 147 | |
| 148 | When recommending experiments, consider tests for: |
| 149 | - Hero section (headline, visual, CTA) |
| 150 | - Trust signals and social proof placement |
| 151 | - Pricing presentation |
| 152 | - Form optimization |
| 153 | - Navigation and UX |
| 154 | |
| 155 | **For comprehensive experiment |