Page Conversion Rate Optimization (CRO)
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 .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.
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
Tools
| Tool |
Invocation |
Output |
| Conversion audit |
python3 scripts/conversion_audit.py --file page.html (or --url https://...; --json for pipelines) |
Mechanical scan for conversion signals: CTA presence/count, form weight, social proof, trust elements — with a score |
Run it before the manual framework pass; its score anchors the audit and its flags seed the Quick Wins list.
Output Format
Open with the conversion_audit.py score, then structure 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
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-flow-cro — WHEN: the page itself converts well but users drop off during the signup or registration process that follows it. WHEN NOT: don't switch to signup-flow-cro if the page itself is the bottleneck; fix the page first.
- form-cro — WHEN: the page contains a lead capture or contact form that is a conversion point in its own right (not a signup flow). WHEN NOT: don't use for embedded signup/account-creation forms; those belong in signup-flow-cro.
- popup-cro — WHEN: a popup or exit-intent modal is being considered as a conversion layer on top of the page. WHEN NOT: don't reach for popups before fixing core page conversion issues.
- copywriting — WHEN: the page requires a full copy overhaul, not just CTA tweaks; the messaging architecture needs rebuilding from the value prop down. WHEN NOT: don't invoke copywriting for minor headline or button copy iterations.
- ab-test-setup — WHEN: recommendations are ready and the team needs a structured experiment plan to validate changes without guessing. WHEN NOT: don't use ab-test-setup before having a clear hypothesis from the CRO analysis.
- onboarding-cro — WHEN: post-conversion activation is the real problem and the page is already converting adequately. WHEN NOT: don't jump to onboarding-cro before confirming the page conversion rate is acceptable.
- marketing-context — WHEN: always read
.claude/product-marketing-context.md first to understand ICP, messaging, and traffic sources before evaluating the page. WHEN NOT: skip if the user has shared all relevant context directly.
Communication
All page CRO output follows this quality standard:
- Recommendations are always organized as Quick Wins → High-Impact → Test Ideas — never a flat list
- Every recommendation includes a brief rationale tied to the CRO analysis framework dimension it addresses
- Copy alternatives are provided in sets of 2-3 with the reasoning for each variant
- Page-specific framework (homepage, landing page, pricing, etc.) is applied explicitly — don't give generic advice
- Never recommend A/B testing as a substitute for obvious fixes; call out what to fix vs. what to test
- Avoid prescribing layout without acknowledging traffic source and audience context
Proactive Triggers
Automatically surface page-cro recommendations when:
- "This page isn't converting" — Any mention of low conversion, poor page performance, or high bounce rate immediately activates the CRO analysis framework.
- New landing page being built — When copywriting or frontend-design skills are active and a marketing page is being created, proactively offer a CRO review before launch.
- Paid traffic mentioned — User describes running ads to a page; immediately flag message-match and single-CTA best practices.
- Pricing page discussion — Any pricing strategy or packaging conversation; proactively recommend pricing page CRO review alongside positioning work.
- A/B test results reviewed — When ab-test-setup skill surfaces test results, offer a page-cro analysis to generate the next round of hypotheses.
Output Artifacts
| Artifact |
Format |
Description |
| CRO Audit Summary |
Markdown sections |
Analysis across all 7 framework dimensions with issue severity ratings |
| Quick Wins List |
Bullet list |
≤5 changes implementable immediately with expected impact |
| High-Impact Recommendations |
Structured list |
Each with rationale, effort estimate, and success metric |
| Copy Alternatives |
Side-by-side table |
2-3 variants per key element (headline, CTA, subhead) with reasoning |
| A/B Test Hypotheses |
Table |
Hypothesis × variant description × success metric × priority |
1---2name: page-cro3description: When 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 conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.4license: MIT5metadata:6 source: https://skillmd.com/skills/bestagentkits/page-cro7 version: 1.0.08 author: Alireza Rezvani9 category: marketing10 updated: 2026-03-0611---1213# Page Conversion Rate Optimization (CRO)1415You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.1617## Initial Assessment1819**Check for product marketing context first:**20If `.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.2122Before providing recommendations, identify:23241. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other252. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales263. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)2728---2930## CRO Analysis Framework3132Analyze the page across these dimensions, in order of impact:3334### 1. Value Proposition Clarity (Highest Impact)3536**Check for:**37- Can a visitor understand what this is and why they should care within 5 seconds?38- Is the primary benefit clear, specific, and differentiated?39- Is it written in the customer's language (not company jargon)?4041**Common issues:**42- Feature-focused instead of benefit-focused43- Too vague or too clever (sacrificing clarity)44- Trying to say everything instead of the most important thing4546### 2. Headline Effectiveness4748**Evaluate:**49- Does it communicate the core value proposition?50- Is it specific enough to be meaningful?51- Does it match the traffic source's messaging?5253**Strong headline patterns:**54- Outcome-focused: "Get [desired outcome] without [pain point]"55- Specificity: Include numbers, timeframes, or concrete details56- Social proof: "Join 10,000+ teams who..."5758### 3. CTA Placement, Copy, and Hierarchy5960**Primary CTA assessment:**61- Is there one clear primary action?62- Is it visible without scrolling?63- Does the button copy communicate value, not just action?64 - Weak: "Submit," "Sign Up," "Learn More"65 - Strong: "Start Free Trial," "Get My Report," "See Pricing"6667**CTA hierarchy:**68- Is there a logical primary vs. secondary CTA structure?69- Are CTAs repeated at key decision points?7071### 4. Visual Hierarchy and Scannability7273**Check:**74- Can someone scanning get the main message?75- Are the most important elements visually prominent?76- Is there enough white space?77- Do images support or distract from the message?7879### 5. Trust Signals and Social Proof8081**Types to look for:**82- Customer logos (especially recognizable ones)83- Testimonials (specific, attributed, with photos)84- Case study snippets with real numbers85- Review scores and counts86- Security badges (where relevant)8788**Placement:** Near CTAs and after benefit claims8990### 6. Objection Handling9192**Common objections to address:**93- Price/value concerns94- "Will this work for my situation?"95- Implementation difficulty96- "What if it doesn't work?"9798**Address through:** FAQ sections, guarantees, comparison content, process transparency99100### 7. Friction Points101102**Look for:**103- Too many form fields104- Unclear next steps105- Confusing navigation106- Required information that shouldn't be required107- Mobile experience issues108- Long load times109110---111112## Tools113114| Tool | Invocation | Output |115|---|---|---|116| Conversion audit | `python3 scripts/conversion_audit.py --file page.html` (or `--url https://...`; `--json` for pipelines) | Mechanical scan for conversion signals: CTA presence/count, form weight, social proof, trust elements — with a score |117118Run it before the manual framework pass; its score anchors the audit and its flags seed the Quick Wins list.119120---121122## Output Format123124Open with the `conversion_audit.py` score, then structure recommendations as:125126### Quick Wins (Implement Now)127Easy changes with likely immediate impact.128129### High-Impact Changes (Prioritize)130Bigger changes that require more effort but will significantly improve conversions.131132### Test Ideas133Hypotheses worth A/B testing rather than assuming.134135### Copy Alternatives136For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.137138---139140## Page-Specific Frameworks141142### Homepage CRO143- Clear positioning for cold visitors144- Quick path to most common conversion145- Handle both "ready to buy" and "still researching"146147### Landing Page CRO148- Message match with traffic source149- Single CTA (remove navigation if possible)150- Complete argument on one page151152### Pricing Page CRO153- Clear plan comparison154- Recommended plan indication155- Address "which plan is right for me?" anxiety156157### Feature Page CRO158- Connect feature to benefit159- Use cases and examples160- Clear path to try/buy161162### Blog Post CRO163- Contextual CTAs matching content topic164- Inline CTAs at natural stopping points165166---167168## Experiment Ideas169170When recommending experiments, consider tests for:171- Hero section (headline, visual, CTA)172- Trust signals and social proof placement173- Pricing presentation174- Form optimization175- Navigation and UX176177---178179## Task-Specific Questions1801811. What's your current conversion rate and goal?1822. Where is traffic coming from?1833. What does your signup/purchase flow look like after this page?1844. Do you have user research, heatmaps, or session recordings?1855. What have you already tried?186187---188189## Related Skills190191- **signup-flow-cro** — WHEN: the page itself converts well but users drop off during the signup or registration process that follows it. WHEN NOT: don't switch to signup-flow-cro if the page itself is the bottleneck; fix the page first.192- **form-cro** — WHEN: the page contains a lead capture or contact form that is a conversion point in its own right (not a signup flow). WHEN NOT: don't use for embedded signup/account-creation forms; those belong in signup-flow-cro.193- **popup-cro** — WHEN: a popup or exit-intent modal is being considered as a conversion layer on top of the page. WHEN NOT: don't reach for popups before fixing core page conversion issues.194- **copywriting** — WHEN: the page requires a full copy overhaul, not just CTA tweaks; the messaging architecture needs rebuilding from the value prop down. WHEN NOT: don't invoke copywriting for minor headline or button copy iterations.195- **ab-test-setup** — WHEN: recommendations are ready and the team needs a structured experiment plan to validate changes without guessing. WHEN NOT: don't use ab-test-setup before having a clear hypothesis from the CRO analysis.196- **onboarding-cro** — WHEN: post-conversion activation is the real problem and the page is already converting adequately. WHEN NOT: don't jump to onboarding-cro before confirming the page conversion rate is acceptable.197- **marketing-context** — WHEN: always read `.claude/product-marketing-context.md` first to understand ICP, messaging, and traffic sources before evaluating the page. WHEN NOT: skip if the user has shared all relevant context directly.198199---200201## Communication202203All page CRO output follows this quality standard:204- Recommendations are always organized as **Quick Wins → High-Impact → Test Ideas** — never a flat list205- Every recommendation includes a brief rationale tied to the CRO analysis framework dimension it addresses206- Copy alternatives are provided in sets of 2-3 with the reasoning for each variant207- Page-specific framework (homepage, landing page, pricing, etc.) is applied explicitly — don't give generic advice208- Never recommend A/B testing as a substitute for obvious fixes; call out what to fix vs. what to test209- Avoid prescribing layout without acknowledging traffic source and audience context210211---212213## Proactive Triggers214215Automatically surface page-cro recommendations when:2162171. **"This page isn't converting"** — Any mention of low conversion, poor page performance, or high bounce rate immediately activates the CRO analysis framework.2182. **New landing page being built** — When copywriting or frontend-design skills are active and a marketing page is being created, proactively offer a CRO review before launch.2193. **Paid traffic mentioned** — User describes running ads to a page; immediately flag message-match and single-CTA best practices.2204. **Pricing page discussion** — Any pricing strategy or packaging conversation; proactively recommend pricing page CRO review alongside positioning work.2215. **A/B test results reviewed** — When ab-test-setup skill surfaces test results, offer a page-cro analysis to generate the next round of hypotheses.222223---224225## Output Artifacts226227| Artifact | Format | Description |228|----------|--------|-------------|229| CRO Audit Summary | Markdown sections | Analysis across all 7 framework dimensions with issue severity ratings |230| Quick Wins List | Bullet list | ≤5 changes implementable immediately with expected impact |231| High-Impact Recommendations | Structured list | Each with rationale, effort estimate, and success metric |232| Copy Alternatives | Side-by-side table | 2-3 variants per key element (headline, CTA, subhead) with reasoning |233| A/B Test Hypotheses | Table | Hypothesis × variant description × success metric × priority |