Back to Details

cro-optimization

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

CRO Optimization

CRO优化

Purpose

目标

Analyze a landing page and deliver a comprehensive CRO audit with specific, actionable recommendations to maximize conversions.
分析着陆页并提供全面的CRO审核报告，附带具体、可执行的建议以最大化转化率。

Execution Logic

执行逻辑

Check $ARGUMENTS first to determine execution mode:
首先检查$ARGUMENTS以确定执行模式：

If $ARGUMENTS is empty or not provided:

如果$ARGUMENTS为空或未提供：

Respond with: "cro-optimization loaded, provide your landing page URL or paste your HTML/CSS code"
Then wait for the user to provide their landing page in the next message.
回复内容： "cro-optimization已加载，请提供您的着陆页URL或粘贴HTML/CSS代码"
然后等待用户在后续消息中提供着陆页信息。

If $ARGUMENTS contains content:

如果$ARGUMENTS包含内容：

Proceed immediately to Task Execution (skip the "loaded" message).
立即执行任务（跳过已加载提示）。

Task Execution

任务执行

When landing page is available (either from initial $ARGUMENTS or follow-up message):
当获取到着陆页信息后（来自初始$ARGUMENTS或后续消息）：

1. MANDATORY: Read Reference Files FIRST

1. 强制要求：首先读取参考文件

BLOCKING REQUIREMENT — DO NOT SKIP THIS STEP
Before doing ANYTHING else, you MUST use the Read tool to read ALL three reference files:
Read: ./references/cro_principles.md
Read: ./references/landing_page_patterns.md
Read: ./references/element_audit_framework.md
What you will find:
  • cro_principles.md: 13 core CRO principles with detection criteria and fix patterns
  • landing_page_patterns.md: Real patterns from high-converting pages (ClickUp, Notion, Stripe, Apple, etc.) organized by category
  • element_audit_framework.md: Systematic framework for auditing HTML elements, CTAs, forms, and visual hierarchy
DO NOT PROCEED to Step 2 until you have read all files and have the principles, patterns, and audit framework loaded in context.
阻塞性要求——请勿跳过此步骤
在进行任何操作之前，必须使用Read工具读取全部三个参考文件：
Read: ./references/cro_principles.md
Read: ./references/landing_page_patterns.md
Read: ./references/element_audit_framework.md
文件内容说明：
  • cro_principles.md：13项核心CRO原则，包含检测标准和修复模式
  • landing_page_patterns.md：来自高转化页面（如ClickUp、Notion、Stripe、Apple等）的真实模式，按类别整理
  • element_audit_framework.md：用于审核HTML元素、CTA、表单和视觉层级的系统化框架
在读取所有文件并将原则、模式和审核框架载入上下文之前，请勿进入步骤2。

2. Check for Business Context

2. 检查业务上下文

Check if 
FOUNDER_CONTEXT.md
exists in the project root.
  • If it exists: Read it and use the business context to personalize recommendations (industry, target audience, product type, competitors).
  • If it doesn't exist: Proceed with analysis based on page content alone.
检查项目根目录下是否存在
FOUNDER_CONTEXT.md
文件：
  • 如果存在：读取该文件，并利用业务上下文（行业、目标受众、产品类型、竞争对手）个性化建议
  • 如果不存在：仅基于页面内容进行分析

3. Fetch and Extract Landing Page

3. 获取并提取着陆页内容

If user provided a URL:
  • Use WebFetch to retrieve the landing page content
  • Extract and catalog key elements (see Element Extraction below)
If user provided HTML/CSS directly:
  • Analyze the provided code directly
  • Note any missing context (live styling, images, etc.)
如果用户提供URL：
  • 使用WebFetch工具获取着陆页内容
  • 提取并分类关键元素（见下方元素提取部分）
如果用户直接提供HTML/CSS：
  • 直接分析提供的代码
  • 记录任何缺失的上下文（如实时样式、图片等）

4. Element Extraction

4. 元素提取

Extract and catalog these elements from the page:
Typography:
  • H1 (should be exactly one)
  • H2s (section headers)
  • Body text samples
  • CTA button copy
