skills/strategies/launch/conversion/SKILL.md
When the user wants to improve conversion rates, run A/B tests, optimize funnels, or reduce friction. Also use when the user mentions "CRO," "conversion rate optimization," "A/B test," "split test," "funnel optimization," "checkout optimization," "form optimization," or "conversion funnel." For pricing psychology, use pricing-strategy.
npx skillsauth add kostja94/marketing-skills conversion-optimizationInstall 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.
Guides conversion rate optimization (CRO): increasing the percentage of visitors who complete desired actions. Higher conversion rates mean increased revenue, reduced CAC, and better ROI. Use this skill when optimizing funnels, running experiments, or reducing friction on high-traffic pages.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read Sections 4 (Audience), 5 (Website), 6 (Keywords).
Identify:
| Step | Action | |------|--------| | 1. Research | Map funnel; identify high-traffic, low-conversion pages | | 2. Hypothesize | Form testable hypothesis (if X, then Y because Z) | | 3. Prioritize | Score by Potential, Importance, Ease (PIE) | | 4. Test | A/B or multivariate; adequate sample size | | 5. Analyze | Statistical significance; implement winner |
Score each test idea 1–10:
| Factor | Question | |--------|----------| | Potential | How much improvement is possible? | | Importance | How much traffic does this page get? | | Ease | How easy to implement? |
Rank backlog by total score; run highest-impact tests first.
| Practice | Guideline | |----------|-----------| | Sample size | Calculate minimum before launch; 95% significance without adequate sample = false positives | | Duration | Run full week cycles; account for day-of-week effects | | One variable | Test one element per experiment (or use MVT for multiple) | | Mobile separate | Mobile converts ~50% of desktop; test mobile independently—thumb reach, form complexity differ | | Low traffic | Use Bayesian testing for faster, actionable results |
| Page Type | Test Ideas | |-----------|------------| | Homepage | Search bar prominence; personalized content; hero CTA; social proof placement | | Landing page | Headline; form length; CTA copy; above-fold layout | | Product/Category | Quick view; descriptions; add-to-cart placement | | Checkout | Form fields; progress indicator; trust badges; guest checkout | | Pricing | Plan order; anchoring; CTA per tier |
Personalization: Personalized experiences generate ~41% more impact than generic ones.
| Module | Purpose | |--------|---------| | Data & BI | Data warehouse; user behavior events; agile surveys | | A/B testing | Experiment platform; statistical significance; backend-controlled variants | | User education | Help docs (multi-language); update notifications; EDM | | Attribution | Ad pixels; attribution model; impression-to-click-to-sale tracking |
Avoid: Intrusive interstitials; popups that block content. Prefer non-intrusive ad formats.
data-ai
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.
testing
When the user wants to add or optimize Open Graph metadata for social sharing. Also use when the user mentions "Open Graph," "og:tags," "og:title," "og:image," "og:description," "Facebook preview," "LinkedIn preview," or "social share preview." For X (Twitter) link previews, use twitter-cards. For SERP title/description, use title-tag and meta-description.
tools
When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page." For legal overview page, use legal-page-generator.
development
When the user wants to create or optimize a shipping or delivery information page. Also use when the user mentions "shipping," "delivery," "shipping policy," "delivery times," "shipping page," "free shipping," "shipping rates," "delivery options," "shipping info," "cross-border shipping," "international delivery," or "order tracking." For legal overview, use legal-page-generator.