Landing Page CRO Audit & Copy Optimizer

What it does

/landing-fix is a Cursor slash command. Type it in chat to run a saved workflow: Landing Page CRO Audit & Copy Optimizer.

Analyzes landing page conversion bottlenecks: evaluates headline clarity, cognitive friction, CTA contrast, and objection coverage to increase conversion rates.

Audits headline clarity, visual hierarchy, CTA friction, and conversion rates. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /landing-fix for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /landing-fix exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Marketing Kit. It is wired to the Direct Response Copywriter (copywriter) and Growth Marketing Lead (growth-strategist) agents. Required skills: Landing Page Conversion Rate Optimization (CRO); Marketing Psychology & Direct Response Principles.

When to use it

• Use when conversion rates are lower than expected to optimize page elements.
• Use /landing-fix when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just touched production SQL.

When not to use it

• Do not run /landing-fix as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. Review hero section against 5-second clarity test
2. Analyze CTA placement, contrast, and microcopy friction
3. Identify unaddressed customer anxieties and missing trust signals
4. Generate prioritized CRO recommendations with rewritten copy snippets

Example usage

Type this in Cursor chat: /landing-fix Audit hero headline and CTA placement to improve conversion rate

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: docs/marketing/cro-audit.md

Best practices

• Keep the prompt specific. /landing-fix Audit hero headline and CTA placement to improve conversion rate is the shape: object, constraint, and outcome.
• Let the listed agents work in order: copywriter → growth-strategist.
• Save outputs in the repo. Chat-only answers evaporate.
• Marketing commands write to docs/marketing/ so the next command can read positioning before it writes a landing page.

Common mistakes

• Typing /landing-fix with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the Landing Page Conversion Rate Optimization (CRO) skill that the command depends on.