# Mk Page Cro

> 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. EN triggers "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," "why isn't this page working," "my landing page sucks," "nobody's converting," "low conversion rate," "bounce rate is too high," "people leave without signing up," "this page needs work," "optimize my landing page." FR triggers "optimise ma page," "améliore les conversions," "ma landing page ne convertit pas," "taux de conversion trop bas," "audit CRO," "pourquoi cette page ne convertit pas," "personne ne s'inscrit," "trop de rebond." Use this even if the user just shares a URL and asks for feedback — they probably want conversion help. For signup/registration flows, see mk-signup-flow-cro. For post-signup activation, see mk-onboarding-cro. For forms outside of signup, see mk-form-cro. For popups/modals, see mk-popup-cro.

- Skill: `agentik-os/mk-page-cro` (Agent Skill)
- Install (CLI): `npx skillmds@latest add agentik-os/mk-page-cro`
- Raw SKILL.md: https://api.skillmd.com/api/skills/agentik-os/mk-page-cro/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: agentik-os (https://skillmd.com/u/agentik-os)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/agentik-os/mk-page-cro

---


# 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 `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

> Portability note: the `.agents/` / `.claude/` context file is an optional project convention — if it is absent, skip silently and gather context from the page + the Task-Specific Questions below. Never block on it.

Before providing recommendations, identify:

1. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other
2. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales
3. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)

---

## Dynamic Workflow orchestration

A CRO audit is inherently multi-angle. Run it as a fan-out workflow over the 7 framework dimensions rather than one linear pass — each dimension is an independent analytical lens.

1. **Plan** — Capture the page (live URL via the Playwright CLI screenshot, or the pasted markup/copy). Lock the Page Type + Primary Conversion Goal + Traffic Context from Initial Assessment. These frame every lens.
2. **Parallel fan-out** — Analyze all 7 dimensions concurrently, one lens each, against the SAME captured evidence:
   - L1 Value Proposition Clarity · L2 Headline Effectiveness · L3 CTA Placement/Copy/Hierarchy · L4 Visual Hierarchy & Scannability · L5 Trust Signals & Social Proof · L6 Objection Handling · L7 Friction Points
   - Each lens emits findings as `dimension → issue → evidence (quote/element/screenshot region) → recommendation → expected lift direction`.
3. **Adversarial verify (2-of-3)** — Before a finding ships, falsify it: (a) is the issue grounded in the actual captured page, not a generic CRO truism? (b) does the recommendation match THIS Page Type + Traffic Context (a landing-page rule may be wrong for a homepage)? (c) is the claimed impact direction defensible? A finding survives only if ≥2 of 3 hold. Drop or downgrade the rest.
4. **Synthesize** — Merge surviving findings, dedupe overlaps (e.g. a weak headline often surfaces in both L1 and L2 — report once), then rank by impact x ease into the Output Format below. Synthesis is your own judgment, never a raw concat of the 7 lenses.
5. **Loop-until-dry** — Multi-page or full-funnel request → repeat the cycle per page until every requested page is covered; do not stop at the first page.

---

## 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

The deliverable is ONE prioritized CRO recommendation report, structured 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.

### Output contract
Every finding in the report carries: the dimension (L1–L7), the specific on-page evidence it is anchored to, the recommendation, and an impact x ease ranking. No orphan opinions.

### VERIFY before delivering
- [ ] Page Type, Conversion Goal, and Traffic Context are stated and every recommendation is consistent with them.
- [ ] Each of the 7 dimensions was assessed (or explicitly marked N/A with reason).
- [ ] Every finding cites real on-page evidence (a quoted line, a named element, a screenshot region) — passed the 2-of-3 verify.
- [ ] Findings are deduped and ranked; Quick Wins are genuinely low-effort.
- [ ] Copy Alternatives are concrete strings, not descriptions of strings.

### Guardrails (evidence / no-hallucination / scope)
- **Evidence or it didn't happen** — anchor every claim to the actual page. If you cannot see the page (no URL captured, no markup pasted), say so and ask for it; never invent the page's content or fabricate a conversion rate.
- **No fabricated metrics** — never assert a numeric lift ("+30% conversions"). Express impact as a direction + rationale unless the user supplies real data.
- **Scope discipline** — optimize the page in front of you. Signup flow → mk-signup-flow-cro; forms → mk-form-cro; popups → mk-popup-cro; full rewrite → mk-copywriting. Recommend, don't silently expand scope.

---

## 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](references/experiments.md)

---

## Task-Specific Questions

1. What's your current conversion rate and goal?
2. Where is traffic coming from?
3. What does your signup/purchase flow look like after this page?
4. Do you have user research, heatmaps, or session recordings?
5. What have you already tried?

---

## Related Skills

- **signup-flow-cro**: If the issue is in the signup process itself
- **form-cro**: If forms on the page need optimization
- **popup-cro**: If considering popups as part of the strategy
- **copywriting**: If the page needs a complete copy rewrite
- **ab-test-setup**: To properly test recommended changes