conversion-optimization

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Strategies: Conversion Optimization

策略:转化优化

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.
指导转化率优化(CRO):提升完成预期行动的访客占比。更高的转化率意味着营收增加、客户获取成本(CAC)降低、投资回报率(ROI)提升。当你需要优化转化漏斗、运行实验或降低高流量页面的流程阻力时,可以使用本技能。
调用规则:首次调用时,如果合适,可以先用1-2句话介绍本技能覆盖的范围和价值,再输出核心内容。如果是后续调用或者用户要求跳过介绍,直接输出核心内容即可。

Initial Assessment

初步评估

Check for product marketing context first: If
.claude/product-marketing-context.md
or
.cursor/product-marketing-context.md
exists, read Sections 4 (Audience), 5 (Website), 6 (Keywords).
Identify:
  1. Funnel stage: Awareness, consideration, decision, post-purchase
  2. Conversion goal: Signup, purchase, download, demo request
  3. Traffic: Volume; mobile vs desktop split
  4. Current conversion rate: Baseline for improvement
首先确认产品营销上下文:如果存在
.claude/product-marketing-context.md
.cursor/product-marketing-context.md
文件,请阅读第4节(受众)、第5节(网站)、第6节(关键词)。
需要明确以下信息:
  1. 漏斗阶段:认知、考虑、决策、购后
  2. 转化目标:注册、购买、下载、申请演示
  3. 流量情况:量级;移动端/桌面端占比
  4. 当前转化率:作为优化的基准线

CRO Process

CRO流程

StepAction
1. ResearchMap funnel; identify high-traffic, low-conversion pages
2. HypothesizeForm testable hypothesis (if X, then Y because Z)
3. PrioritizeScore by Potential, Importance, Ease (PIE)
4. TestA/B or multivariate; adequate sample size
5. AnalyzeStatistical significance; implement winner
步骤动作
1. 调研梳理转化漏斗;定位高流量、低转化率页面
2. 提出假设形成可测试的假设(如果做X,就会达成Y,原因是Z)
3. 优先级排序按照潜力(Potential)、重要性(Importance)、易实施性(Ease)(即PIE框架)打分
4. 测试开展A/B测试或多变量测试;保证足够的样本量
5. 分析验证统计显著性;落地效果更优的方案

PIE Prioritization Framework

PIE优先级框架

Score each test idea 1–10:
FactorQuestion
PotentialHow much improvement is possible?
ImportanceHow much traffic does this page get?
EaseHow easy to implement?
Rank backlog by total score; run highest-impact tests first.
每个测试想法按1-10分打分:
评估维度评估问题
潜力可实现的提升幅度有多大?
重要性该页面的流量量级是多少?
易实施性落地的难度有多低?
按总分对待办项排序,优先运行影响最高的测试。

A/B Testing Best Practices

A/B测试最佳实践

PracticeGuideline
Sample sizeCalculate minimum before launch; 95% significance without adequate sample = false positives
DurationRun full week cycles; account for day-of-week effects
One variableTest one element per experiment (or use MVT for multiple)
Mobile separateMobile converts ~50% of desktop; test mobile independently—thumb reach, form complexity differ
Low trafficUse Bayesian testing for faster, actionable results
实践规范
样本量启动前计算最小样本量;没有足够样本支撑的95%显著性=假阳性
测试时长运行完整的周周期;考虑工作日/周末的效果差异
单一变量每次实验仅测试一个元素(如需测试多个可使用多变量测试MVT)
移动端单独测试移动端转化率约为桌面端的50%;需要独立测试移动端——拇指可触范围、表单复杂度都和桌面端有差异
低流量场景使用贝叶斯测试获取更快、可落地的结果

Key Testing Areas

核心测试领域

Page TypeTest Ideas
HomepageSearch bar prominence; personalized content; hero CTA; social proof placement
Landing pageHeadline; form length; CTA copy; above-fold layout
Product/CategoryQuick view; descriptions; add-to-cart placement
CheckoutForm fields; progress indicator; trust badges; guest checkout
PricingPlan order; anchoring; CTA per tier
Personalization: Personalized experiences generate ~41% more impact than generic ones.
页面类型测试方向
首页搜索栏显眼程度;个性化内容;首屏CTA;社交证明摆放位置
落地页标题;表单长度;CTA文案;首屏布局
产品/分类页快速预览功能;产品描述;加购按钮位置
结账页表单项;进度指示器;信任徽章;游客结账选项
定价页套餐排序;价格锚点;每个套餐对应的CTA
个性化:个性化体验的效果比通用体验高约41%。

Commercialization Infrastructure

商业化基建

ModulePurpose
Data & BIData warehouse; user behavior events; agile surveys
A/B testingExperiment platform; statistical significance; backend-controlled variants
User educationHelp docs (multi-language); update notifications; EDM
AttributionAd pixels; attribution model; impression-to-click-to-sale tracking
Avoid: Intrusive interstitials; popups that block content. Prefer non-intrusive ad formats.
模块用途
数据与BI数据仓库;用户行为事件;敏捷调研
A/B测试实验平台;统计显著性计算;后端控制的变量版本
用户教育帮助文档(多语言);更新通知;营销邮件(EDM)
归因广告像素;归因模型;曝光-点击-销售全链路追踪
注意规避:侵入式插屏;遮挡内容的弹窗。优先使用非侵入式的广告格式。

Foundational Requirements

基础要求

  • Analytics: Map funnels; identify drop-off points (analytics-tracking, traffic-analysis)
  • Qualitative: Heatmaps, session recordings, user tests—understand why drop-off occurs
  • Technical: Dedicated resources for 2–4 tests/month; maintain momentum
  • 数据分析:梳理转化漏斗;定位流失点(analytics-tracking、traffic-analysis)
  • 定性研究:热力图、会话录制、用户测试——理解用户流失的原因
  • 技术支持:预留每月可落地2-4个测试的专属资源;保持优化节奏

Output Format

输出格式

  • Funnel map (stages, conversion rates, drop-off)
  • Hypothesis (if X, then Y because Z)
  • Test plan (variant, metric, sample size, duration)
  • Implementation checklist
  • 转化漏斗地图(阶段、转化率、流失率)
  • 假设(如果做X,就会达成Y,原因是Z)
  • 测试方案(变量版本、观测指标、样本量、测试时长)
  • 落地checklist

Related Skills

相关技能

  • landing-page-generator: Landing page structure and copy
  • cta-generator: CTA design and placement
  • analytics-tracking: GA4, events, conversion tracking
  • traffic-analysis: Attribution, funnel analysis
  • copywriting: Headline, CTA copy for tests
  • landing-page-generator:落地页结构与文案
  • cta-generator:CTA设计与摆放
  • analytics-tracking:GA4、事件、转化追踪
  • traffic-analysis:归因、漏斗分析
  • copywriting:测试用的标题、CTA文案