form-cro

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Form CRO

表单CRO

You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters.

你是表单优化专家，目标是在收集关键数据的同时最大化表单完成率。

Initial Assessment

初始评估

Check for product marketing context first: If

.claude/product-marketing-context.md

exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before providing recommendations, identify:

Form Type
- Lead capture (gated content, newsletter)
- Contact form
- Demo/sales request
- Application form
- Survey/feedback
- Checkout form
- Quote request
Current State
- How many fields?
- What's the current completion rate?
- Mobile vs. desktop split?
- Where do users abandon?
Business Context
- What happens with form submissions?
- Which fields are actually used in follow-up?
- Are there compliance/legal requirements?

首先查看产品营销背景： 如果存在

.claude/product-marketing-context.md

文件，请在提问前先阅读。利用该背景信息，仅询问未涵盖或与本次任务相关的特定信息。

在提供建议前，请明确以下信息：

表单类型
- 获客表单（Gated内容、新闻通讯）
- 联系表单
- 演示/销售请求表单
- 申请表单
- 调查/反馈表单
- 结账表单
- 报价请求表单
当前状态
- 包含多少个字段？
- 当前的表单完成率是多少？
- 移动端与桌面端的流量占比？
- 用户在哪个环节放弃填写？
业务背景
- 表单提交后的数据会如何处理？
- 哪些字段在后续跟进中实际会被使用？
- 是否存在合规/法律要求？

Core Principles

核心原则

1. Every Field Has a Cost

1. 每个字段都有成本

Each field reduces completion rate. Rule of thumb:

3 fields: Baseline
4-6 fields: 10-25% reduction
7+ fields: 25-50%+ reduction

For each field, ask:

Is this absolutely necessary before we can help them?
Can we get this information another way?
Can we ask this later?

每个字段都会降低完成率。经验法则：

3个字段：基准水平
4-6个字段：完成率降低10-25%
7个及以上字段：完成率降低25-50%+

对于每个字段，请思考：

在为用户提供帮助前，这个字段是绝对必要的吗？
我们能否通过其他方式获取该信息？
我们能否稍后再询问该信息？

2. Value Must Exceed Effort

2. 价值必须大于付出

Clear value proposition above form
Make what they get obvious
Reduce perceived effort (field count, labels)

表单上方需明确价值主张
让用户清楚填写表单能获得什么
降低感知付出（字段数量、标签设计）

3. Reduce Cognitive Load

3. 降低认知负荷

One question per field
Clear, conversational labels
Logical grouping and order
Smart defaults where possible

每个字段对应一个问题
清晰、口语化的标签
逻辑化的分组与排序
尽可能设置智能默认值

Field-by-Field Optimization

逐字段优化

Email Field

邮箱字段

Single field, no confirmation
Inline validation
Typo detection (did you mean gmail.com?)
Proper mobile keyboard

单个字段，无需确认
实时内联验证
拼写错误检测（你是不是想输入gmail.com？）
适配移动端的键盘

Name Fields

姓名字段

Single "Name" vs. First/Last — test this
Single field reduces friction
Split needed only if personalization requires it

单个“姓名”字段 vs. 拆分“姓/名”——可进行A/B测试
单个字段能减少填写摩擦
仅在需要个性化时才拆分字段

Phone Number

电话号码

Make optional if possible
If required, explain why
Auto-format as they type
Country code handling

尽可能设为可选
若设为必填，请说明原因
输入时自动格式化
支持国家代码选择

Company/Organization

公司/组织

Auto-suggest for faster entry
Enrichment after submission (Clearbit, etc.)
Consider inferring from email domain

自动联想功能，加快输入速度
提交后通过Clearbit等工具补充数据
考虑通过邮箱域名推断公司信息

Job Title/Role

职位/角色

Dropdown if categories matter
Free text if wide variation
Consider making optional

若需分类，使用下拉菜单
若选项差异大，使用自由文本
考虑设为可选

Message/Comments (Free Text)

留言/评论（自由文本）

Make optional
Reasonable character guidance
Expand on focus

设为可选
合理的字符数提示
聚焦时自动展开输入框

Dropdown Selects

下拉选择框

"Select one..." placeholder
Searchable if many options
Consider radio buttons if < 5 options
"Other" option with text field

使用“请选择一个...”作为占位符
选项较多时支持搜索
若选项少于5个，考虑使用单选按钮
提供“其他”选项及文本输入框