Visual Structure:
  • Above-the-fold content
  • Section sequence
  • Image/visual placement
  • Color scheme and contrast
Conversion Elements:
  • Primary CTA (copy, placement, design)
  • Secondary CTAs
  • Forms (field count, labels)
  • Trust signals (logos, testimonials, badges)
  • Social proof (metrics, reviews, case studies)
Technical:
  • Mobile responsiveness indicators
  • Load speed concerns (large images, etc.)
从页面中提取并分类以下元素：
排版：
  • H1（应仅有一个）
  • H2（章节标题）
  • 正文文本示例
  • CTA按钮文案
视觉结构：
  • 首屏内容
  • 章节顺序
  • 图片/视觉元素布局
  • 配色方案与对比度
转化元素：
  • 主CTA（文案、布局、设计）
  • 次要CTA
  • 表单（字段数量、标签）
  • 信任信号（logo、客户证言、徽章）
  • 社交证明（数据、评价、案例研究）
技术层面：
  • 移动端响应性指标
  • 加载速度问题（如大图片等）

5. Audit Against CRO Principles

5. 依据CRO原则审核

For each of the 13 principles in cro_principles.md:
  1. Check if the page violates the principle
  2. Note specific violations with evidence
  3. Determine severity (High/Medium/Low)
  4. Draft specific recommendations
Prioritize by impact:
  • High: Above-fold clarity, CTA effectiveness, major trust gaps
  • Medium: Objection handling, visual hierarchy, scannability
  • Low: Minor copy tweaks, nice-to-have additions
针对cro_principles.md中的每一项原则：
  1. 检查页面是否违反该原则
  2. 记录具体违规情况及证据
  3. 确定严重程度（高/中/低）
  4. 草拟具体建议
按影响优先级排序：
  • 高优先级：首屏清晰度、CTA有效性、重大信任缺口
  • 中优先级：异议处理、视觉层级、易读性
  • 低优先级：文案微调、锦上添花的补充内容

6. Compare to High-Converting Patterns

6. 与高转化模式对比

Using landing_page_patterns.md:
  1. Identify the most relevant category (B2B SaaS, E-commerce, etc.)
  2. Compare page structure to proven patterns
  3. Note missing elements that top performers include
  4. Identify opportunities to adopt successful patterns
使用landing_page_patterns.md：
  1. 识别最相关的类别（如B2B SaaS、电商等）
  2. 将页面结构与已验证的模式进行对比
  3. 记录顶级页面具备但当前页面缺失的元素
  4. 识别采用成功模式的机会

7. Generate Recommendations

7. 生成建议

For each issue found, provide:
  1. What to change — specific element and action
  2. Why it matters — principle violated and expected impact
  3. How to implement — concrete example or rewrite
  4. Priority — High/Medium/Low with reasoning
针对每个发现的问题，提供：
  1. 修改内容——具体元素及操作
  2. 重要性——违反的原则及预期影响
  3. 实施方式——具体示例或改写
  4. 优先级——高/中/低及理由

8. Format and Verify

8. 格式化与验证

  • Structure output according to Output Format section
  • Complete Quality Checklist self-verification
  • Ensure recommendations are specific and actionable (not generic advice)
  • 按照输出格式部分的要求整理输出内容
  • 完成质量检查表的自我验证
  • 确保建议具体且可执行（而非通用建议）

Writing Rules

写作规则

Hard constraints. No interpretation.
硬性约束，不得随意解读。

Core Rules

核心规则

  • Every recommendation must be specific and actionable
  • Include before/after examples for copy changes
  • Reference the specific principle violated
  • Prioritize by conversion impact, not ease of implementation
  • Frame changes as testable hypotheses when possible
  • Never recommend changes without explaining the "why"
  • 每条建议必须具体且可执行
  • 文案修改需包含前后示例
  • 引用具体违反的原则
  • 按转化影响而非实施难度排序
  • 尽可能将修改表述为可测试的假设
  • 绝不推荐无原因说明的修改

Analysis Rules

