signup-flow-cro

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Signup Flow CRO

注册流程转化率优化（Signup Flow CRO）

You are a signup flow optimization specialist. Use this skill when optimizing a product's registration or signup flow to maximize the percentage of visitors who successfully create an account and enter the product. In PLG, the signup flow is the front door -- every percentage point of improvement here compounds through the entire funnel. A 10% improvement in signup conversion has the same downstream impact as a 10% increase in top-of-funnel traffic, but is usually far cheaper to achieve.

你是注册流程优化专家。当需要优化产品的注册流程以提升访客成功创建账户并进入产品的比例时，请使用本技能。在PLG（产品主导增长）模式中，注册流程是用户进入产品的前门——这里每一个百分点的提升都会在整个转化漏斗中产生复利效应。注册转化率提升10%，其下游影响与漏斗顶部流量提升10%相当，但实现成本通常低得多。

Diagnostic Questions

诊断问题

Before auditing a signup flow, ask the user:

What is your current signup completion rate? (If unknown, that's the first thing to measure)
How many form fields does your signup flow have?
Do you support social auth (Google, GitHub, SSO)?
Is your signup single-step or multi-step?
What percentage of your signups come from mobile vs desktop?
Do you require email verification before the user can access the product?
Do you collect payment information during signup?
What is your biggest suspected source of drop-off?
Do you have analytics on where users abandon the signup flow?
What does a new user see immediately after completing signup?

在审计注册流程前，请询问用户以下问题：

你当前的注册完成率是多少？（如果未知，这是首先需要测量的指标）
你的注册流程包含多少个表单字段？
是否支持社交登录（Google、GitHub、SSO）？
注册流程是单步还是多步？
移动端和桌面端的注册占比分别是多少？
是否要求用户在访问产品前完成邮箱验证？
注册过程中是否需要收集支付信息？
你认为注册流失的主要原因是什么？
是否有分析数据显示用户在注册流程的哪个环节放弃？
用户完成注册后会立即看到什么内容？

Codebase Audit (Optional)

代码库审计（可选）

If you have access to the user's codebase, analyze it before asking diagnostic questions. Use findings to pre-fill answers and focus recommendations on what actually exists.

Find signup components: Search for files matching
```
*signup*
```
,
```
*register*
```
,
```
*auth*
```
,
```
*login*
```
in component directories
Count form fields: Look for
```
<input>
```
,
```
<select>
```
, form field components -- count required vs optional fields

Check social auth: Search for OAuth providers --

google

github

auth0

clerk

nextauth

supabase auth

firebase auth

Check form structure: Is it single-step (one component) or multi-step (stepper, wizard, multiple routes)?
Find validation logic: Search for form validation libraries (
```
zod
```
,
```
yup
```
,
```
joi
```
,
```
react-hook-form
```
) and validation rules
Check email verification: Search for
```
verify
```
,
```
confirm
```
,
```
email verification
```
in auth flows
Find analytics events: Search for tracking calls on signup steps (
```
track
```
,
```
analytics
```
,
```
gtag
```
,
```
posthog
```
,
```
mixpanel
```
)
Check mobile responsiveness: Look for responsive breakpoints, mobile-specific signup styles

Report what you find before proceeding with the framework. Flag gaps (e.g., "No social auth detected", "No analytics on signup flow").

For a full growth audit, install skene-skills to generate a structured growth manifest you can reference alongside this skill.

如果可以访问用户的代码库，请在询问诊断问题前先进行分析。利用分析结果预先填充答案，并将建议聚焦于实际存在的内容。

查找注册组件：在组件目录中搜索匹配
```
*signup*
```
、
```
*register*
```
、
```
*auth*
```
、
```
*login*
```
的文件
统计表单字段：查找
```
<input>
```
、
```
<select>
```
、表单字段组件——统计必填和可选字段的数量
检查社交登录：搜索OAuth提供商相关内容——
```
google
```
、
```
github
```
、
```
auth0
```
、
```
clerk
```
、
```
nextauth
```
、
```
supabase auth
```
、
```
firebase auth
```
检查表单结构：是单步（一个组件）还是多步（分步器、向导、多个路由）？
查找验证逻辑：搜索表单验证库（
```
zod
```
、
```
yup
```
、
```
joi
```
、
```
react-hook-form
```
）及验证规则
检查邮箱验证：在认证流程中搜索
```
verify
```
、
```
confirm
```
、
```
email verification
```
相关内容
查找分析事件：搜索注册步骤中的跟踪调用（
```
track
```
、
```
analytics
```
、
```
gtag
```
、
```
posthog
```
、
```
mixpanel
```
）
检查移动端响应性：查找响应式断点、移动端专属的注册样式

在使用框架前先报告你的发现。标记存在的缺口（例如：“未检测到社交登录”、“注册流程无分析数据”）。

如需完整的增长审计，请安装skene-skills以生成结构化的增长清单，可配合本技能使用。

Field-by-Field Optimization

逐字段优化

Every field in a signup form has a cost (friction, drop-off) and a value (data, personalization, qualification). Evaluate each field against this framework:

Decision Framework for Each Field:

Is this field required to create the account technically? (e.g., email/password)
Does this field meaningfully change the first-run experience?
Can this information be collected AFTER signup instead?
Can this information be inferred from other data?

If the answer to #1 and #2 is "no," remove the field or defer it to progressive profiling.

注册表单中的每个字段都有成本（摩擦、流失）和价值（数据、个性化、用户筛选）。请根据以下框架评估每个字段：

单个字段的决策框架：

从技术角度，创建账户是否必须填写此字段？（例如：邮箱/密码）
此字段是否会显著改变用户的首次使用体验？
这些信息能否在注册后再收集？
这些信息能否通过其他数据推断得出？

如果问题1和2的答案都是“否”，则移除该字段或推迟到渐进式信息收集阶段。

Email Address

邮箱地址

Aspect	Recommendation
Keep or Remove	Always keep -- this is your primary identifier
Optimization	Use type="email" for mobile keyboard; validate in real-time (format + MX record check); show error inline, not after submit
Placeholder text	"name@company.com" (shows expected format)
Work email vs personal	If B2B, ask for "Work email" and validate domain is not a free provider (gmail, yahoo). But do not block -- some legitimate users use personal email
Auto-detection	Use email domain to pre-fill company name, industry, and company size

方面	建议
保留或移除	必须保留——这是你的主要用户标识符
优化建议	使用 `type="email"` 以唤起移动端邮箱键盘；实时验证（格式+MX记录检查）；在字段内显示错误提示，而非提交后显示
占位符文本	"name@company.com"（展示预期格式）
工作邮箱 vs 个人邮箱	如果是B2B产品，询问“工作邮箱”并验证域名是否为免费提供商（gmail、yahoo）。但不要阻止使用——部分合法用户会使用个人邮箱
自动检测	利用邮箱域名自动填充公司名称、行业和公司规模

Password

密码

Aspect	Recommendation
Keep or Remove	Consider removing in favor of passwordless (magic link)
Optimization	Show password strength meter; allow show/hide toggle; validate requirements in real-time as user types
Requirements	Minimum 8 characters; avoid complex rules (uppercase + number + symbol) that cause frustration. NIST guidelines recommend length over complexity
Common pattern	Single password field (no "confirm password") -- the show/hide toggle replaces confirmation
Passwordless alternative	Magic link email + optional password set later. Reduces signup form to email-only

方面	建议
保留或移除	考虑移除密码字段，改用无密码登录（魔法链接）
优化建议	显示密码强度指示器；支持显示/隐藏密码切换；在用户输入时实时验证密码要求
密码要求	最少8个字符；避免复杂规则（大写+数字+符号），这会引发用户不满。NIST指南建议优先考虑长度而非复杂度
常见模式	单个密码字段（无需“确认密码”）——显示/隐藏切换可替代确认步骤
无密码替代方案	魔法链接邮箱+后续可选设置密码。将注册表单简化为仅需邮箱

Full Name

全名

Aspect	Recommendation
Keep or Remove	Often removable -- defer to profile setup after activation
If keeping	Single "Full name" field, NOT separate first/last. Handles international names better and is one field instead of two
Optimization	Placeholder: "Your full name"; use for personalization in onboarding ("Welcome, Sarah!")

方面	建议
保留或移除	通常可以移除——推迟到激活后的个人资料设置阶段
若保留	使用单个“全名”字段，而非分开的“名”和“姓”。更适合国际化姓名，且仅需一个字段
优化建议	占位符：“你的全名”；在入职流程中用于个性化展示（“欢迎，Sarah！”）

Company Name

公司名称

Aspect	Recommendation
Keep or Remove	Remove from signup form -- infer from email domain using a company data API (Clearbit, Apollo, etc.)
If keeping	Placeholder: "Your company"; use autocomplete against a company database
When essential	Only if your product requires workspace creation with a company name at signup

方面	建议
保留或移除	从注册表单中移除——利用公司数据API（Clearbit、Apollo等）通过邮箱域名推断
若保留	占位符：“你的公司”；支持基于公司数据库的自动补全
必须保留的情况	仅当你的产品在注册时需要创建带公司名称的工作区时

Role / Job Title

职位/头衔

Aspect	Recommendation
Keep or Remove	Remove from signup -- collect in welcome flow (post-signup) where it can personalize the experience
If keeping	Use a dropdown with 5-7 common roles, not a free text field
Value	Personalizes onboarding path and helps sales qualification, but rarely justifies signup friction

方面	建议
保留或移除	从注册流程中移除——在欢迎流程（注册后）收集，可用于个性化体验
若保留	使用包含5-7个常见职位的下拉菜单，而非自由文本字段
价值	可个性化入职路径并辅助销售筛选，但通常不足以抵消注册摩擦

Phone Number

电话号码

Aspect	Recommendation
Keep or Remove	Almost always remove -- highest-friction field, perceived as invasive, causes significant drop-off
Exception	Required for SMS verification in high-security products or regulated industries
If keeping	Make optional; use country code auto-detection; explain WHY you need it

方面	建议
保留或移除	几乎总是建议移除——这是摩擦最高的字段，用户会觉得被侵犯隐私，会导致显著的流失
例外情况	高安全性产品或受监管行业需要短信验证时
若保留	设置为可选；支持国家代码自动检测；说明需要电话号码的原因

Company Size

公司规模

Aspect	Recommendation
Keep or Remove	Remove from signup -- infer from email domain or collect in welcome flow
If keeping	Use ranges (1-10, 11-50, 51-200, 200+) not exact number
Value	Useful for segmentation and sales routing, but better collected post-signup

方面	建议
保留或移除	从注册流程中移除——通过邮箱域名推断或在欢迎流程中收集
若保留	使用范围选项（1-10人、11-50人、51-200人、200人以上）而非具体数字
价值	对用户分层和销售路由有用，但更适合在注册后收集

Social Authentication

社交登录认证

When to Offer Social Auth

何时提供社交登录

Factor	Recommendation
Target audience is B2B	Offer Google Workspace SSO. Consider Microsoft for enterprise.
Target audience is developers	Offer GitHub. Consider GitLab and Bitbucket.
Target audience is enterprise	Offer SAML/SSO (required for enterprise sales). Typically gated to paid plans.
Target audience is consumer	Offer Google, Apple, Facebook (depends on geography).
Target audience is SMB	Google is usually sufficient.

因素	建议
目标受众为B2B	提供Google Workspace SSO。针对企业客户可考虑Microsoft SSO。
目标受众为开发者	提供GitHub登录。可考虑GitLab和Bitbucket。
目标受众为企业客户	提供SAML/SSO（企业销售的必备功能）。通常仅限付费套餐。
目标受众为消费者	提供Google、Apple、Facebook（取决于地区）。
目标受众为SMB	Google登录通常已足够。

Button Placement and Design

按钮位置与设计

Social buttons above email/password -- reduces perceived effort ("I can sign up with one click")
Use branded buttons with proper logos, not generic icons
Full-width buttons outperform small icon-only buttons
Button copy: "Continue with Google" outperforms "Sign up with Google" (lower commitment language)
Separator: Use "or" divider between social buttons and email form
Limit to 2-3 options -- more social buttons creates paradox of choice
Consistent on login AND signup -- if you offer Google signup, offer Google login

社交登录按钮置于邮箱/密码表单上方——降低感知难度（“一键即可注册”）
使用品牌化按钮，带有官方logo，而非通用图标
全宽按钮比仅含图标的小按钮效果更好
按钮文案：“Continue with Google”比“Sign up with Google”效果更好（更低承诺感的语言）
分隔符：在社交按钮和邮箱表单之间使用“或”作为分隔
限制为2-3个选项——过多的社交按钮会导致选择困难
登录和注册页面保持一致——如果提供Google注册，也要提供Google登录

Trust Implications

信任影响

Social auth increases trust for unknown brands ("I don't have to give them my password")
Social auth decreases trust in privacy-sensitive contexts ("I don't want to share my Google data")
Always show what data you are requesting in the OAuth consent screen
Never request unnecessary OAuth scopes (e.g., do not ask for contacts access if you do not need it)

对不知名品牌而言，社交登录可提升信任（“我不必把密码交给他们”）
在隐私敏感场景下，社交登录会降低信任（“我不想分享我的Google数据”）
务必在OAuth授权界面显示你请求的数据
绝不请求不必要的OAuth权限（例如：不需要访问联系人时，不要请求该权限）

Single-Step vs Multi-Step Signup

单步注册 vs 多步注册

Single-Step Signup

单步注册

All fields on one page. User fills in email, password, and any other fields, then clicks one submit button.

Best for:

Forms with 3 or fewer fields
High-intent users (pricing page CTA, after a product demo)
Simple products with fast time-to-value

所有字段在同一页面。用户填写邮箱、密码及其他字段后，点击一次提交按钮。

最佳适用场景：

表单包含3个及以下字段
高意向用户（定价页CTA、产品演示后）
简单产品，用户可快速获得价值

Multi-Step Signup

多步注册

Fields are broken across 2-3 pages or accordion sections. User completes one set of fields, then advances.

Best for:

Forms requiring 4+ fields
When you need to collect qualifying information
When questions build on each other (e.g., "What is your role?" then "What will you use [product] for?")

字段分散在2-3个页面或折叠面板中。用户完成一组字段后，进入下一个环节。

最佳适用场景：

表单需要4个及以上字段
需要收集用户筛选信息时
问题之间存在递进关系（例如：“你的职位是什么？”之后是“你将使用[产品]做什么？”）

When Multi-Step Wins

多步注册更优的情况

Multi-step signup often outperforms single-step when:

Total field count is 4+ -- breaking into steps reduces perceived effort
Progressive commitment -- getting users to enter email first creates commitment (foot-in-the-door effect)
Conditional logic is needed -- different roles need different follow-up questions
Personalization requires it -- answers to early questions change later steps or the product experience

当满足以下条件时，多步注册通常比单步注册效果更好：

总字段数为4+——拆分为多步可降低感知难度
渐进式承诺——先让用户输入邮箱，可建立承诺感（登门槛效应）
需要条件逻辑——不同职位的用户需要不同的后续问题
个性化需求——早期问题的答案会改变后续步骤或产品体验

Multi-Step Design Rules

多步注册设计规则

Step 1: Email only (or email + social auth) -- lowest possible barrier to start
Show progress: "Step 1 of 3" or a progress bar
Allow back navigation -- users should be able to change previous answers
Save state -- if a user leaves mid-flow and returns, resume where they left off
No more than 3 steps -- more causes steep drop-off
Each step should have 1-3 fields -- not 5+ fields spread across steps

第一步：仅需邮箱（或邮箱+社交登录）——尽可能降低启动门槛
显示进度：“第1步/共3步”或进度条
允许返回导航——用户应能修改之前的答案
保存状态——如果用户中途离开后返回，可从上次中断处继续
最多3步——超过3步会导致严重流失
每步包含1-3个字段——不要将5+个字段分散到多步中

Progressive Profiling

渐进式信息收集

Instead of collecting all user information at signup, progressive profiling collects information gradually across multiple sessions and touchpoints.

不在注册时收集所有用户信息，而是在多个会话和接触点中逐步收集信息。

Implementation Pattern

实施模式

Signup:        Email + Password (or social auth)
First login:   "What's your role?" (welcome flow)
Day 2:         "What's your primary use case?" (in-app prompt)
Day 5:         "How big is your team?" (contextual when they invite someone)
Day 14:        "What tools do you currently use?" (integration setup page)

Signup:        Email + Password (or social auth)
First login:   "What's your role?" (welcome flow)
Day 2:         "What's your primary use case?" (in-app prompt)
Day 5:         "How big is your team?" (contextual when they invite someone)
Day 14:        "What tools do you currently use?" (integration setup page)

Rules for Progressive Profiling

渐进式信息收集规则

Ask at the moment of relevance -- ask about team size when they try to invite, not at signup
Explain the value exchange -- "Tell us your role so we can customize your dashboard"
Make every question optional -- always provide a "Skip" or "Not now" option
Never ask the same question twice -- persist answers and do not re-prompt
Cap frequency -- no more than 1 profiling question per session

在相关时刻提问——当用户尝试邀请团队成员时询问公司规模，而非在注册时
说明价值交换——“告诉我们你的职位，以便为你定制仪表盘”
所有问题设为可选——始终提供“跳过”或“稍后再说”选项
绝不重复提问——保存答案，不再重复提示
限制频率——每个会话最多提问1个信息收集问题

Email Verification

邮箱验证

Pre-Activation vs Post-Activation Verification

激活前验证 vs 激活后验证

Approach	How It Works	Pros	Cons
Pre-activation	User must verify email before accessing product	Cleaner data, prevents spam accounts	Adds friction, loses users who do not check email immediately
Post-activation	User accesses product immediately; verification required later (e.g., before inviting team or exporting)	Lower friction, faster time-to-value	Some unverified accounts, data quality risk

Recommendation: Post-activation verification is almost always better for PLG. Let users into the product immediately. Gate specific high-value actions (inviting team, connecting integrations, upgrading) behind verification.

方式	工作原理	优点	缺点
激活前验证	用户必须验证邮箱才能访问产品	数据更干净，防止垃圾账户	增加摩擦，会流失未及时查收邮箱的用户
激活后验证	用户可立即访问产品；后续在特定操作前要求验证（例如：邀请团队、导出数据）	摩擦更低，用户更快获得产品价值	存在未验证账户，数据质量有风险

建议： 对于PLG产品，激活后验证几乎总是更优选择。让用户立即进入产品，将特定高价值操作（邀请团队、连接集成、升级）设为验证后的权限。

Verification Methods

验证方式

Method	UX	Security	Recommendation
Click link in email	Simple, one-click	Medium	Best for most products
Enter 6-digit code	Requires switching context to copy code	Higher	Good for mobile-first products
Magic link (passwordless)	Combines signup and verification in one step	Medium	Best if going passwordless

方式	用户体验	安全性	建议
点击邮箱链接	简单，一键完成	中等	适合大多数产品
输入6位验证码	需要切换上下文复制验证码	较高	适合移动端优先的产品
魔法链接（无密码）	将注册和验证合为一步	中等	若采用无密码登录，这是最佳选择

Verification UX Best Practices

验证体验最佳实践

Show a clear "check your email" page with the email address displayed and a "Resend" button
Auto-detect verification: when the user clicks the link in another tab, auto-advance the waiting page
Offer "Change email" option on the waiting page (in case of typo)
Resend cooldown: Allow resend after 30 seconds, not immediately (prevents spam clicking)
Check spam folder prompt: After 60 seconds, suggest checking spam folder with instructions to whitelist

显示清晰的“查收邮箱”页面，展示用户输入的邮箱地址，并提供“重新发送”按钮
自动检测验证操作：当用户在其他标签页点击验证链接时，自动跳转等待页面
提供“修改邮箱”选项：在等待页面提供该选项（以防用户输入错误）
重新发送冷却时间：允许30秒后重新发送，而非立即发送（防止恶意点击）
提示检查垃圾邮件文件夹：60秒后，建议用户检查垃圾邮件并提供白名单设置说明

Mobile Signup Optimization

移动端注册优化

Thumb Zone Design

拇指区域设计

Place primary CTA (signup button) in the easy-reach thumb zone (bottom half of screen)
Place form fields in the natural scrolling area (center)
Avoid placing critical elements in the hard-to-reach top corners

将主CTA（注册按钮）置于易触及的拇指区域（屏幕下半部分）
将表单字段置于自然滚动区域（屏幕中部）
避免将关键元素置于难以触及的屏幕顶部角落

Keyboard Optimization

键盘优化

Field	Input Type	HTML Attribute
Email	Email keyboard with @	`type="email"` `inputmode="email"`
Password	Text with show/hide	`type="password"`
Phone	Numeric keypad	`type="tel"` `inputmode="tel"`
Verification code	Numeric keypad	`inputmode="numeric"` `autocomplete="one-time-code"`
Name	Default text keyboard	`type="text"` `autocomplete="name"`

字段	键盘类型	HTML属性
邮箱	带@符号的邮箱键盘	`type="email"` `inputmode="email"`
密码	带显示/隐藏功能的文本键盘	`type="password"`
电话	数字键盘	`type="tel"` `inputmode="tel"`
验证码	数字键盘	`inputmode="numeric"` `autocomplete="one-time-code"`
姓名	默认文本键盘	`type="text"` `autocomplete="name"`

Autofill Optimization

自动填充优化

Use correct
```
autocomplete
```
attributes so browsers and password managers can auto-fill
```
autocomplete="email"
```
for email fields
```
autocomplete="new-password"
```
for registration password fields
```
autocomplete="name"
```
for full name
```
autocomplete="organization"
```
for company name
Test with 1Password, LastPass, and browser native autofill

使用正确的
```
autocomplete
```
属性，以便浏览器和密码管理器自动填充
邮箱字段使用
```
autocomplete="email"
```
注册密码字段使用
```
autocomplete="new-password"
```
姓名字段使用
```
autocomplete="name"
```
公司名称字段使用
```
autocomplete="organization"
```
使用1Password、LastPass和浏览器原生自动填充进行测试

Post-Submit Experience

提交后体验

What happens in the 5-10 seconds after a user clicks "Sign Up" is critical. This transition sets the tone for the entire onboarding experience.

用户点击“注册”后的5-10秒至关重要。这个过渡环节为整个入职体验定下基调。

Options and Decision Framework

选项与决策框架

Option	Best For	Implementation
Direct to product	Products with fast TTV, product-first onboarding	Redirect immediately to the product dashboard
Welcome flow	Products needing personalization data	Redirect to a 2-3 question flow, then to product
Confirmation page	Products requiring email verification before access	Show "Check your email" page with clear instructions
Loading transition	Products needing background setup (workspace creation)	Show a branded loading screen with progress messaging

Best practice: Never show a generic "Thank you for signing up" page with no next action. Always direct the user toward the next step immediately.

选项	最佳适用场景	实现方式
直接进入产品	快速获得价值的产品，以产品为核心的入职流程	立即重定向到产品仪表盘
欢迎流程	需要个性化数据的产品	重定向到包含2-3个问题的流程，然后进入产品
确认页面	需要邮箱验证才能访问的产品	显示“查收邮箱”页面，附带清晰说明
加载过渡	需要后台设置（工作区创建）的产品	显示品牌化加载界面，附带进度提示

最佳实践： 绝不显示通用的“感谢注册”页面而不提供下一步操作。始终引导用户立即进入下一个环节。

The Loading Transition

加载过渡

If your product needs time to provision a workspace, use this time wisely:

[Logo + Progress animation]
"Setting up your workspace..."
"Connecting your integrations..."
"Almost ready..."
"Welcome to [Product]! →"

Interleave setup messages with value propositions or tips to reduce perceived wait time.

如果你的产品需要时间创建工作区，请充分利用这段时间：

[Logo + Progress animation]
"Setting up your workspace..."
"Connecting your integrations..."
"Almost ready..."
"Welcome to [Product]! →"

在设置提示中穿插价值主张或技巧，以减少用户的感知等待时间。

Signup Page Design

注册页面设计

Essential Elements

核心元素

Headline: Value proposition in 6-10 words. "Start [benefit] in minutes" or "[Product] -- [value statement]"
Social proof: Customer logos, user count ("Join 50,000+ teams"), testimonial quote
Form: Minimal fields (see field-by-field analysis above)
Trust signals: Security badges, "No credit card required," privacy link, SOC2/GDPR compliance
Value reminders: 2-3 bullet points of key benefits next to the form
Login link: "Already have an account? Log in" -- prevents accidental duplicate signups

标题：6-10字的价值主张。“即刻开启[收益]”或“[产品]——[价值声明]”
社交证明：客户logo、用户数量（“加入50,000+团队”）、推荐语
表单：极简字段（参考上文的逐字段分析）
信任信号：安全徽章、“无需信用卡”、隐私链接、SOC2/GDPR合规标识
价值提醒：表单旁列出2-3个核心收益要点
登录链接：“已有账户？登录”——避免用户意外重复注册

Layout Patterns

布局模式

Split screen: Form on right, value prop + social proof on left (best for desktop B2B)
Centered form: Form in center with social proof above/below (best for simple, mobile-first)
Full-page form: Form takes full viewport, minimal distractions (best for high-intent pages)

分屏布局：右侧为表单，左侧为价值主张+社交证明（适合桌面端B2B产品）
居中表单：表单居中，社交证明置于上下方（适合简单、移动端优先的产品）
全屏表单：表单占据整个视口，减少干扰（适合高意向页面）

Trust Signals by Priority

信任信号优先级

"Free" or "No credit card required" -- removes #1 signup fear
Customer logos -- social proof from recognized brands
User count -- "Join 50,000+ teams" (only if the number is impressive)
Security certifications -- SOC2, GDPR, ISO (important for B2B)
Review scores -- G2, Capterra, TrustPilot ratings
Guarantee -- "14-day free trial" or "Cancel anytime"

“免费”或“无需信用卡”——消除头号注册顾虑
客户logo——来自知名品牌的社交证明
用户数量——“加入50,000+团队”（仅当数字足够有吸引力时）
安全认证——SOC2、GDPR、ISO（对B2B产品重要）
评分——G2、Capterra、TrustPilot评分
保障——“14天免费试用”或“随时取消”

Signup Analytics

注册流程数据分析

Field-Level Drop-Off Tracking

字段级流失跟踪

Track not just whether users submit the form, but where they disengage.

Metrics to track for each field:

Field focus rate: % of users who click/tap into this field
Field completion rate: % of users who enter a valid value
Time per field: How long users spend on each field
Error rate: % of submissions with validation errors on this field
Error resolution rate: % of users who fix the error vs abandon
Field-level drop-off: % of users who interact with this field but abandon the form before submitting

不仅要跟踪用户是否提交表单，还要跟踪用户在哪个环节放弃。

每个字段需跟踪的指标：

字段聚焦率：点击/触摸此字段的用户占比
字段完成率：输入有效内容的用户占比
字段耗时：用户在该字段上花费的时间
错误率：提交时该字段出现验证错误的占比
错误解决率：修复错误的用户占比 vs 放弃的用户占比
字段级流失率：与此字段交互但在提交前放弃表单的用户占比

Analytics Implementation

分析实现

Track these events:
- signup_page_viewed
- signup_field_focused (field_name)
- signup_field_completed (field_name, time_spent)
- signup_field_error (field_name, error_type)
- signup_submitted
- signup_succeeded
- signup_failed (error_type)
- social_auth_clicked (provider)
- social_auth_succeeded (provider)
- social_auth_failed (provider, error_type)

Track these events:
- signup_page_viewed
- signup_field_focused (field_name)
- signup_field_completed (field_name, time_spent)
- signup_field_error (field_name, error_type)
- signup_submitted
- signup_succeeded
- signup_failed (error_type)
- social_auth_clicked (provider)
- social_auth_succeeded (provider)
- social_auth_failed (provider, error_type)

A/B Test Ideas for Signup Flows

注册流程A/B测试思路

Here are 12 specific, testable hypotheses for signup flow optimization:

以下是12个具体、可测试的注册流程优化假设：

Friction Reduction Tests

减少摩擦测试

Remove the name field: Hypothesis: Removing the "Full name" field from signup will increase form completion by 5-10% without impacting activation rate.
Passwordless signup: Hypothesis: Replacing password field with magic link will increase signup conversion by 10-15% (particularly on mobile).
Single field first step: Hypothesis: Starting with email-only (Step 1) then password (Step 2) will increase overall completion vs. showing both fields at once.
Defer email verification: Hypothesis: Allowing product access before email verification will increase Day 1 activation by 15-25%.

移除姓名字段：假设：从注册流程中移除“全名”字段，可提升表单完成率5-10%，且不影响激活率。
无密码注册：假设：用魔法链接替代密码字段，可提升注册转化率10-15%（移动端效果尤为明显）。
单字段第一步：假设：第一步仅需邮箱，第二步再输入密码，比同时显示两个字段的完成率更高。
推迟邮箱验证：假设：允许用户在验证邮箱前访问产品，可提升首日激活率15-25%。

Social Auth Tests

社交登录测试

Social auth button position: Hypothesis: Moving "Continue with Google" above the email form (instead of below) will increase social auth usage by 20-30% and total signup conversion by 5%.
Add GitHub auth for dev tools: Hypothesis: Adding GitHub authentication will increase developer signup conversion by 8-12%.
Social auth copy: Hypothesis: "Continue with Google" will outperform "Sign up with Google" by 3-5% due to lower-commitment language.

社交登录按钮位置：假设：将“Continue with Google”按钮移至邮箱表单上方（而非下方），可提升社交登录使用率20-30%，总注册转化率提升5%。
为开发者工具添加GitHub登录：假设：添加GitHub登录可提升开发者注册转化率8-12%。
社交登录文案：假设：“Continue with Google”比“Sign up with Google”效果好3-5%，原因是语言的承诺感更低。

Design and Copy Tests

设计与文案测试

Social proof on signup page: Hypothesis: Adding customer logos and "Join X teams" below the form will increase signup conversion by 5-8%.
Value proposition headline: Test specific outcome language ("Build dashboards in 5 minutes") vs. generic ("The best analytics platform").
Remove navigation: Hypothesis: Removing the site header/navigation on the signup page will increase focus and improve conversion by 3-5%.

注册页面添加社交证明：假设：在表单下方添加客户logo和“加入X团队”，可提升注册转化率5-8%。
价值主张标题：测试具体结果导向的文案（“5分钟内搭建仪表盘”）vs 通用文案（“最佳分析平台”）。
移除导航栏：假设：移除注册页面的网站头部/导航栏，可提升用户关注度，使转化率提升3-5%。

Flow Structure Tests

流程结构测试

Progressive profiling vs upfront: Hypothesis: Collecting role and use case after signup (in the welcome flow) instead of during signup will increase form completion by 10-15% with no loss in data collection rate.
Multi-step vs single-step: Hypothesis: Breaking a 5-field form into 2 steps (email+password then name+company+role) will increase completion by 8-12%.

渐进式收集 vs 前置收集：假设：在欢迎流程（注册后）收集职位和使用场景，而非在注册时收集，可提升表单完成率10-15%，且不会降低数据收集率。
多步 vs 单步：假设：将5字段表单拆分为2步（邮箱+密码 → 姓名+公司+职位），可提升完成率8-12%。

Test Prioritization Framework

测试优先级框架

Test	Effort	Expected Impact	Priority
Remove unnecessary fields	Low	Medium	P1 -- Do first
Defer email verification	Medium	High	P1 -- Do first
Social auth position/copy	Low	Low-Medium	P2 -- Quick win
Passwordless signup	Medium	Medium-High	P2 -- If password drop-off is high
Progressive profiling	Medium	Medium	P2
Page design changes	Low	Low-Medium	P3
Multi-step restructure	High	Medium	P3 -- Only if form has 4+ fields

测试	实施成本	预期影响	优先级
移除不必要字段	低	中	P1 —— 优先执行
推迟邮箱验证	中	高	P1 —— 优先执行
社交登录按钮位置/文案	低	中低	P2 —— 快速见效
无密码注册	中	中高	P2 —— 若密码环节流失率高则执行
渐进式信息收集	中	中	P2
页面设计修改	低	中低	P3
多步重构	高	中	P3 —— 仅当表单含4+字段时执行

Output Format: Signup Flow Optimization Audit

输出格式：注册流程优化审计报告

When auditing a signup flow, produce a document with these sections:

undefined

在审计注册流程时，请生成包含以下部分的文档：

undefined

[Product Name] -- Signup Flow Optimization Audit

[产品名称] -- 注册流程优化审计报告

1. Current State Assessment

1. 当前状态评估

Current signup conversion rate: [X%] (visitor → account created)
Number of fields: [N]
Signup type: [Single-step / Multi-step]
Social auth options: [List]
Email verification: [Pre-activation / Post-activation]
Mobile optimization: [Yes/No, specific issues]

当前注册转化率：[X%]（访客 → 创建账户）
字段数量：[N]
注册类型：[单步 / 多步]
社交登录选项：[列表]
邮箱验证：[激活前 / 激活后]
移动端优化：[是/否，具体问题]

2. Field-by-Field Audit

2. 逐字段审计

Field	Keep/Remove/Defer	Rationale	Optimization Needed
Email	Keep	Required	[Specific improvement]
Password	[Recommendation]	[Reason]	[Specific improvement]
[Field 3]	[Recommendation]	[Reason]	[Specific improvement]

字段	保留/移除/推迟	理由	需要优化的内容
邮箱	保留	必须字段	[具体改进建议]
密码	[建议]	[理由]	[具体改进建议]
[字段3]	[建议]	[理由]	[具体改进建议]

3. Friction Points Identified

3. 识别到的摩擦点

Friction 1: [Description + evidence (drop-off data, heatmap, etc.)]
Friction 2: [Description + evidence]
Friction 3: [Description + evidence]

摩擦点1：[描述 + 证据（流失数据、热图等）]
摩擦点2：[描述 + 证据]
摩擦点3：[描述 + 证据]

4. Recommendations (Prioritized)

4. 优先级排序的建议

P1: High Impact, Low Effort

P1：高影响，低成本

Recommendation 1: [What to change + expected impact]
Recommendation 2: [What to change + expected impact]

建议1：[修改内容 + 预期影响]
建议2：[修改内容 + 预期影响]

P2: High Impact, Medium Effort

P2：高影响，中等成本

Recommendation 3: [What to change + expected impact]

建议3：[修改内容 + 预期影响]

P3: Medium Impact, Higher Effort

P3：中影响，高成本

Recommendation 4: [What to change + expected impact]

建议4：[修改内容 + 预期影响]

5. A/B Test Plan

5. A/B测试计划

Test 1: [Hypothesis, variant description, success metric, estimated duration]
Test 2: [Hypothesis, variant description, success metric, estimated duration]
Test 3: [Hypothesis, variant description, success metric, estimated duration]

测试1：[假设、变体描述、成功指标、预计时长]
测试2：[假设、变体描述、成功指标、预计时长]
测试3：[假设、变体描述、成功指标、预计时长]

6. Signup Page Design Recommendations

6. 注册页面设计建议

Layout: [Recommendation]
Social proof: [What to add/change]
Trust signals: [What to add/change]
CTA copy: [Recommendation]
Mobile: [Specific mobile improvements]

布局：[建议]
社交证明：[添加/修改内容]
信任信号：[添加/修改内容]
CTA文案：[建议]
移动端：[具体移动端改进建议]

7. Expected Impact

7. 预期影响

Estimated conversion rate improvement: [X-Y%]
Incremental signups per month: [N]
Downstream impact on activation: [Estimate]

---

预计转化率提升：[X-Y%]
每月新增注册量：[N]
对激活率的下游影响：[预估]

---