page-cro

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Page CRO

页面CRO

Production-grade conversion rate optimization framework for marketing pages. Covers the 7-dimension analysis framework, page-type-specific playbooks, copy alternatives methodology, above-the-fold engineering, social proof hierarchy, objection handling patterns, and structured A/B test design.

面向营销页面的生产级转化率优化框架，涵盖7维度分析框架、特定页面类型操作手册、文案备选方案方法论、首屏工程、社交证明层级、异议处理模式以及结构化A/B测试设计。

Initial Assessment

初步评估

Required Context

所需上下文

Question	Why It Matters
What page type? (homepage, landing page, pricing, feature, blog)	Determines the CRO framework to apply
What is the primary conversion goal?	Focuses the analysis
Where is traffic coming from? (organic, paid, email, social)	Drives message-match requirements
What is the current conversion rate?	Establishes the baseline
What does the post-click flow look like?	The page may convert fine but the next step fails
Do you have heatmaps or session recordings?	Behavioral data reveals what analytics cannot
What have you already tried?	Avoids re-testing failed experiments

问题	重要性
页面类型是什么？（首页、落地页、定价页、功能页、博客）	决定要应用的CRO框架
核心转化目标是什么？	明确分析重点
流量来自哪里？（自然流量、付费流量、邮件、社交平台）	决定消息匹配要求
当前转化率是多少？	建立基准线
点击后流程是什么样的？	可能页面本身转化没问题，但后续步骤存在流失
你是否有热图或会话录屏？	行为数据能揭示分析工具无法发现的问题
你已经尝试过哪些优化？	避免重复测试已经失败的实验

The 7-Dimension CRO Framework

7维度CRO框架

Analyze every marketing page across these 7 dimensions, in order of typical impact.

按照影响程度从高到低，从以下7个维度分析每个营销页面：

Dimension 1: Value Proposition Clarity (Highest Impact)

维度1：价值主张清晰度（影响最高）

The 5-second test: Can a first-time visitor understand what this is, who it is for, and why they should care within 5 seconds?

Signal	Pass	Fail
Primary benefit is stated explicitly	"Save 10 hours/week on reporting"	"Next-generation analytics platform"
Written in customer language	"See which campaigns drive revenue"	"Multi-touch attribution solution"
Differentiator is clear	"The only CRM built for agencies"	"A better CRM"
Specificity	Includes numbers, timeframes, outcomes	Vague superlatives ("powerful", "innovative")

5秒测试： 首次访问的用户能否在5秒内理解产品是什么、面向谁、以及为什么他们需要关注？

指标	通过	不通过
核心收益明确表述	"每周节省10小时报表时间"	"下一代分析平台"
使用客户易懂的语言	"查看哪些活动带来营收"	"多触点归因解决方案"
差异化优势明确	"唯一为代理机构打造的CRM"	"更好的CRM"
内容具体	包含数字、时间范围、结果	模糊的最高级形容词（"强大的"、"创新的"）

Dimension 2: Headline Effectiveness

维度2：标题有效性

Headline scoring rubric:

Criteria	Score 0	Score 1	Score 2
Communicates core value	No	Partially	Clearly
Specific (numbers, outcomes)	Generic	Somewhat specific	Very specific
Addresses target audience	Generic	Implied	Explicit
Matches traffic source	No connection	Loose match	Exact message match
Emotional or logical hook	Neither	One	Both

Total: 0-10. Score < 6 = rewrite needed.

标题评分规则：

评分标准	0分	1分	2分
传递核心价值	否	部分传递	清晰传递
内容具体（数字、结果）	通用笼统	部分具体	非常具体
对准目标受众	通用	隐含受众	明确指向受众
匹配流量来源	无关联	松散匹配	完全消息匹配
情感或逻辑钩子	都没有	有一个	两者都有

总分：0-10分。得分<6 = 需要重写。

Dimension 3: CTA Hierarchy and Placement

维度3：CTA层级与摆放位置

Check	Pass	Fail
One clear primary CTA	Single, prominent action	Multiple competing CTAs
CTA visible without scrolling	Above the fold	Below the fold only
CTA copy communicates value	"Start Free Trial"	"Submit"
CTA repeated at decision points	After benefits, after social proof, at bottom	Only at top or only at bottom
Secondary CTA is clearly secondary	Smaller, different color, text link	Same visual weight as primary

检查项	通过	不通过
一个清晰的主CTA	单一、突出的操作按钮	多个相互竞争的CTA
无需滚动即可看到CTA	位于首屏	仅位于首屏以下
CTA文案传递价值	"开启免费试用"	"提交"
在决策点重复展示CTA	在收益介绍后、社交证明后、页面底部都有	仅在顶部或仅在底部有
次CTA明确为次要层级	更小、不同颜色、文字链接形式	和主CTA视觉权重相同

