Cro
Optimize conversion rates.
Marketing teams lose hours to ad-hoc, inconsistent cro work — Optimize conversion rates. Use when: auditing landing pages, testing forms, or improving checkout flow. This playbook turns the process into a repeatable, brand-aware workflow.
Who it's for: digital marketers, marketing managers, growth marketers
Example
"Run /cro for our brand" → Cro workflow output with brand context, structured inputs captured, process steps executed, and a complete deliverable ready for review.
CLAUDE.md Template
New here? 3-minute setup guide → | Already set up? Copy the template below.
# Cro
# CRO (Conversion Rate Optimization)
## When to Use This Skill
Activate this skill when the user's request involves any of the following:
- Auditing a landing page for conversion performance
- Designing or improving a landing page layout, copy, or user flow
- Setting up, analyzing, or interpreting A/B tests or multivariate tests
- Optimizing web forms (lead gen, signup, contact, application)Get new playbooks like this one
One email a week with new Claude Code workflows. Free, like everything here.
No spam. Unsubscribe anytime.
What This Does
Optimize conversion rates.
Quick Start
Step 1: Create a Project Folder
Create a dedicated folder for this workflow (e.g. ~/marketing/cro).
Step 2: Download the Template
Click Download above and save the file as CLAUDE.md in that folder.
Step 3: Run the Workflow
Open the folder in Claude Code and describe your goal. Claude will prompt you for any missing inputs, follow the structured process, and produce a complete deliverable.
Inputs You'll Need
Claude will prompt for the brand context, objective, and any asset references needed to produce the deliverable.
How It Works
Standard Landing Page Audit (Most Common Use Case)
- 5-second scan -- Review the page as a first-time visitor. Can you identify what the company does, who it is for, and what action to take within 5 seconds?
- Above-the-fold audit -- Evaluate headline specificity, subheadline support, hero relevance, and CTA prominence. The fold is the most valuable real estate.
- Trust and credibility -- Inventory all trust signals (testimonials, logos, reviews, certifications, guarantees). Identify gaps where social proof is missing at critical decision points.
- CTA analysis -- Count all CTAs on the page. Check for competing actions, button copy specificity ("Get My Free Trial" beats "Submit"), contrast ratio, and placement frequency.
- Content flow -- Walk through the page section by section. Does it follow a logical persuasion sequence? Problem, solution, proof, action?
- Form/conversion point -- Evaluate the form or conversion mechanism. Count fields, assess labels, check error handling, and evaluate the micro-copy around the submit button.
- Mobile audit -- Review the same page on mobile. Check touch targets (minimum 44x44px), scroll depth to CTA, horizontal scrolling issues, and load time.
- Speed check -- Note any visible performance issues. Recommend Core Web Vitals audit if speed appears to be a factor.
- Prioritized recommendations -- Deliver findings as a prioritized list using the ICE framework. Quick wins first, structural changes second, redesign-level changes last.
A/B Test Design Process
- Identify the problem -- Use data (analytics, heatmaps, session recordings, user feedback) to pinpoint the conversion bottleneck.
- Form hypothesis -- Write a structured hypothesis: "If we [change X], then [metric Y] will [increase/decrease] by [estimated amount] because [rationale based on evidence]."
- Score with ICE -- Rate Impact, Confidence, and Ease on a 1-10 scale. Prioritize tests with highest composite scores.
- Calculate requirements -- Determine sample size needed based on current conversion rate and minimum detectable effect. Estimate test duration based on daily traffic.
- Design variation -- Create the test variation. Change only one variable per test (unless running a multivariate test with sufficient traffic).
- QA the test -- Verify tracking, check both variations across devices and browsers, confirm that the test does not break downstream flows.
- Run and monitor -- Launch the test. Do not peek at results before reaching calculated sample size. Monitor for technical issues only.
- Analyze and document -- At the end of the test, evaluate statistical significance, check segment-level results, calculate revenue impact, and document learnings regardless of outcome.
What You Get
A complete, brand-aligned deliverable ready to review, share, or hand off to execution.