Landing Page Cro

---
name: landing-page-cro
description: Improve an existing landing, sales, homepage, pricing, feature, or lead-capture page with prioritized copy, structure, trust, CTA, friction, and test changes.
---

# Landing Page CRO

Improve the conversion path of an existing page while separating observations from testable hypotheses.

## Job contract

- Owns: page-level conversion clarity, persuasion, trust, hierarchy, friction, and experiments.
- Does not own: underlying offer design (`offer-builder`) or voice cleanup alone (`de-slop`).
- Required input: page copy, screenshots, files, or a URL the agent can inspect, plus the intended action when known.
- Finished deliverable: prioritized page diagnosis and copy-ready changes.

## Workflow

1. Identify page type, intended visitor, traffic source, and primary action.
2. Run the five-second test: what it is, who it is for, why it matters, and what to do next.
3. Trace message match from source to headline to proof to CTA.
4. Inspect value clarity, CTA hierarchy, evidence, objections, friction, scannability, mobile risks, and next-step uncertainty.
5. Separate confirmed problems from hypotheses that require analytics or testing.
6. Prioritize by likely effect, confidence, and effort.
7. Draft replacement copy for the highest-priority sections.

## Output

```markdown
# Landing Page Conversion Review

## Conversion Goal And Visitor
[What is known and assumed]

## What Is Blocking Action
[Evidence from the page]

## Priority Changes
| Priority | Change | Why | Confidence | Effort |

## Copy-Ready Replacements
[Headline, subhead, CTA, proof, objection copy]

## Test Queue
[Hypothesis, variant, metric, decision rule]

## Missing Evidence
[Analytics, traffic, research, or device checks needed]
```

## Guardrails

- Never claim a conversion lift before a real test.
- Do not invent customer proof, urgency, guarantees, or performance data.
- Preserve the defined offer unless the user explicitly asks to change it.