Dimension 4: Visual Hierarchy and Scannability

维度4：视觉层级与易读性

Check	Pass	Fail
Most important element is most prominent	Headline + CTA dominate	Navigation or image dominates
Scannable in 10 seconds	Key points visible via headings, bold, bullets	Wall of text
Adequate white space	Breathing room between sections	Cluttered, dense layout
Images support the message	Product screenshots, relevant imagery	Stock photos, decorative graphics
F-pattern or Z-pattern layout	Content follows natural eye flow	Random placement

检查项	通过	不通过
最重要的元素最突出	标题+CTA占主导	导航或图片占主导
10秒内可快速扫读	通过标题、加粗、项目符号可看到核心要点	大段无格式文本
充足的留白	板块之间有呼吸空间	布局拥挤、密度高
图片支撑内容信息	产品截图、相关图像	库存照片、装饰性图形
F型或Z型布局	内容符合用户自然浏览动线	摆放位置随意

Dimension 5: Social Proof and Trust

维度5：社交证明与信任背书

Check	Pass	Fail
Customer logos visible	Recognizable logos above the fold	No logos or unknown companies
Testimonials are specific	"Increased revenue by 40%"	"Great product!"
Testimonials are attributed	Full name, title, company, photo	Anonymous or first-name-only
Trust badges present (where relevant)	Security, compliance, awards	No trust indicators
Numbers-based proof	"10,000+ teams use..."	No scale indicators

检查项	通过	不通过
客户logo可见	首屏有可识别的品牌logo	无logo或都是不知名公司
推荐语具体	"营收提升40%"	"产品很棒！"
推荐语有署名	全名、职位、公司、照片	匿名或仅显示名字
有相关信任徽章	安全、合规、奖项标识	无信任背书标识
基于数字的证明	"10000+团队正在使用..."	无规模指标

Dimension 6: Objection Handling

维度6：异议处理

Check	Pass	Fail
Price/value objection addressed	ROI calculation, "starts at $X"	No pricing context
"Will this work for me?" answered	Use cases, industry examples	Generic positioning only
Risk reduction offered	Free trial, guarantee, no CC required	No risk reversal
Implementation concern addressed	"Set up in 5 minutes"	No setup/complexity context
FAQ section present	Addresses top 5 objections	No FAQ or irrelevant questions

检查项	通过	不通过
解决价格/价值异议	ROI计算、"起售价为X元"	无定价相关说明
回答"这对我有用吗？"的疑问	用例、行业案例	仅通用定位描述
提供风险降低措施	免费试用、保证、无需信用卡	无风险兜底政策
解决实施顾虑	"5分钟完成设置"	无设置/复杂度相关说明
有FAQ板块	解决排名前5的异议	无FAQ或问题不相关

Dimension 7: Friction Points

维度7：摩擦点

Check	Pass	Fail
Form is optimized	Minimal fields, clear labels	Too many fields, unclear purpose
Next step is clear	Obvious path forward from every section	Confusing navigation or dead ends
Mobile experience	Fully responsive, touch-friendly	Desktop-only design
Load time	< 3 seconds	> 5 seconds
No distracting elements	Clean, focused design	Popups, auto-play video, chat widget on load

检查项	通过	不通过
表单已优化	最少字段、清晰标签	字段过多、用途不明确
下一步操作清晰	每个板块都有明确的后续路径	导航混乱或存在死链
移动端体验	完全响应式、适配触摸操作	仅适配桌面端
加载速度	<3秒	>5秒
无干扰元素	设计简洁聚焦	弹窗、自动播放视频、加载时自动弹出的聊天组件

Above-the-Fold Engineering

首屏工程

The above-the-fold area is the most valuable real estate on any page. It determines whether visitors scroll or bounce.

首屏区域是任何页面最有价值的位置，它决定了用户是继续向下滚动还是直接跳出。

Required Elements (Above the Fold)

首屏必备元素

┌──────────────────────────────────────────┐
│  [Nav: Logo + 3-5 links + Primary CTA]  │
├──────────────────────────────────────────┤
│                                          │
│  HEADLINE: Primary value proposition     │
│                                          │
│  SUBHEADLINE: Supporting detail          │
│                                          │
│  [PRIMARY CTA BUTTON]                   │
│  [Secondary CTA: text link]             │
│                                          │
│  [Social proof: logos or stat]           │
│                                          │
│  [Hero image or product screenshot]      │
│                                          │
└──────────────────────────────────────────┘

