Conversion Rate Optimization (CRO)
When to Use
Use this skill when you need when the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't...
You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.
Initial Assessment
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before providing recommendations, identify:
- Page Type: Homepage, landing page, pricing, feature, blog, about, other
- Primary Conversion Goal: Sign up, request demo, purchase, subscribe, download, contact sales
- Traffic Context: Where are visitors coming from? (organic, paid, email, social)
CRO Analysis Framework
Analyze the page across these dimensions, in order of impact:
1. Value Proposition Clarity (Highest Impact)
Check for:
- Can a visitor understand what this is and why they should care within 5 seconds?
- Is the primary benefit clear, specific, and differentiated?
- Is it written in the customer's language (not company jargon)?
Common issues:
- Feature-focused instead of benefit-focused
- Too vague or too clever (sacrificing clarity)
- Trying to say everything instead of the most important thing
2. Headline Effectiveness
Evaluate:
- Does it communicate the core value proposition?
- Is it specific enough to be meaningful?
- Does it match the traffic source's messaging?
Strong headline patterns:
- Outcome-focused: "Get [desired outcome] without [pain point]"
- Specificity: Include numbers, timeframes, or concrete details
- Social proof: "Join 10,000+ teams who..."
3. CTA Placement, Copy, and Hierarchy
Primary CTA assessment:
- Is there one clear primary action?
- Is it visible without scrolling?
- Does the button copy communicate value, not just action?
- Weak: "Submit," "Sign Up," "Learn More"
- Strong: "Start Free Trial," "Get My Report," "See Pricing"
CTA hierarchy:
- Is there a logical primary vs. secondary CTA structure?
- Are CTAs repeated at key decision points?
4. Visual Hierarchy and Scannability
Check:
- Can someone scanning get the main message?
- Are the most important elements visually prominent?
- Is there enough white space?
- Do images support or distract from the message?
5. Trust Signals and Social Proof
Types to look for:
- Customer logos (especially recognizable ones)
- Testimonials (specific, attributed, with photos)
- Case study snippets with real numbers
- Review scores and counts
- Security badges (where relevant)
Placement: Near CTAs and after benefit claims
6. Objection Handling
Common objections to address:
- Price/value concerns
- "Will this work for my situation?"
- Implementation difficulty
- "What if it doesn't work?"
Address through: FAQ sections, guarantees, comparison content, process transparency
7. Friction Points
Look for:
- Too many form fields
- Unclear next steps
- Confusing navigation
- Required information that shouldn't be required
- Mobile experience issues
- Long load times
Output Format
Structure your recommendations as:
Quick Wins (Implement Now)
Easy changes with likely immediate impact.
High-Impact Changes (Prioritize)
Bigger changes that require more effort but will significantly improve conversions.
Test Ideas
Hypotheses worth A/B testing rather than assuming.
Copy Alternatives
For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.
Page-Specific Frameworks
Homepage CRO
- Clear positioning for cold visitors
- Quick path to most common conversion
- Handle both "ready to buy" and "still researching"
Landing Page CRO
- Message match with traffic source
- Single CTA (remove navigation if possible)
- Complete argument on one page
Pricing Page CRO
- Clear plan comparison
- Recommended plan indication
- Address "which plan is right for me?" anxiety
Feature Page CRO
- Connect feature to benefit
- Use cases and examples
- Clear path to try/buy
Blog Post CRO
- Contextual CTAs matching content topic
- Inline CTAs at natural stopping points
Experiment Ideas
When recommending experiments, consider tests for:
- Hero section (headline, visual, CTA)
- Trust signals and social proof placement
- Pricing presentation
- Form optimization
- Navigation and UX
For comprehensive experiment ideas by page type: See references/experiments.md
Task-Specific Questions
- What's your current conversion rate and goal?
- Where is traffic coming from?
- What does your signup/purchase flow look like after this page?
- Do you have user research, heatmaps, or session recordings?
- What have you already tried?
Related Skills
- signup: If the issue is in the signup process itself
- popups: If considering popups as part of the strategy
- copywriting: If the page needs a complete copy rewrite
- ab-testing: To properly test recommended changes
Form Optimization
For detailed form CRO guidance — including field optimization, multi-step forms, error handling, and form-specific experiments — see references/form.md.
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
1---2name: cro3description: When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't...4license: MIT5---67# Conversion Rate Optimization (CRO)8## When to Use910Use this skill when you need when the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't...111213You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.1415## Initial Assessment1617**Check for product marketing context first:**18If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.1920Before providing recommendations, identify:21221. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other232. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales243. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)2526---2728## CRO Analysis Framework2930Analyze the page across these dimensions, in order of impact:3132### 1. Value Proposition Clarity (Highest Impact)3334**Check for:**35- Can a visitor understand what this is and why they should care within 5 seconds?36- Is the primary benefit clear, specific, and differentiated?37- Is it written in the customer's language (not company jargon)?3839**Common issues:**40- Feature-focused instead of benefit-focused41- Too vague or too clever (sacrificing clarity)42- Trying to say everything instead of the most important thing4344### 2. Headline Effectiveness4546**Evaluate:**47- Does it communicate the core value proposition?48- Is it specific enough to be meaningful?49- Does it match the traffic source's messaging?5051**Strong headline patterns:**52- Outcome-focused: "Get [desired outcome] without [pain point]"53- Specificity: Include numbers, timeframes, or concrete details54- Social proof: "Join 10,000+ teams who..."5556### 3. CTA Placement, Copy, and Hierarchy5758**Primary CTA assessment:**59- Is there one clear primary action?60- Is it visible without scrolling?61- Does the button copy communicate value, not just action?62 - Weak: "Submit," "Sign Up," "Learn More"63 - Strong: "Start Free Trial," "Get My Report," "See Pricing"6465**CTA hierarchy:**66- Is there a logical primary vs. secondary CTA structure?67- Are CTAs repeated at key decision points?6869### 4. Visual Hierarchy and Scannability7071**Check:**72- Can someone scanning get the main message?73- Are the most important elements visually prominent?74- Is there enough white space?75- Do images support or distract from the message?7677### 5. Trust Signals and Social Proof7879**Types to look for:**80- Customer logos (especially recognizable ones)81- Testimonials (specific, attributed, with photos)82- Case study snippets with real numbers83- Review scores and counts84- Security badges (where relevant)8586**Placement:** Near CTAs and after benefit claims8788### 6. Objection Handling8990**Common objections to address:**91- Price/value concerns92- "Will this work for my situation?"93- Implementation difficulty94- "What if it doesn't work?"9596**Address through:** FAQ sections, guarantees, comparison content, process transparency9798### 7. Friction Points99100**Look for:**101- Too many form fields102- Unclear next steps103- Confusing navigation104- Required information that shouldn't be required105- Mobile experience issues106- Long load times107108---109110## Output Format111112Structure your recommendations as:113114### Quick Wins (Implement Now)115Easy changes with likely immediate impact.116117### High-Impact Changes (Prioritize)118Bigger changes that require more effort but will significantly improve conversions.119120### Test Ideas121Hypotheses worth A/B testing rather than assuming.122123### Copy Alternatives124For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.125126---127128## Page-Specific Frameworks129130### Homepage CRO131- Clear positioning for cold visitors132- Quick path to most common conversion133- Handle both "ready to buy" and "still researching"134135### Landing Page CRO136- Message match with traffic source137- Single CTA (remove navigation if possible)138- Complete argument on one page139140### Pricing Page CRO141- Clear plan comparison142- Recommended plan indication143- Address "which plan is right for me?" anxiety144145### Feature Page CRO146- Connect feature to benefit147- Use cases and examples148- Clear path to try/buy149150### Blog Post CRO151- Contextual CTAs matching content topic152- Inline CTAs at natural stopping points153154---155156## Experiment Ideas157158When recommending experiments, consider tests for:159- Hero section (headline, visual, CTA)160- Trust signals and social proof placement161- Pricing presentation162- Form optimization163- Navigation and UX164165**For comprehensive experiment ideas by page type**: See [references/experiments.md](references/experiments.md)166167---168169## Task-Specific Questions1701711. What's your current conversion rate and goal?1722. Where is traffic coming from?1733. What does your signup/purchase flow look like after this page?1744. Do you have user research, heatmaps, or session recordings?1755. What have you already tried?176177---178179## Related Skills180181- **signup**: If the issue is in the signup process itself182- **popups**: If considering popups as part of the strategy183- **copywriting**: If the page needs a complete copy rewrite184- **ab-testing**: To properly test recommended changes185186---187188## Form Optimization189190For detailed form CRO guidance — including field optimization, multi-step forms, error handling, and form-specific experiments — see [references/form.md](references/form.md).191192## Limitations193194- Use this skill only when the task clearly matches its upstream source and local project context.195- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.196- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.