page-cro

---
name: page-cro
description: Use when analyzing a marketing page (homepage, landing, pricing, feature) to improve conversion rate — headline, CTA, trust signals, or friction points.
category: Marketing
version: 1.0.0
tools: []
---

# Page Conversion Rate Optimization (CRO)

Analyze marketing pages and produce actionable recommendations to improve conversion rates.

Check the Knowledge Base for existing product-marketing context first, and use it instead of re-asking questions already covered there. Before recommending anything, identify: page type (homepage, landing page, pricing, feature, blog, about), the primary conversion goal (signup, demo request, purchase, subscribe, download, contact sales), and traffic context (organic, paid, email, social).

## CRO Analysis Framework

Work through these dimensions in order of impact:

**1. Value proposition clarity (highest impact).** Can a visitor understand what this is and why they should care within 5 seconds? Is the primary benefit clear, specific, and differentiated, written in the customer's language rather than company jargon? Common failures: feature-focused instead of benefit-focused, too vague or too clever, trying to say everything instead of the one most important thing.

**2. Headline effectiveness.** Does it communicate the core value proposition, match the traffic source's messaging, and stay specific enough to be meaningful? Strong patterns: outcome-focused ("Get [outcome] without [pain point]"), specificity (numbers, timeframes, concrete details), social proof ("Join 10,000+ teams who...").

**3. CTA placement, copy, and hierarchy.** Is there one clear primary action, visible without scrolling, with button copy that communicates value rather than just action (weak: "Submit," "Sign Up," "Learn More"; strong: "Start Free Trial," "Get My Report," "See Pricing")? Is there a logical primary/secondary hierarchy, repeated at key decision points?

**4. Visual hierarchy and scannability.** Can someone scanning get the main message? Are the most important elements visually prominent, with enough white space, and do images support rather than distract from the message?

**5. Trust signals and social proof.** Customer logos (especially recognizable ones), attributed testimonials with photos, case-study snippets with real numbers, review scores/counts, security badges where relevant — placed near CTAs and after benefit claims.

**6. Objection handling.** Address price/value concerns, "will this work for my situation," implementation difficulty, and "what if it doesn't work" through FAQ sections, guarantees, comparison content, and process transparency.

**7. Friction points.** Too many form fields, unclear next steps, confusing navigation, unnecessary required fields, mobile experience issues, and long load times.

## Producing the Audit

A mechanical scan for conversion signals — CTA presence/count, form weight, social proof, trust elements — anchors a numeric score before the manual framework pass; use that score to seed the Quick Wins list, then walk the seven dimensions above.

## Output Format

Structure recommendations as: **Quick Wins** (easy changes, likely immediate impact), **High-Impact Changes** (bigger effort, significant conversion improvement), **Test Ideas** (hypotheses worth A/B testing rather than assuming), and **Copy Alternatives** (2–3 options per key element with rationale for each).

## Page-Specific Frameworks

Homepage: clear positioning for cold visitors, a quick path to the most common conversion, and handling for both "ready to buy" and "still researching" visitors. Landing page: message match with the traffic source, a single CTA (remove navigation if possible), a complete argument on one page. Pricing page: clear plan comparison, a recommended-plan indicator, addressing "which plan is right for me" anxiety. Feature page: connect the feature to the benefit, use cases and examples, a clear path to try/buy. Blog post: contextual CTAs matching the content topic, placed inline at natural stopping points.

## Experiment Ideas

Consider tests for: hero section (headline, visual, CTA), trust-signal placement, pricing presentation, form optimization, and navigation/UX.

## Communication

Organize recommendations as Quick Wins → High-Impact → Test Ideas, never a flat list. Every recommendation ties back to the framework dimension it addresses. Copy alternatives come in sets of 2–3 with reasoning for each. Apply the page-specific framework explicitly rather than giving generic advice. Never recommend A/B testing as a substitute for an obvious fix — call out what to fix vs. what to test. Don't prescribe layout changes without accounting for traffic source and audience context.

## Proactive Triggers

- "This page isn't converting" or high bounce rate mentioned → run the full CRO analysis framework.
- A new landing page is being built → proactively offer a CRO review before launch.
- Paid traffic is mentioned → flag message-match and single-CTA best practices immediately.
- Pricing page discussion → recommend a pricing-page CRO review alongside positioning work.
- A/B test results are reviewed → offer a follow-up page-CRO analysis for the next round of hypotheses.

## Coordinate With
@mention a signup-flow specialist if the page converts well but users drop during registration; a form specialist for standalone lead-capture/contact forms; a popup specialist only after core page conversion is already solid; a copywriter for a full messaging rebuild rather than CTA tweaks; an experimentation specialist once there's a clear hypothesis to test; and an onboarding specialist if post-conversion activation is the real bottleneck.