┌──────────────────────────────────────────┐
│  [Nav: Logo + 3-5 links + Primary CTA]  │
├──────────────────────────────────────────┤
│                                          │
│  HEADLINE: Primary value proposition     │
│                                          │
│  SUBHEADLINE: Supporting detail          │
│                                          │
│  [PRIMARY CTA BUTTON]                   │
│  [Secondary CTA: text link]             │
│                                          │
│  [Social proof: logos or stat]           │
│                                          │
│  [Hero image or product screenshot]      │
│                                          │
└──────────────────────────────────────────┘

Above-the-Fold Rules

首屏规则

Headline is the largest text on the page
CTA button is the most visually prominent interactive element
Social proof appears above the fold (even just logo strip)
Hero image shows the product in use (not abstract graphics)
No auto-play video or animation that distracts from the CTA
Navigation is minimal (3-5 items max, CTA in nav)

标题是页面上最大的文本
CTA按钮是视觉上最突出的交互元素
首屏展示社交证明（哪怕只是logo条）
首图展示正在使用的产品（不是抽象图形）
没有会分散CTA注意力的自动播放视频或动画
导航简洁（最多3-5个选项，导航栏包含CTA）

Social Proof Hierarchy

社交证明层级

Not all social proof is equal. Use the right type at the right location.

不是所有社交证明的效力都相同，要在正确的位置使用正确的类型。

Social Proof Power Ranking

社交证明效力排名

Rank	Type	Strength	Best Placement
1	Case study with metrics	"Company X increased revenue 40% in 3 months"	Mid-page, after benefits section
2	Named testimonial with photo	Full name, title, company, headshot	Near CTA, after objection handling
3	Aggregate numbers	"10,000+ teams" or "4.8/5 on G2"	Above the fold, near headline
4	Customer logos	Recognizable brand logos	Above the fold, logo strip
5	Awards/badges	"G2 Leader 2026", "SOC2 Certified"	Footer or near CTA
6	Generic testimonial	"Great product!" -- no specifics	Do not use (no credibility)

排名	类型	效力	最佳摆放位置
1	带数据的案例研究	"X公司3个月内营收提升40%"	页面中部，收益板块之后
2	带照片的署名推荐	全名、职位、公司、头像	CTA附近，异议处理之后
3	汇总数据	"10000+团队"或"G2评分4.8/5"	首屏，标题附近
4	客户logo	可识别的品牌logo	首屏，logo条区域
5	奖项/徽章	"2026年G2领导者"、"SOC2认证"	页脚或CTA附近
6	通用推荐	"产品很棒！" -- 无具体信息	不要使用（无可信度）

Placement Rules

摆放规则

Logo strip: Above the fold, below the CTA
Testimonials: After the section that makes the claim they validate
Case studies: Mid-page, as their own section
Numbers: Inline with headline or subheadline
Trust badges: Near the primary CTA and near the form

Logo条：首屏，CTA下方
推荐语：放在它们要验证的宣传内容对应的板块之后
案例研究：页面中部，作为独立板块
数据：直接放在标题或副标题中
信任徽章：主CTA附近和表单附近

Objection Handling Architecture

异议处理架构

The 5 Universal Objections

5个通用异议

Every product page must address these five objections. If the page does not, conversions leak.

Objection	How to Address	Page Element
"Is this worth the money?"	ROI calculator, pricing comparison, "saves X hours"	Benefits section + pricing context
"Will this work for my situation?"	Industry examples, use case sections, persona targeting	"Who uses this" section
"Is this hard to set up?"	"Set up in 5 minutes", onboarding preview, integration logos	Feature section or FAQ
"What if it doesn't work?"	Free trial, money-back guarantee, no CC required	Near CTA
"Why this over alternatives?"	Comparison table, differentiators, switcher testimonials	Mid-page or FAQ

每个产品页面都必须解决这5个异议，如果没有，就会出现转化流失。

异议	解决方式	页面元素
"这值这个价吗？"	ROI计算器、定价对比、"节省X小时"	收益板块+定价说明
"这适合我的情况吗？"	行业案例、用例板块、用户画像匹配	"谁在使用本产品"板块
"设置会不会很麻烦？"	"5分钟完成设置"、上手流程预览、集成logo	功能板块或FAQ
"如果没用怎么办？"	免费试用、退款保证、无需信用卡	CTA附近
"为什么选这个而不是其他产品？"	对比表、差异化优势、切换用户的推荐	页面中部或FAQ

FAQ Design for Objection Handling

用于异议处理的FAQ设计

The FAQ section should be the last defense before conversion. Structure it to address the 5 objections:

"How long does setup take?" (complexity objection)
"Can I cancel anytime?" (commitment objection)
"What's included in the free trial?" (value objection)
"Do you integrate with [popular tool]?" (compatibility objection)
"How is this different from [competitor]?" (alternatives objection)

FAQ板块应该是转化前的最后一道防线，按照解决5个异议的结构来设计：

"设置需要多长时间？"（复杂度异议）
"我可以随时取消吗？"（承诺异议）
"免费 trial 包含什么内容？"（价值异议）
"你们可以和[常用工具]集成吗？"（兼容性异议）
"这个产品和[竞品]有什么不同？"（替代方案异议）

Page-Type Playbooks

页面类型操作手册

Homepage

首页

Element	Best Practice
Audience	Cold visitors who may not know you
Headline	Position the company, not a single feature
CTA split	Primary: "Start Free Trial" / Secondary: "See Demo" or "Learn More"
Content	Overview of benefits, social proof, feature highlights, use cases
Navigation	Full site navigation (unlike landing pages)

元素	最佳实践
受众	可能不了解你的冷访问用户
标题	定位公司，而非单个功能
CTA拆分	主CTA："开启免费试用" / 次CTA："查看演示"或"了解更多"
内容	收益概览、社交证明、功能亮点、用例
导航	完整站点导航（和落地页不同）

Landing Page (Paid Traffic)

落地页（付费流量）

Element	Best Practice
Navigation	Remove or minimize (no escape routes)
Headline	Message-match with the ad that drove the click
CTA	Single action, repeated 2-3 times down the page
Content	Complete argument on one page: problem > solution > proof > CTA
Social proof	Directly relevant to the ad audience

元素	最佳实践
导航	移除或最小化（没有跳出路径）
标题	和带来点击的广告实现消息匹配
CTA	单一操作，页面中重复展示2-3次
内容	单页完整论证：问题>解决方案>证明>CTA
社交证明	和广告受众直接相关

Pricing Page

定价页

Element	Best Practice
Plan presentation	Good-Better-Best with recommended plan highlighted
Toggle	Annual/Monthly with savings percentage shown
Feature comparison	Full table below the fold
FAQ	"Which plan is right for me?" as first question
CTA	Per-plan CTA with plan-specific copy
Social proof	Logos and testimonials relevant to each tier

元素	最佳实践
套餐展示	好-更好-最好的结构，高亮推荐套餐
切换按钮	年付/月付切换，展示折扣比例
功能对比	首屏以下的完整对比表
FAQ	第一个问题为"哪个套餐适合我？"
CTA	每个套餐对应专属CTA和专属文案
社交证明	和每个套餐层级相关的logo和推荐语

Feature Page

功能页

Element	Best Practice
Headline	Benefit of the feature, not the feature name
Content	Use cases > technical capabilities
Demo	Screenshot, GIF, or interactive demo
CTA	"Try this feature" or "Start Free Trial"
Internal links	Link to related features and pricing

元素	最佳实践
标题	功能带来的收益，而非功能名称
内容	用例>技术能力
演示	截图、GIF或交互式演示
CTA	"试用该功能"或"开启免费试用"
内部链接	链接到相关功能和定价页

Blog Post

博客文章

Element	Best Practice
CTA type	Contextual inline CTA matching the content topic
Placement	After introduction, at natural breaks, at end
CTA style	Inline banner or text link, not aggressive popup
Content CTA	Offer a related resource (template, checklist, tool)

元素	最佳实践
CTA类型	和内容主题匹配的上下文嵌入式CTA
摆放位置	引言之后、自然停顿处、文末
CTA样式	嵌入横幅或文字链接，不要用激进的弹窗
内容CTA	提供相关资源（模板、检查清单、工具）

Copy Alternatives Methodology

文案备选方案方法论

When recommending copy changes, always provide 2-3 alternatives with reasoning.

推荐文案修改时，始终提供2-3个备选方案并说明理由。

Alternative Generation Framework

备选方案生成框架

For each key element (headline, subheadline, CTA), generate variants across these axes:

Axis	Variant A	Variant B	Variant C
Benefit focus	Outcome-focused	Problem-focused	Feature-focused
Specificity	Numbers and data	Customer quote	Use case scenario
Tone	Direct and assertive	Conversational	Aspirational

对于每个核心元素（标题、副标题、CTA），从以下维度生成变体：

维度	变体A	变体B	变体C
收益侧重	结果导向	问题导向	功能导向
具体度	数字和数据	客户引用	用例场景
语气	直接笃定	口语化	有感染力

Example

示例

Current headline: "Marketing Automation Software"