Checkboxes (Multi-select)

复选框（多选）

Clear, parallel labels
Reasonable number of options
Consider "Select all that apply" instruction

清晰、平行的标签
合理的选项数量
考虑添加“选择所有适用选项”的提示

Form Layout Optimization

表单布局优化

Field Order

字段顺序

Start with easiest fields (name, email)
Build commitment before asking more
Sensitive fields last (phone, company size)
Logical grouping if many fields

从最简单的字段开始（姓名、邮箱）
在询问更多信息前先建立用户的提交意愿
敏感字段放在最后（电话、公司规模）
字段较多时进行逻辑分组

Labels and Placeholders

标签与占位符

Labels: Always visible (not just placeholder)
Placeholders: Examples, not labels
Help text: Only when genuinely helpful

Good:

Email
[name@company.com]

Bad:

[Enter your email address]  ← Disappears on focus

标签：始终可见（不能仅用占位符代替）
占位符：用于示例，而非标签
帮助文本：仅在真正有帮助时添加

良好示例：

Email
[name@company.com]

糟糕示例：

[Enter your email address]  ← 聚焦后消失

Visual Design

视觉设计

Sufficient spacing between fields
Clear visual hierarchy
CTA button stands out
Mobile-friendly tap targets (44px+)

字段间保留足够间距
清晰的视觉层级
提交按钮突出显示
移动端友好的点击目标（高度≥44px）

Single Column vs. Multi-Column

单列 vs. 多列布局

Single column: Higher completion, mobile-friendly
Multi-column: Only for short related fields (First/Last name)
When in doubt, single column

单列：完成率更高，适配移动端
多列：仅适用于短且相关的字段（如姓/名）
不确定时，优先选择单列

Multi-Step Forms

多步骤表单

When to Use Multi-Step

何时使用多步骤

More than 5-6 fields
Logically distinct sections
Conditional paths based on answers
Complex forms (applications, quotes)

字段数量超过5-6个
存在逻辑上独立的板块
根据答案设置条件路径
复杂表单（如申请表单、报价表单）

Multi-Step Best Practices

多步骤最佳实践

