Conversion optimization skill
When the user wants to improve conversion rates, run A/B tests, optimize funnels, or reduce friction.
by kostja94·MIT license·★ 1,006 Stars on the repo·GitHub ↗
Use now
npx degit kostja94/marketing-skills/skills/strategies/launch/conversion#main ~/.claude/skills/conversion-optimization-kostja94Checked ·commit main
Files of Conversion optimization
SKILL.md
Show the full text99 lines
Strategies: Conversion Optimization
Guides conversion rate optimization (CRO): increasing the percentage of visitors who complete desired actions. Higher conversion rates mean increased revenue, reduced CAC, and better ROI. Use this skill when optimizing funnels, running experiments, or reducing friction on high-traffic pages.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
Identify:
- Funnel stage: Awareness, consideration, decision, post-purchase
- Conversion goal: Signup, purchase, download, demo request
- Traffic: Volume; mobile vs desktop split
- Current conversion rate: Baseline for improvement
CRO Process
| Step | Action |
|---|---|
| 1. Research | Map funnel; identify high-traffic, low-conversion pages |
| 2. Hypothesize | Form testable hypothesis (if X, then Y because Z) |
| 3. Prioritize | Score by Potential, Importance, Ease (PIE) |
| 4. Test | A/B or multivariate; adequate sample size |
| 5. Analyze | Statistical significance; implement winner |
PIE Prioritization Framework
Score each test idea 1–10:
| Factor | Question |
|---|---|
| Potential | How much improvement is possible? |
| Importance | How much traffic does this page get? |
| Ease | How easy to implement? |
Rank backlog by total score; run highest-impact tests first.
A/B Testing Best Practices
| Practice | Guideline |
|---|---|
| Sample size | Calculate minimum before launch; 95% significance without adequate sample = false positives |
| Duration | Run full week cycles; account for day-of-week effects |
| One variable | Test one element per experiment (or use MVT for multiple) |
| Mobile separate | Mobile converts ~50% of desktop; test mobile independently—thumb reach, form complexity differ |
| Low traffic | Use Bayesian testing for faster, actionable results |
Key Testing Areas
| Page Type | Test Ideas |
|---|---|
| Homepage | Search bar prominence; personalized content; hero CTA; social proof placement |
| Landing page | Headline; form length; CTA copy; above-fold layout |
| Product/Category | Quick view; descriptions; add-to-cart placement |
| Checkout | Form fields; progress indicator; trust badges; guest checkout |
| Pricing | Plan order; anchoring; CTA per tier |
Personalization: Personalized experiences generate ~41% more impact than generic ones.
Commercialization Infrastructure
| Module | Purpose |
|---|---|
| Data & BI | Data warehouse; user behavior events; agile surveys |
| A/B testing | Experiment platform; statistical significance; backend-controlled variants |
| User education | Help docs (multi-language); update notifications; EDM |
| Attribution | Ad pixels; attribution model; impression-to-click-to-sale tracking |
Avoid: Intrusive interstitials; popups that block content. Prefer non-intrusive ad formats.
Foundational Requirements
- Analytics: Map funnels; identify drop-off points (analytics-tracking, traffic-analysis)
- Qualitative: Heatmaps, session recordings, user tests—understand why drop-off occurs
- Technical: Dedicated resources for 2–4 tests/month; maintain momentum
Output Format
- Funnel map (stages, conversion rates, drop-off)
- Hypothesis (if X, then Y because Z)
- Test plan (variant, metric, sample size, duration)
- Implementation checklist
Related Skills
- landing-page-generator: Landing page structure and copy
- cta-generator: CTA design and placement
- analytics-tracking: GA4, events, conversion tracking
- traffic-analysis: Attribution, funnel analysis
- copywriting: Headline, CTA copy for tests
| 1 | |
| 2 | name conversion-optimization |
| 3 | description When the user wants to improve conversion rates, run A/B tests, optimize funnels, or reduce friction. Also use when the user mentions "CRO," "conversion rate optimization," "A/B test," "split test," "funnel optimization," "checkout optimization," "form optimization," or "conversion funnel." For pricing psychology, use pricing-strategy. |
| 4 | metadata |
| 5 | version 1.1.1 |
| 6 | |
| 7 | |
| 8 | # Strategies: Conversion Optimization |
| 9 | |
| 10 | Guides conversion rate optimization (CRO): increasing the percentage of visitors who complete desired actions. Higher conversion rates mean increased revenue, reduced CAC, and better ROI. Use this skill when optimizing funnels, running experiments, or reducing friction on high-traffic pages. |
| 11 | |
| 12 | **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. |
| 13 | |
| 14 | ## Initial Assessment |
| 15 | |
| 16 | **Project context:** Read root `contextus.md` when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system. |
| 17 | |
| 18 | Identify: |
| 19 | **Funnel stage**: Awareness, consideration, decision, post-purchase |
| 20 | **Conversion goal**: Signup, purchase, download, demo request |
| 21 | **Traffic**: Volume; mobile vs desktop split |
| 22 | **Current conversion rate**: Baseline for improvement |
| 23 | |
| 24 | ## CRO Process |
| 25 | |
| 26 | | Step | Action | |
| 27 | |------|--------| |
| 28 | | **1. Research** | Map funnel; identify high-traffic, low-conversion pages | |
| 29 | | **2. Hypothesize** | Form testable hypothesis (if X, then Y because Z) | |
| 30 | | **3. Prioritize** | Score by Potential, Importance, Ease (PIE) | |
| 31 | | **4. Test** | A/B or multivariate; adequate sample size | |
| 32 | | **5. Analyze** | Statistical significance; implement winner | |
| 33 | |
| 34 | ## PIE Prioritization Framework |
| 35 | |
| 36 | Score each test idea 1–10: |
| 37 | |
| 38 | | Factor | Question | |
| 39 | |--------|----------| |
| 40 | | **Potential** | How much improvement is possible? | |
| 41 | | **Importance** | How much traffic does this page get? | |
| 42 | | **Ease** | How easy to implement? | |
| 43 | |
| 44 | Rank backlog by total score; run highest-impact tests first. |
| 45 | |
| 46 | ## A/B Testing Best Practices |
| 47 | |
| 48 | | Practice | Guideline | |
| 49 | |----------|-----------| |
| 50 | | **Sample size** | Calculate minimum before launch; 95% significance without adequate sample = false positives | |
| 51 | | **Duration** | Run full week cycles; account for day-of-week effects | |
| 52 | | **One variable** | Test one element per experiment (or use MVT for multiple) | |
| 53 | | **Mobile separate** | Mobile converts ~50% of desktop; test mobile independently—thumb reach, form complexity differ | |
| 54 | | **Low traffic** | Use Bayesian testing for faster, actionable results | |
| 55 | |
| 56 | ## Key Testing Areas |
| 57 | |
| 58 | | Page Type | Test Ideas | |
| 59 | |-----------|------------| |
| 60 | | **Homepage** | Search bar prominence; personalized content; hero CTA; social proof placement | |
| 61 | | **Landing page** | Headline; form length; CTA copy; above-fold layout | |
| 62 | | **Product/Category** | Quick view; descriptions; add-to-cart placement | |
| 63 | | **Checkout** | Form fields; progress indicator; trust badges; guest checkout | |
| 64 | | **Pricing** | Plan order; anchoring; CTA per tier | |
| 65 | |
| 66 | **Personalization**: Personalized experiences generate ~41% more impact than generic ones. |
| 67 | |
| 68 | ## Commercialization Infrastructure |
| 69 | |
| 70 | | Module | Purpose | |
| 71 | |--------|---------| |
| 72 | | **Data & BI** | Data warehouse; user behavior events; agile surveys | |
| 73 | | **A/B testing** | Experiment platform; statistical significance; backend-controlled variants | |
| 74 | | **User education** | Help docs (multi-language); update notifications; EDM | |
| 75 | | **Attribution** | Ad pixels; attribution model; impression-to-click-to-sale tracking | |
| 76 | |
| 77 | **Avoid**: Intrusive interstitials; popups that block content. Prefer non-intrusive ad formats. |
| 78 | |
| 79 | ## Foundational Requirements |
| 80 | |
| 81 | **Analytics**: Map funnels; identify drop-off points (analytics-tracking, traffic-analysis) |
| 82 | **Qualitative**: Heatmaps, session recordings, user tests—understand *why* drop-off occurs |
| 83 | **Technical**: Dedicated resources for 2–4 tests/month; maintain momentum |
| 84 | |
| 85 | ## Output Format |
| 86 | |
| 87 | **Funnel map** (stages, conversion rates, drop-off) |
| 88 | **Hypothesis** (if X, then Y because Z) |
| 89 | **Test plan** (variant, metric, sample size, duration) |
| 90 | **Implementation** checklist |
| 91 | |
| 92 | ## Related Skills |
| 93 | |
| 94 | **landing-page-generator**: Landing page structure and copy |
| 95 | **cta-generator**: CTA design and placement |
| 96 | **analytics-tracking**: GA4, events, conversion tracking |
| 97 | **traffic-analysis**: Attribution, funnel analysis |
| 98 | **copywriting**: Headline, CTA copy for tests |
| 99 |
Discussion
Alternatives
A/B Test SetupWhen the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab test analysisAnalyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Ad Copy Generator + A/B TesterGenerate and A/B test Google Ads copy. Use when asked to write ad copy, headlines, descriptions, create ad variants, test ad messaging, improve CTR, or generate RSA (Responsive Search Ad) components. Trigger on "ad copy", "write ads", "headlines", "descriptions", "RSA", "responsive search ad", "ad text", "ad creative", "improve CTR", "ad A/B test", "ad variants", "write me an ad", "ad variation experiment", or when the user wants to improve click-through rate on existing ads.
A/B Test Planner SkillDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.Browse more free Claude skills or everything in Marketing.