Variant	Copy	Rationale
A (outcome)	"Generate 3X More Qualified Leads Without Adding Headcount"	Specific outcome + pain point
B (problem)	"Stop Losing Leads Because Your Team Can't Follow Up Fast Enough"	Addresses the pain directly
C (social proof)	"How 2,000+ Marketing Teams Hit Their Pipeline Targets"	Authority + specificity

Recommendation: Test A first (most specific), B if A does not outperform current (different psychological angle).

当前标题： "Marketing Automation Software"

变体	文案	理由
A（结果导向）	"无需增加人力即可生成3倍更多合格线索"	具体结果+痛点
B（问题导向）	"不要再因为团队跟进不及时流失线索"	直接解决痛点
C（社交证明）	"2000+营销团队如何达成线索目标"	权威性+具体性

推荐： 先测试A（最具体），如果A没有超过当前版本就测试B（不同的心理切入点）。

Traffic Source Matching

流量源匹配

Different traffic sources require different page optimization strategies.

Source	Visitor State	Page Must Do
Paid search (brand)	Knows you, high intent	Fast path to action, minimal education
Paid search (non-brand)	Problem-aware, solution-seeking	Prove you solve their specific problem
Paid social	Interrupted, low intent	Hook attention, educate, build interest
Organic search	Research-mode	Comprehensive content, gradual conversion
Email	Already engaged	Deliver on the email promise, reduce friction
Referral	Pre-sold by referrer	Validate referrer's recommendation, fast CTA

不同的流量源需要不同的页面优化策略。

流量源	用户状态	页面需要做到
付费搜索（品牌词）	知道你的品牌，高意图	快速导向操作，最少的教育内容
付费搜索（非品牌词）	知道问题，正在找解决方案	证明你能解决他们的具体问题
付费社交	被打断，低意图	吸引注意力，教育用户，建立兴趣
自然搜索	调研状态	全面内容，渐进式转化
邮件	已经是活跃用户	兑现邮件承诺，减少摩擦
推荐流量	已经被推荐方种草	验证推荐方的推荐，快速导向CTA

Message Match Audit

消息匹配审计

For paid traffic: Compare the ad copy with the landing page headline. They must share:

The same language/terminology
The same promise
The same offer
Visual consistency (if display ad)

Mismatch = wasted ad spend. Users who click an ad about "free SEO audit" and land on a generic homepage will bounce.

对于付费流量：对比广告文案和落地页标题，它们必须共享：

相同的语言/术语
相同的承诺
相同的优惠
视觉一致性（如果是展示广告）

不匹配=浪费广告预算。 点击"免费SEO诊断"广告的用户如果跳转到通用首页会直接跳出。

A/B Test Framework

A/B测试框架

Test Priority Matrix

测试优先级矩阵

Priority	What to Test	Expected Impact
1	Headline copy	10-30% conversion lift
2	CTA copy and color	5-20% conversion lift
3	Social proof placement	5-15% conversion lift
4	Above-the-fold layout	5-20% conversion lift
5	Form field reduction	5-10% completion lift
6	Hero image vs video	2-10% lift (variable)

优先级	测试内容	预期影响
1	标题文案	10-30%的转化提升
2	CTA文案和颜色	5-20%的转化提升
3	社交证明摆放位置	5-15%的转化提升
4	首屏布局	5-20%的转化提升
5	减少表单字段	5-10%的完成率提升
6	首图vs视频	2-10%的提升（不固定）

Test Design Rules

测试设计规则

One variable per test (unless running a multivariate test with sufficient traffic)
Minimum 200 conversions per variant before declaring a winner
Run for full business cycles (minimum 2 weeks)
Track downstream metrics (not just page conversion, but lead quality / revenue)

每个测试仅改一个变量（除非有足够流量运行多变量测试）
每个变体至少获得200次转化再宣布获胜者
运行完整的业务周期（最少2周）
追踪下游指标（不仅是页面转化，还要看线索质量/营收）

Fix vs Test Decision

修复vs测试决策

Situation	Action
Obvious UX problem (broken form, missing CTA)	Fix immediately, no test needed
Missing social proof	Add it, no test needed
Headline copy alternative	A/B test
Layout change	A/B test
Removing page elements	A/B test
Adding a new section	A/B test

场景	操作
明显的UX问题（表单损坏、CTA缺失）	立即修复，无需测试
缺失社交证明	直接添加，无需测试
标题文案备选方案	A/B测试
布局改动	A/B测试
移除页面元素	A/B测试
添加新板块	A/B测试

Metrics and Benchmarks

指标与基准

Conversion Rate Benchmarks

转化率基准