分析规则

  • Audit systematically — don't skip principles
  • Note what's working well, not just problems
  • Consider the page's apparent target audience
  • Account for likely traffic sources
  • Distinguish between critical issues and optimizations
  • 系统化审核——请勿遗漏原则
  • 记录表现良好的元素，而非仅指出问题
  • 考虑页面的目标受众
  • 参考可能的流量来源
  • 区分关键问题与优化项

Recommendation Rules

建议规则

  • Lead with highest-impact changes
  • Group related recommendations together
  • Provide specific copy rewrites, not just "make it clearer"
  • Include placement suggestions, not just content suggestions
  • Consider mobile experience separately
  • 优先呈现高影响修改
  • 将相关建议分组
  • 提供具体的文案改写，而非仅“使其更清晰”
  • 包含布局建议，而非仅内容建议
  • 单独考虑移动端体验

Output Format

输出格式

markdown
undefined
markdown
undefined

CRO Audit Report: [Page Name/URL]

CRO审核报告：[页面名称/URL]

Executive Summary

执行摘要

[2-3 sentences: Overall assessment, biggest opportunities, expected impact]
[2-3句话：整体评估、最大机会、预期影响]

What's Working Well

表现良好的元素

[Bullet list of 3-5 elements that follow CRO best practices]
[3-5个符合CRO最佳实践的元素列表]

Critical Issues (Fix First)

关键问题（优先修复）

Issue 1: [Specific Problem]

问题1：[具体问题]

Principle Violated: [Principle name and number] Current State: [What exists now] Problem: [Why this hurts conversions] Recommendation: [Specific fix] Example:
BEFORE: [Current copy/element]
AFTER: [Recommended copy/element]
Expected Impact: [What improvement to expect]
违反原则： [原则名称及编号] 当前状态： [现有情况] 问题： [为何影响转化] 建议： [具体修复方案] 示例：
BEFORE: [当前文案/元素]
AFTER: [推荐文案/元素]
预期影响： [预期提升效果]

Issue 2: [Specific Problem]

问题2：[具体问题]

[Same structure]
[相同结构]

High-Impact Optimizations

高影响优化项

Optimization 1: [Improvement Area]

优化项1：[改进领域]

Current State: [What exists] Opportunity: [What could be better] Recommendation: [Specific change] Example:
BEFORE: [Current]
AFTER: [Recommended]
Priority: [High/Medium] — [Reasoning]
[Continue for each optimization]
当前状态： [现有情况] 机会： [可改进方向] 建议： [具体修改] 示例：
BEFORE: [当前内容]
AFTER: [推荐内容]
优先级： [高/中] — [理由]
[依次列出每个优化项]

Section-by-Section Analysis

逐节分析

Above the Fold

首屏

  • H1: [Assessment and recommendation if needed]
  • Subheadline: [Assessment and recommendation if needed]
  • CTA: [Assessment and recommendation if needed]
  • Trust signals: [Assessment and recommendation if needed]
  • H1： [评估及必要建议]
  • 副标题： [评估及必要建议]
  • CTA： [评估及必要建议]
  • 信任信号： [评估及必要建议]

[Section Name]

[章节名称]

[Analysis and recommendations]
[Continue for each major section]
[分析及建议]
[依次分析每个主要章节]

Quick Wins (Easy Implementations)

快速优化项（易实施）

  1. [Simple change with good impact]
  2. [Simple change with good impact]
  3. [Simple change with good impact]
  1. [影响良好的简单修改]
  2. [影响良好的简单修改]
  3. [影响良好的简单修改]

Testing Roadmap

测试路线图

  1. Test First: [Highest impact hypothesis]
  2. Test Second: [Next priority]
  3. Test Third: [Following priority]
  1. 优先测试： [最高影响假设]
  2. 次要测试： [次优先级]
  3. 后续测试： [下一个优先级]

Benchmark Comparison

基准对比

Compared to: [Relevant high-converting examples from patterns file] Missing elements: [What top performers have that this page lacks] Adoption opportunities: [Specific patterns to consider implementing]

---
对比对象： [模式文件中相关的高转化示例] 缺失元素： [顶级页面具备但当前页面缺失的元素] 可采用模式： [可考虑实施的具体模式]

---

References

参考文件

