skills/ai-marketing-suite/skills/market-landing/SKILL.md
# Landing Page CRO Analysis ## Skill Purpose Perform a comprehensive Conversion Rate Optimization (CRO) analysis on any landing page. This skill produces a section-by-section teardown with prioritized, actionable fixes that directly impact conversion rates. ## When to Use - User provides a landing page URL and asks for conversion optimization - User asks for landing page feedback, review, or audit - User wants to improve signup, lead capture, or purchase rates - Triggered by `/market landing <
npx skillsauth add kennyolofsson23-netizen/claude-code-config skills/ai-marketing-suite/skills/market-landingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Perform a comprehensive Conversion Rate Optimization (CRO) analysis on any landing page. This skill produces a section-by-section teardown with prioritized, actionable fixes that directly impact conversion rates.
/market landing <url> or /market cro <url>Determine which type of landing page you are analyzing. This affects benchmark expectations and scoring weights.
| Page Type | Primary Goal | Good CR | Great CR | |---|---|---|---| | Lead Capture | Email/form submission | 5-10% | 15%+ | | SaaS Signup | Free trial or freemium signup | 3-7% | 10%+ | | E-commerce Product | Add to cart / Purchase | 2-4% | 5%+ | | Webinar Registration | Register for event | 20-30% | 40%+ | | App Download | Install app | 10-15% | 20%+ | | Waitlist | Join waitlist | 15-25% | 35%+ | | Consultation Booking | Schedule a call | 5-10% | 15%+ | | Nonprofit Donation | Make a donation | 2-5% | 8%+ |
Analyze each section in order. Score each section 1-10 and provide specific findings.
The first screen a visitor sees. This is where 80% of conversion decisions begin.
Checklist:
Scoring Criteria:
How clearly the page communicates WHY someone should convert.
Checklist:
Evaluate Using the 4U Framework:
Evidence that others trust and benefit from this product/service.
Types of Social Proof (ranked by persuasion power):
Checklist:
How the page presents what the product/service includes.
Checklist:
Feature-to-Benefit Translation Check: Bad: "AI-powered analytics dashboard" Good: "See exactly which campaigns drive revenue -- AI analyzes your data so you don't have to"
How the page addresses reasons a visitor might NOT convert.
Common Objections by Page Type:
| Objection | How to Address | |---|---| | "Too expensive" | ROI calculator, price comparison, money-back guarantee | | "Not sure it works" | Case studies, free trial, demo video | | "Too complicated" | Setup wizard, onboarding support, "get started in 5 minutes" | | "Not sure I need it" | Problem agitation, cost of inaction | | "What if I don't like it?" | Free trial, money-back guarantee, cancel anytime | | "Is my data safe?" | Security badges, compliance logos, privacy policy link | | "I need to ask my team" | Shareable comparison page, team trial, ROI one-pager |
Checklist:
The conversion mechanism itself.
CTA Button Checklist:
CTA Copy Scoring:
The bottom of the page and supporting elements.
Checklist:
Score the overall page copy on 5 dimensions (1-10 each):
Calculate the Copy Score: average of all 5 dimensions, multiplied by 10 for a score out of 100.
If the page has a form, evaluate:
| Element | Best Practice | |---|---| | Field count | Every additional field reduces conversion ~7%. Lead capture: 3-5 fields max. | | Labels | Use inline labels or floating labels. Avoid placeholder-only labels. | | Button text | Match the value proposition. "Get My Free Guide" > "Submit". | | Error handling | Inline validation. Specific error messages. Don't clear the entire form on error. | | Multi-step | Break long forms into steps with progress indicator. | | Required vs optional | Mark optional fields, not required ones. | | Auto-fill | Enable browser auto-fill for standard fields. | | Field types | Use appropriate input types (email, tel, url) for mobile keyboards. |
Mobile accounts for 60%+ of web traffic. Check:
Reference these conversion impact benchmarks:
| Load Time | Conversion Impact | |---|---| | 0-2 seconds | Baseline (optimal) | | 2-3 seconds | -7% conversion rate | | 3-5 seconds | -20% conversion rate | | 5-8 seconds | -35% conversion rate | | 8+ seconds | -50%+ conversion rate |
Check for common speed issues:
Format each test as a hypothesis:
Template: "If we [CHANGE], then [METRIC] will [IMPROVE/INCREASE] because [REASON]."
Example tests to consider:
Even without actual heat map data, provide guidance on:
Generate a file called LANDING-CRO.md in the project root or output directory with:
# Landing Page CRO Analysis
## [Page URL]
### Analysis Date: [date]
---
## Overall CRO Score: [X/100]
## Page Type: [identified type]
## Current Estimated Conversion Rate: [estimate based on findings]
## Target Conversion Rate: [realistic improvement target]
---
## Section-by-Section Analysis
### 1. Hero Section [Score: X/10]
**Findings:**
- [specific observations]
**Fixes (Priority: HIGH/MEDIUM/LOW):**
- [specific, actionable recommendations]
[Repeat for all 7 sections]
---
## Copy Score: [X/100]
| Dimension | Score | Notes |
|---|---|---|
| Clarity | X/10 | [notes] |
| Urgency | X/10 | [notes] |
| Specificity | X/10 | [notes] |
| Proof | X/10 | [notes] |
| Action Orientation | X/10 | [notes] |
---
## Form Audit
[findings and recommendations]
---
## Mobile Audit
[findings and recommendations]
---
## A/B Test Recommendations
1. [Hypothesis format test]
2. [Hypothesis format test]
3. [Hypothesis format test]
---
## Prioritized Fix List
### Quick Wins (implement this week)
1. [fix with expected impact]
### Medium-Term (implement this month)
1. [fix with expected impact]
### Strategic (implement this quarter)
1. [fix with expected impact]
---
## Before/After Wireframe Suggestions
[Text-based wireframe descriptions of current vs recommended layout]
/market audit previously, incorporate those findings into the CRO analysis for a more complete picture.development
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
testing
Full QA pass: run all tests, check types, catch regressions, write missing tests. Use when the user says "run tests", "QA", "verify changes", "check for regressions", "test everything", or "make sure it works".
development
Provides guidance for property-based testing across multiple languages and smart contracts. Use when writing tests, reviewing code with serialization/validation/parsing patterns, designing features, or when property-based testing would provide stronger coverage than example-based tests.
development
Initialize a new project with Kenny's universal conventions and stack-appropriate infrastructure. Use this skill whenever: setting up a new project, creating a new repo, scaffolding a new app, starting fresh on a new idea, 'init project', 'new project', 'set up a new app', 'create a project for X', or any variant of starting a new codebase from scratch. Also trigger when the user says 'bootstrap', 'scaffold', or 'kickstart'. This skill ensures every project gets the same quality gates and conventions while adapting infrastructure to the chosen stack.