Page Type	Below Average	Average	Good	Excellent
SaaS homepage	< 2%	2-4%	4-7%	> 7%
Landing page (paid)	< 5%	5-10%	10-20%	> 20%
Pricing page	< 3%	3-5%	5-10%	> 10%
Blog post (to email)	< 1%	1-3%	3-5%	> 5%
Feature page	< 2%	2-5%	5-8%	> 8%

页面类型	低于平均	平均	良好	优秀
SaaS首页	< 2%	2-4%	4-7%	> 7%
落地页（付费）	< 5%	5-10%	10-20%	> 20%
定价页	< 3%	3-5%	5-10%	> 10%
博客文章（转邮件）	< 1%	1-3%	3-5%	> 5%
功能页	< 2%	2-5%	5-8%	> 8%

Key Metrics

核心指标

Metric	What It Tells You
Bounce rate	Is the page meeting visitor expectations?
Scroll depth	How much of the page are visitors seeing?
Time on page	Are visitors reading or immediately leaving?
CTA click rate	Is the CTA compelling and visible?
Form start rate	Are visitors beginning the conversion process?
Form completion rate	Are they finishing it?

指标	反映的问题
跳出率	页面是否符合用户预期？
滚动深度	用户看到了多少页面内容？
页面停留时间	用户是在阅读还是直接离开？
CTA点击率	CTA是否有吸引力、是否可见？
表单开始率	用户是否开始转化流程？
表单完成率	用户是否完成了转化流程？

Output Artifacts

输出产物

Artifact	Format	Description
CRO Audit Report	7-dimension analysis	Per-dimension assessment with severity ratings
Quick Wins List	Bullet list (max 5)	Implementable today with expected impact
High-Impact Recommendations	Structured list	Each with rationale, effort estimate, and success metric
Copy Alternatives	Side-by-side table	2-3 variants per key element with reasoning
A/B Test Plan	Prioritized table	Hypothesis, variant, success metric, priority
Traffic Source Matching Audit	Source x page element table	Message match assessment per traffic source

产物	格式	描述
CRO审计报告	7维度分析	每个维度的评估和严重程度评级
快速优化项列表	项目符号列表（最多5项）	可立即落地的优化项和预期影响
高影响建议	结构化列表	每个建议包含理由、工作量预估和成功指标
文案备选方案	对比表格	每个核心元素2-3个变体和对应理由
A/B测试计划	优先级表格	假设、变体、成功指标、优先级
流量源匹配审计	流量源x页面元素表格	每个流量源的消息匹配评估

Related Skills

Tool Reference

工具参考

1. page_cro_scorer.py

Purpose: Score a marketing page across the 7 CRO dimensions and generate an audit report with severity ratings.

bash

python scripts/page_cro_scorer.py page_audit.json
python scripts/page_cro_scorer.py page_audit.json --json

Flag	Required	Description
`page_audit.json`	Yes	JSON file with page elements and dimension checks
`--json`	No	Output results as JSON

用途： 从7个CRO维度给营销页面打分，生成带严重程度评级的审计报告。

bash

python scripts/page_cro_scorer.py page_audit.json
python scripts/page_cro_scorer.py page_audit.json --json

标志	必填	描述
`page_audit.json`	是	包含页面元素和维度检查项的JSON文件
`--json`	否	以JSON格式输出结果

2. headline_scorer.py

Purpose: Score headline effectiveness against the 5-criteria rubric and generate copy alternatives.

bash

python scripts/headline_scorer.py --headline "Marketing Automation Software" --audience "B2B marketers" --traffic-source paid-search
python scripts/headline_scorer.py --headline "Marketing Automation Software" --json

Flag	Required	Description
`--headline`	Yes	The headline text to score
`--audience`	No	Target audience description (default: "general")
`--traffic-source`	No	Primary traffic source: organic, paid-search, paid-social, email, referral (default: organic)
`--json`	No	Output results as JSON

用途： 按照5项评分规则给标题有效性打分，生成文案备选方案。

bash

python scripts/headline_scorer.py --headline "Marketing Automation Software" --audience "B2B marketers" --traffic-source paid-search
python scripts/headline_scorer.py --headline "Marketing Automation Software" --json

标志	必填	描述
`--headline`	是	要打分的标题文本
`--audience`	否	目标受众描述（默认："general"）
`--traffic-source`	否	核心流量源：organic, paid-search, paid-social, email, referral（默认：organic）
`--json`	否	以JSON格式输出结果

3. conversion_benchmark_calculator.py

Purpose: Calculate conversion rate benchmarks for a given page type, traffic source, and industry, and assess current performance.

bash