All three files MUST be read using the Read tool before analysis (see Step 1):
FilePurpose
./references/cro_principles.md
13 CRO principles with detection criteria, fix patterns, and violation symptoms
./references/landing_page_patterns.md
Real patterns from ClickUp, Notion, Stripe, Apple, Shopify, etc. organized by category
./references/element_audit_framework.md
Systematic framework for auditing H1s, CTAs, forms, social proof, visual hierarchy
Why all three matter: Principles tell you what's wrong. Patterns show you what good looks like. The audit framework ensures you check everything systematically. Together they produce specific, evidence-based recommendations instead of generic CRO advice.
分析前必须使用Read工具读取全部三个文件（见步骤1）：
文件用途
./references/cro_principles.md
13项CRO原则，包含检测标准、修复模式和违规症状
./references/landing_page_patterns.md
来自ClickUp、Notion、Stripe、Apple、Shopify等平台的真实模式，按类别整理
./references/element_audit_framework.md
用于审核H1、CTA、表单、社交证明、视觉层级的系统化框架
三者的重要性： 原则告诉你问题所在，模式展示优秀案例，审核框架确保全面检查。三者结合可产出具体、基于证据的建议，而非通用CRO指导。

Quality Checklist (Self-Verification)

质量检查表（自我验证）

Before finalizing output, verify ALL of the following:
在完成输出前，验证以下所有项：

Pre-Analysis Check

分析前检查

  • I read 
    ./references/cro_principles.md
    before analyzing
  • I read 
    ./references/landing_page_patterns.md
    before analyzing
  • I read 
    ./references/element_audit_framework.md
    before analyzing
  • I have all 13 principles, category patterns, and audit criteria in context
  • 分析前已读取
    ./references/cro_principles.md
  • 分析前已读取
    ./references/landing_page_patterns.md
  • 分析前已读取
    ./references/element_audit_framework.md
  • 已将13项原则、类别模式和审核标准载入上下文

Extraction Check

提取检查

  • I identified the H1 and assessed its clarity
  • I catalogued all CTAs and their copy
  • I noted social proof elements and placement
  • I evaluated above-the-fold content
  • I assessed the section sequence
  • 已识别H1并评估其清晰度
  • 已分类所有CTA及其文案
  • 已记录社交证明元素及布局
  • 已评估首屏内容
  • 已评估章节顺序

Analysis Check

分析检查

  • Each principle was evaluated against the page
  • Issues cite specific principles violated
  • Recommendations include before/after examples
  • Priority is assigned based on conversion impact
  • I compared to relevant high-converting patterns
  • 已针对页面评估每一项原则
  • 问题均引用了具体违反的原则
  • 建议包含前后示例
  • 优先级基于转化影响分配
  • 已与相关高转化模式对比

Output Check

输出检查

  • Executive summary captures key findings
  • Critical issues are listed first
  • Every recommendation is specific and actionable
  • Testing roadmap provides clear next steps
  • "What's working well" section is included
If ANY check fails → revise before presenting.
  • 执行摘要涵盖关键发现
  • 关键问题优先列出
  • 每条建议均具体且可执行
  • 测试路线图提供明确的下一步
  • 包含“表现良好的元素”章节
如果任何一项未通过 → 修改后再提交。

Defaults & Assumptions

默认设置与假设

Use these unless context indicates otherwise:
  • Page type: SaaS landing page (most common)
  • Traffic temperature: Mixed (cold to warm)
  • Primary goal: Signups or demo requests
  • Audience: Business decision-makers
  • Device split: 60% desktop, 40% mobile
  • Conversion definition: Primary CTA click
If the page type is clearly different (e-commerce, content site, etc.), adjust analysis accordingly.
Document any assumptions made in the Executive Summary.
除非上下文另有说明，否则使用以下设置：
  • 页面类型： SaaS着陆页（最常见）
  • 流量热度： 混合（冷流量到暖流量）
  • 主要目标： 注册或演示请求
  • 受众： 企业决策者
  • 设备占比： 60%桌面端，40%移动端
  • 转化定义： 主CTA点击
如果页面类型明显不同（如电商、内容站点等），则相应调整分析方式。
在执行摘要中记录所有做出的假设。