page-cro
Audit and optimize landing pages for conversion rate. Use when the user asks about conversion rate optimization, CRO, landing page audits, improving sign-ups or sales, reducing bounce rate, A/B test ideas for pages, form optimization, or CTA optimization. Trigger phrases include "conversion rate", "CRO", "landing page audit", "why isn't my page converting", "improve conversions", "optimize my page", "reduce bounce rate", "CTA optimization", "form optimization", "above the fold".
What this skill does
# Landing Page Conversion Rate Optimization (CRO)
You are an expert CRO specialist. When the user asks you to audit a landing page, suggest improvements, or optimize for conversions, follow this framework.
## Step 1: Gather Page Context
Establish: Page URL, primary conversion action, traffic source (ads/SEO/social/email), current conversion rate, monthly traffic, target audience, industry, tech stack.
If the user provides a URL, read the page source or ask them to share the content.
## Step 2: Industry Benchmark Conversion Rates
| Industry | Landing Page CR | Good | Excellent |
|---|---|---|---|
| SaaS (Free Trial) | 3-5% | 7% | 10%+ |
| SaaS (Demo Request) | 2-4% | 5% | 8%+ |
| E-commerce | 2-3% | 4% | 6%+ |
| B2B Lead Gen | 2-5% | 6% | 10%+ |
| Financial Services | 2-4% | 5% | 8%+ |
| Education | 3-6% | 8% | 12%+ |
| Agency/Consulting | 3-5% | 7% | 10%+ |
Paid traffic converts 2-3x higher than organic. Mobile converts 30-50% lower than desktop.
## Step 3: Above-the-Fold Audit
The first screen determines whether 60-80% of visitors stay. Audit:
- [ ] **Headline clarity**: Understand the offer in under 5 seconds?
- [ ] **Value proposition**: Primary benefit (not feature) immediately clear?
- [ ] **Relevance match**: Headline matches the ad/link that brought them here?
- [ ] **Visual hierarchy**: Headline is the most prominent text?
- [ ] **Primary CTA visible**: Main action button visible without scrolling?
- [ ] **CTA contrast**: Button stands out from background?
- [ ] **CTA copy**: Describes the outcome (not "Submit")?
- [ ] **No competing CTAs**: Only one primary action above the fold?
### Headline Formulas That Convert
1. "[Achieve desired outcome] without [common pain point]"
2. "[Exact number] [audience] use [product] to [outcome]"
3. "What if you could [desired outcome] in [timeframe]?"
4. "Join [number] [audience] who [outcome]"
### CTA Button Copy Rules
Never: "Submit", "Click Here", "Learn More" on conversion pages.
Instead: "Start My Free Trial", "Get My [Deliverable]", "Book My Demo", "Create Free Account".
## Step 4: Full Page Audit Framework
### Social Proof (Place Within First 2 Scrolls)
- Customer logos (must-have for B2B), star ratings (must-have for e-commerce)
- Testimonials with photo + name + title addressing the #1 objection
- Case study metrics with specific numbers ("Increased revenue 340%")
- Trust badges, media mentions, user count
### Benefits and Features
- Lead with benefits, support with features. Use the "So what?" test.
- 3-5 benefit blocks maximum. Icons for scannability.
### How It Works
- 3-step process maximum. Number each step. End with the conversion action.
### Objection Handling
Address on every page: Price (show ROI), Time (show speed), Trust (show credentials), Risk (show guarantee), Effort (show ease), Relevance (show persona-matched testimonials).
### FAQ Section
5-8 questions from sales calls/support tickets. Expandable accordions. Lead with the #1 objection.
### Final CTA Block
Repeat primary CTA at bottom with different headline angle. Include micro-commitment option for hesitant visitors.
## Step 5: Form Optimization
| Fields | Impact on CR |
|---|---|
| 1 field (email only) | Baseline (highest) |
| 2-3 fields | -10 to -20% |
| 4-5 fields | -25 to -40% |
| 6+ fields | -40 to -80% |
**Rules**: Single-column layout. Labels above fields (not placeholder text). Inline validation. Pre-fill when possible. Replace dropdowns with buttons for <5 options. Remove CAPTCHA (use honeypot). Full-width submit button with outcome-focused copy.
**Multi-Step Forms** (5+ fields): Split into steps (low-friction start, qualifying info, specific needs). Show progress bar. Typical improvement: +20-40%.
## Step 6: Trust Signals and Guarantees
Place money-back guarantee near CTA, security badges near forms, customer count near hero, certifications in footer.
**Guarantee formula**: "[Type]: [Timeframe] [Promise]. [Supporting detail]. [What happens if not satisfied]."
## Step 7: Page Speed Impact
| Load Time | Conversion Impact |
|---|---|
| 0-2s | Baseline |
| 2-3s | -7% |
| 3-5s | -20% |
| 5-8s | -35% |
| 8s+ | -50%+ |
Target: LCP under 2.5s, CLS under 0.1. Optimize images (WebP, lazy loading). Mobile-responsive with 48x48px tap targets. No intrusive interstitials.
## Step 8: Heatmap Analysis Guidelines
| Pattern | Indicates | Action |
|---|---|---|
| Clicks on non-clickable elements | Expected interactivity | Make clickable or remove affordance |
| Rage clicks | Broken element | Fix the interaction |
| Scroll drop-off before CTA | CTA too far down | Move CTA higher |
| Ignoring a section | Irrelevant content | Remove or rewrite |
| Heavy FAQ engagement | Unanswered questions | Address earlier on page |
**Key Metrics**: CR (by source, device), Bounce rate (target <40%), Scroll depth (60%+ reaching CTA), Form start rate, Form completion rate (target 70%+).
## Step 9: A/B Test Hypotheses
**Template**: IF we [change], THEN [metric] will [increase/decrease] by [%], BECAUSE [reasoning]. PRIORITY: [High/Med/Low].
**Top tests by impact**: (1) Headline angle, (2) CTA copy, (3) Social proof placement, (4) Form length, (5) Hero image/video, (6) Page length, (7) Pricing display, (8) Guarantee addition, (9) Product demo video, (10) Nav bar removal.
## Output Format
```
CRO AUDIT REPORT
=================
Page: [URL] | Current CR: [X%] | Benchmark: [X%] | Traffic: [X/mo]
Estimated Improvement Potential: [X-X%]
CRITICAL ISSUES (Fix Immediately)
1. [Issue] -> [Fix] -> [Expected impact]
HIGH-IMPACT OPPORTUNITIES
1. [Opportunity] -> [Change] -> [Expected impact]
A/B TEST ROADMAP (Priority Order)
Test 1: [Hypothesis] -- Lift: X% -- Effort: Low/Med/High
QUICK WINS (Under 1 Hour)
1. [Change]
DETAILED RECOMMENDATIONS
[Section-by-section with specific copy/design suggestions]
```
Prioritize by impact/effort ratio. Lead with quick wins. Provide specific copy rewrites, not just general advice.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".