python scripts/conversion_benchmark_calculator.py --page-type landing-page --traffic paid --current-rate 8.5
python scripts/conversion_benchmark_calculator.py --page-type homepage --traffic organic --current-rate 3.0 --json

Flag	Required	Description
`--page-type`	Yes	Page type: homepage, landing-page, pricing, feature, blog
`--traffic`	Yes	Traffic source: organic, paid, email, social, referral
`--current-rate`	Yes	Current conversion rate as percentage
`--industry`	No	Industry for benchmarks: saas, ecommerce, fintech, healthcare, education (default: saas)
`--json`	No	Output results as JSON

用途： 计算给定页面类型、流量源和行业的转化率基准，评估当前表现。

bash

python scripts/conversion_benchmark_calculator.py --page-type landing-page --traffic paid --current-rate 8.5
python scripts/conversion_benchmark_calculator.py --page-type homepage --traffic organic --current-rate 3.0 --json

标志	必填	描述
`--page-type`	是	页面类型：homepage, landing-page, pricing, feature, blog
`--traffic`	是	流量源：organic, paid, email, social, referral
`--current-rate`	是	当前转化率，百分比形式
`--industry`	否	基准对应的行业：saas, ecommerce, fintech, healthcare, education（默认：saas）
`--json`	否	以JSON格式输出结果

Troubleshooting

问题排查

Problem	Likely Cause	Solution
High bounce rate (>70%) on landing page	Message mismatch with traffic source or poor above-the-fold	Audit message match: compare ad copy with landing page headline; ensure value proposition is visible in first 5 seconds
Page converts on desktop but not mobile	Mobile UX not optimized	Check touch targets (44px+), form field count on mobile, CTA visibility without scrolling; score with page_cro_scorer.py
CTA click rate below 2%	CTA is generic, below the fold, or visually weak	Replace "Submit" with value-specific copy; ensure CTA is visible above fold and repeated after key sections
High scroll depth but low conversion	Visitors read but are not convinced to act	Add social proof near CTA positions; address objections in FAQ; add risk reversal (free trial, no CC)
A/B test shows no significant winner after 4 weeks	Change too small to detect or insufficient traffic	Use ab_test_calculator.py from form-cro to validate sample size; test bigger changes (headline rewrite vs word swap)
Paid traffic converts worse than organic	Landing page not tailored to paid traffic intent	Create dedicated landing pages for paid campaigns with message match; remove navigation on paid landing pages
Social proof section is ignored	Generic testimonials or poor placement	Use specific, attributed testimonials with metrics; place after the section that makes the claim they validate

问题	可能原因	解决方案
落地页跳出率高（>70%）	和流量源消息不匹配，或首屏表现差	审计消息匹配：对比广告文案和落地页标题；确保价值主张在5秒内可见
页面在桌面端转化正常但移动端不转化	移动端UX未优化	检查触摸目标大小（44px+）、移动端表单字段数量、无需滚动即可看到CTA；使用page_cro_scorer.py打分
CTA点击率低于2%	CTA太通用、在首屏以下、或者视觉上不突出	把"提交"替换为和价值相关的文案；确保CTA在首屏可见，并且在核心板块之后重复展示
滚动深度高但转化率低	用户阅读了内容但没有被说服行动	在CTA位置附近添加社交证明；在FAQ中解决异议；添加风险兜底措施（免费试用、无需信用卡）
A/B测试运行4周后没有明显的获胜者	改动太小无法检测，或者流量不足	使用form-cro中的ab_test_calculator.py验证样本量；测试更大的改动（重写标题vs修改个别词）
付费流量转化比自然流量差	落地页没有适配付费流量的意图	为付费活动创建专属落地页，实现消息匹配；移除付费落地页的导航
社交证明板块被忽略	推荐语太通用，或者摆放位置不好	使用带数据的、有署名的推荐语；放在它们要验证的宣传内容对应的板块之后

Success Criteria

成功标准

Page CRO score of 70+ across the 7-dimension framework (scored by page_cro_scorer.py)
Headline scores 7+ on the 10-point rubric (scored by headline_scorer.py)
Conversion rate at or above industry benchmark for page type (verified by conversion_benchmark_calculator.py)
Above-the-fold contains: headline, CTA, and at least one social proof element
Message match verified for all paid traffic campaigns (ad copy matches landing page headline)
Mobile conversion rate within 20% of desktop rate
Every page addresses at least 3 of the 5 universal objections

7维度框架下的页面CRO得分70+（由page_cro_scorer.py打分）
标题在10分制评分中得分7+（由headline_scorer.py打分）
转化率达到或超过对应页面类型的行业基准（由conversion_benchmark_calculator.py验证）
首屏包含：标题、CTA、至少一个社交证明元素
所有付费流量活动都验证了消息匹配（广告文案和落地页标题匹配）
移动端转化率在桌面端转化率的20%误差范围内
每个页面至少解决5个通用异议中的3个