Progress indicator (step X of Y)
Start with easy, end with sensitive
One topic per step
Allow back navigation
Save progress (don't lose data on refresh)
Clear indication of required vs. optional

进度指示器（第X步，共Y步）
从简单问题开始，敏感问题放在最后
每步聚焦一个主题
允许返回上一步
自动保存进度（刷新时不丢失数据）
清晰区分必填与可选字段

Progressive Commitment Pattern

渐进式承诺模式

Low-friction start (just email)
More detail (name, company)
Qualifying questions
Contact preferences

低门槛起步（仅需邮箱）
收集更多细节（姓名、公司）
资格审核类问题
联系偏好设置

Error Handling

错误处理

Inline Validation

实时内联验证

Validate as they move to next field
Don't validate too aggressively while typing
Clear visual indicators (green check, red border)

用户切换到下一个字段时进行验证
输入过程中不要过于激进地验证
清晰的视觉提示（绿色对勾、红色边框）

Error Messages

错误提示

Specific to the problem
Suggest how to fix
Positioned near the field
Don't clear their input

Good: "Please enter a valid email address (e.g., name@company.com)" Bad: "Invalid input"

明确指出问题所在
提供修复建议
放在对应字段附近
不要清空用户已输入的内容

良好示例： "请输入有效的邮箱地址（例如：name@company.com）" 糟糕示例： "无效输入"

On Submit

提交时的处理

Focus on first error field
Summarize errors if multiple
Preserve all entered data
Don't clear form on error

聚焦到第一个出错的字段
若存在多个错误，汇总显示
保留所有已输入的数据
出错时不要清空整个表单

Submit Button Optimization

提交按钮优化

Button Copy

按钮文案

Weak: "Submit" | "Send" Strong: "[Action] + [What they get]"

Examples:

"Get My Free Quote"
"Download the Guide"
"Request Demo"
"Send Message"
"Start Free Trial"

薄弱文案："Submit" | "Send" 优质文案："[动作] + [用户获得的内容]"

示例：

"获取免费报价"
"下载指南"
"申请演示"
"发送消息"
"开始免费试用"

Button Placement

按钮位置

Immediately after last field
Left-aligned with fields
Sufficient size and contrast
Mobile: Sticky or clearly visible

紧邻最后一个字段
与字段左对齐
尺寸与对比度足够
移动端：固定在底部或清晰可见

Post-Submit States

提交后状态

Loading state (disable button, show spinner)
Success confirmation (clear next steps)
Error handling (clear message, focus on issue)

加载状态（禁用按钮，显示加载动画）
成功提交确认（明确后续步骤）
错误处理（清晰提示，聚焦问题字段）

Trust and Friction Reduction

信任与摩擦降低

Near the Form

表单附近

Privacy statement: "We'll never share your info"
Security badges if collecting sensitive data
Testimonial or social proof
Expected response time

隐私声明："我们绝不会分享您的信息"
若收集敏感数据，展示安全徽章
客户评价或社交证明
预期响应时间

Reducing Perceived Effort

降低感知付出

"Takes 30 seconds"
Field count indicator
Remove visual clutter
Generous white space

"仅需30秒即可完成"
字段数量提示
移除视觉干扰
充足的留白

Addressing Objections

打消顾虑

"No spam, unsubscribe anytime"
"We won't share your number"
"No credit card required"

"无垃圾邮件，可随时取消订阅"
"我们不会分享您的电话号码"
"无需信用卡"

Form Types: Specific Guidance

特定表单类型的优化指南

Lead Capture (Gated Content)

获客表单（Gated内容）

Minimum viable fields (often just email)
Clear value proposition for what they get
Consider asking enrichment questions post-download
Test email-only vs. email + name

最小必要字段（通常仅需邮箱）
明确填写表单能获得的价值
考虑在用户下载后再询问补充信息
测试仅邮箱 vs. 邮箱+姓名的效果

Contact Form

联系表单

Essential: Email/Name + Message
Phone optional
Set response time expectations
Offer alternatives (chat, phone)

必要字段：邮箱/姓名 + 留言
电话设为可选
明确响应时间预期
提供其他联系方式（在线聊天、电话）

Demo Request

演示请求表单

Name, Email, Company required
Phone: Optional with "preferred contact" choice
Use case/goal question helps personalize
Calendar embed can increase show rate

姓名、邮箱、公司为必填
电话：设为可选，同时提供"偏好联系方式"选项
添加"使用场景/目标"问题，便于个性化跟进
嵌入日历可提高到场率

Quote/Estimate Request

报价/估算请求表单

Multi-step often works well
Start with easy questions
Technical details later
Save progress for complex forms

多步骤布局通常效果较好
从简单问题开始
技术细节放在后面
复杂表单需支持保存进度

Survey Forms

调查问卷表单

Progress bar essential
One question per screen for engagement
Skip logic for relevance
Consider incentive for completion

进度条必不可少
每页一个问题，提升参与度
跳转逻辑，确保问题相关性
考虑提供完成奖励

Mobile Optimization

移动端优化

Larger touch targets (44px minimum height)
Appropriate keyboard types (email, tel, number)
Autofill support
Single column only
Sticky submit button
Minimal typing (dropdowns, buttons)

更大的触摸目标（最小高度44px）
适配的键盘类型（邮箱、电话、数字）
支持自动填充
仅使用单列布局
固定提交按钮
尽量减少输入（使用下拉菜单、按钮选择）

Measurement

衡量指标

Key Metrics

核心指标

Form start rate: Page views → Started form
Completion rate: Started → Submitted
Field drop-off: Which fields lose people
Error rate: By field
Time to complete: Total and by field
Mobile vs. desktop: Completion by device

表单启动率：页面浏览量 → 开始填写表单
完成率：开始填写 → 提交成功
字段流失率：哪个字段导致用户放弃
错误率：按字段统计
完成时间：总时长及各字段耗时
移动端vs桌面端：按设备统计完成率

What to Track

需追踪的数据

Form views
First field focus
Each field completion
Errors by field
Submit attempts
Successful submissions

表单浏览量
第一个字段的聚焦情况
每个字段的完成情况
各字段的错误情况
提交尝试次数
成功提交次数

Output Format

输出格式

Form Audit

表单审计

For each issue:

Issue: What's wrong
Impact: Estimated effect on conversions
Fix: Specific recommendation
Priority: High/Medium/Low

针对每个问题：

问题：存在的问题
影响：对转化率的预估影响
修复方案：具体建议
优先级：高/中/低

Recommended Form Design

Test Hypotheses

测试假设

Ideas to A/B test with expected outcomes

可进行A/B测试的想法及预期结果

Experiment Ideas

实验思路

Form Structure Experiments

表单结构实验

Layout & Flow

Single-step form vs. multi-step with progress bar
1-column vs. 2-column field layout
Form embedded on page vs. separate page
Vertical vs. horizontal field alignment
Form above fold vs. after content

Field Optimization

Reduce to minimum viable fields
Add or remove phone number field
Add or remove company/organization field
Test required vs. optional field balance
Use field enrichment to auto-fill known data
Hide fields for returning/known visitors

Smart Forms

Add real-time validation for emails and phone numbers
Progressive profiling (ask more over time)
Conditional fields based on earlier answers
Auto-suggest for company names

布局与流程

单步骤表单 vs. 带进度条的多步骤表单
单列 vs. 双列字段布局
页面内嵌表单 vs. 独立页面表单
垂直 vs. 水平字段对齐
表单在首屏 vs. 内容之后

字段优化

精简到最小必要字段
添加或移除电话号码字段
添加或移除公司/组织字段
测试必填与可选字段的平衡
使用字段补充工具自动填充已知数据
为回访/已知用户隐藏部分字段

智能表单

添加邮箱和电话号码的实时验证
渐进式信息收集（随时间逐步询问更多信息）
根据之前的答案显示条件字段
公司名称自动联想

Copy & Design Experiments

文案与设计实验

Labels & Microcopy

Test field label clarity and length
Placeholder text optimization
Help text: show vs. hide vs. on-hover
Error message tone (friendly vs. direct)

CTAs & Buttons

Button text variations ("Submit" vs. "Get My Quote" vs. specific action)
Button color and size testing
Button placement relative to fields

Trust Elements

Add privacy assurance near form
Show trust badges next to submit
Add testimonial near form
Display expected response time

标签与微文案

测试字段标签的清晰度与长度
占位符文本优化
帮助文本：显示 vs. 隐藏 vs. 悬停显示
错误提示语气（友好 vs. 直接）

CTA与按钮

按钮文案变体（"Submit" vs. "获取我的报价" vs. 特定动作）
按钮颜色与尺寸测试
按钮相对于字段的位置

信任元素

在表单附近添加隐私声明
在提交按钮旁显示信任徽章
在表单附近添加客户评价
显示预期响应时间

Form Type-Specific Experiments

特定表单类型实验

Demo Request Forms

Test with/without phone number requirement
Add "preferred contact method" choice
Include "What's your biggest challenge?" question
Test calendar embed vs. form submission

Lead Capture Forms

Email-only vs. email + name
Test value proposition messaging above form
Gated vs. ungated content strategies
Post-submission enrichment questions

Contact Forms

Add department/topic routing dropdown
Test with/without message field requirement
Show alternative contact methods (chat, phone)
Expected response time messaging

演示请求表单

测试是否要求填写电话号码
添加"偏好联系方式"选项
加入"你最大的挑战是什么？"的问题
测试嵌入日历 vs. 表单提交的效果

获客表单

仅邮箱 vs. 邮箱+姓名
测试表单上方的价值主张文案
Gated内容 vs. 非Gated内容策略
提交后补充信息询问

联系表单

添加"部门/主题"路由下拉菜单
测试是否要求填写留言字段
显示其他联系方式（在线聊天、电话）
预期响应时间文案

Mobile & UX Experiments

移动端与用户体验实验

Larger touch targets for mobile
Test appropriate keyboard types by field
Sticky submit button on mobile
Auto-focus first field on page load
Test form container styling (card vs. minimal)

移动端更大的触摸目标
测试字段对应的键盘类型
移动端固定提交按钮
页面加载时自动聚焦第一个字段
测试表单容器样式（卡片式 vs. 极简式）

Task-Specific Questions

任务特定问题

What's your current form completion rate?
Do you have field-level analytics?
What happens with the data after submission?
Which fields are actually used in follow-up?
Are there compliance/legal requirements?
What's the mobile vs. desktop split?

你当前的表单完成率是多少？
你有字段级别的分析数据吗？
表单提交后的数据会如何处理？
哪些字段在后续跟进中实际会被使用？
是否存在合规/法律要求？
移动端与桌面端的流量占比是多少？