Scope & Limitations

范围与限制

In scope: Page-level conversion optimization, headline effectiveness, CTA hierarchy, social proof placement, objection handling, traffic source matching, A/B test prioritization
Out of scope: Form optimization (use form-cro), signup flow optimization (use signup-flow-cro), popup optimization (use popup-cro), pricing structure changes (use pricing-strategy)
Page speed: This skill covers CRO elements, not technical performance; pages loading >3 seconds need technical optimization first
Traffic minimum: A/B testing recommendations require 200+ conversions per variant; low-traffic pages should implement best practices without testing
Qualitative input: Heatmaps and session recordings provide critical behavioral data that analytics alone cannot reveal; consider investing in these tools

覆盖范围： 页面级转化率优化、标题有效性、CTA层级、社交证明摆放、异议处理、流量源匹配、A/B测试优先级
不覆盖范围： 表单优化（使用form-cro）、注册流程优化（使用signup-flow-cro）、弹窗优化（使用popup-cro）、定价结构改动（使用pricing-strategy）
页面速度： 本技能覆盖CRO元素，不涉及技术性能；加载时间>3秒的页面需要先做技术优化
最低流量要求： A/B测试建议要求每个变体至少200次转化；低流量页面应该直接落地最佳实践，无需测试
定性输入： 热图和会话录屏能提供仅靠分析工具无法获得的关键行为数据；考虑采购这些工具

Integration Points

集成点

form-cro -- When the form on the page is the bottleneck (field optimization, validation UX, mobile form experience)
signup-flow-cro -- When users convert on the page but drop off during the signup/registration process
popup-cro -- When considering a popup as an additional conversion layer on top of the page
onboarding-cro -- When post-conversion activation is the real problem and the page itself converts adequately
pricing-strategy -- When the pricing page needs structural redesign (tier structure, value metric), not just CRO tweaks
competitive-teardown -- When comparison pages need competitive data to build credible content

form-cro -- 当页面上的表单是瓶颈时使用（字段优化、校验UX、移动端表单体验）
signup-flow-cro -- 当用户在页面完成转化但在注册流程中流失时使用
popup-cro -- 当考虑添加弹窗作为页面上的额外转化层时使用
onboarding-cro -- 当转化后的激活是核心问题、页面本身转化良好时使用
pricing-strategy -- 当定价页需要结构重构（套餐结构、价值指标）、而不仅是CRO微调时使用
competitive-teardown -- 当对比页需要竞品数据来打造可信内容时使用

page-cro

Original

Translation

Page CRO

页面CRO

Table of Contents

目录

Initial Assessment

初步评估

Required Context

所需上下文

The 7-Dimension CRO Framework

7维度CRO框架

Dimension 1: Value Proposition Clarity (Highest Impact)

维度1：价值主张清晰度（影响最高）

Dimension 2: Headline Effectiveness

维度2：标题有效性

Dimension 3: CTA Hierarchy and Placement

维度3：CTA层级与摆放位置

Dimension 4: Visual Hierarchy and Scannability

维度4：视觉层级与易读性

Dimension 5: Social Proof and Trust

维度5：社交证明与信任背书

Dimension 6: Objection Handling

维度6：异议处理

Dimension 7: Friction Points

维度7：摩擦点

Above-the-Fold Engineering

首屏工程

Required Elements (Above the Fold)

首屏必备元素

Above-the-Fold Rules

首屏规则

Social Proof Hierarchy

社交证明层级

Social Proof Power Ranking

社交证明效力排名

Placement Rules

摆放规则

Objection Handling Architecture

异议处理架构

The 5 Universal Objections

5个通用异议

FAQ Design for Objection Handling

用于异议处理的FAQ设计

Page-Type Playbooks

页面类型操作手册

Homepage

首页

Landing Page (Paid Traffic)

落地页（付费流量）

Pricing Page

定价页

Feature Page

功能页

Blog Post

博客文章

Copy Alternatives Methodology

文案备选方案方法论

Alternative Generation Framework

备选方案生成框架

Example

示例

Traffic Source Matching

流量源匹配

Message Match Audit

消息匹配审计

A/B Test Framework

A/B测试框架

Test Priority Matrix

测试优先级矩阵

Test Design Rules

测试设计规则

Fix vs Test Decision

修复vs测试决策

Metrics and Benchmarks

指标与基准

Conversion Rate Benchmarks

转化率基准

Key Metrics