use-cases-page-generator

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Pages: Use Cases

页面：用例

Guides use case pages that bridge product features and real-world customer problems. Scenario-first is the primary organization. BOFU (bottom-of-funnel) pages for SaaS/B2B. Answer "when would I use it?" and "how does it help me?" — distinct from solutions (industry/outcome).

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.

指导搭建连接产品功能与真实客户问题的用例页面，场景优先是核心组织原则。适用于SaaS/B2B的BOFU（漏斗底部）页面，回答“我什么时候需要用它？”和“它能帮我解决什么问题？”，与解决方案页（按行业/产出划分）有明确区分。

调用规则：首次调用时，如果合适，可以先用1-2句话介绍本技能覆盖的范围及价值，再输出核心内容。后续调用或用户要求跳过介绍时，直接输出核心内容即可。

Initial Assessment

初步评估

Check for product marketing context first: If

.claude/product-marketing-context.md

.cursor/product-marketing-context.md

exists, read it for product, ICP, and proof points.

Identify:

Scenarios: Concrete situations (event marketing, lead nurturing)
Personas: Roles (Marketer, Sales Rep, Realtor)
Business goals: Acquisition, Retention, Upsell
Format: Single page vs. per-use-case pages; standalone or under solutions
Primary goal: Demo, sign up, contact sales

优先检查产品营销上下文：如果存在

.claude/product-marketing-context.md

或

.cursor/product-marketing-context.md

文件，先读取文件中的产品、ICP、佐证点等信息。

需明确以下信息：

场景：具体使用场景（例如活动营销、线索培育）
用户画像：目标角色（营销人员、销售代表、房产经纪人）
业务目标：获客、留存、增购
呈现形式：单页汇总vs分用例单独页面；独立页面或归属在解决方案页下
核心转化目标：演示、注册、联系销售

Use Case Page Structure

用例页面结构

Section	Purpose
Headline	"When you need to X, we help you Y" or "For [role]: solve X"
Problem	Pain points, day-to-day challenges
Solution	How product addresses them; link to relevant features (do not duplicate feature copy)
Proof	Case study, testimonial, metrics
CTA	Try free, book demo, contact
Related	Link to other use cases, parent solution

模块	作用
标题	采用“当你需要实现X时，我们帮你完成Y”或“面向[角色]：解决X问题”的结构
问题	阐述痛点、日常工作中的挑战
解决方案	说明产品如何解决这些问题，关联对应的功能（不要复制功能页的文案）
佐证	案例研究、客户证言、数据指标
CTA	免费试用、预约演示、联系我们
相关内容	链接到其他用例、父级解决方案页

Best Practices

最佳实践

Scenario-First

场景优先

Concrete situations: "When you need to run event marketing at scale..."
Before-after: Show transformation, not just features
One scenario per page: Don't mix "event marketing" and "lead nurturing"

具象场景：例如“当你需要规模化开展活动营销时…”
前后对比：展示带来的转变，而不仅仅是罗列功能
每页仅覆盖一个场景：不要把“活动营销”和“线索培育”放在同一页面

Content Differentiation (vs Features)

内容差异化（与功能页的区别）

Use case = scenario + problem + outcome: Write the story (when, who, why, result); reference features via links.
Do not duplicate feature copy: Avoid repeating capability lists or benefit bullets from the features page; instead, describe how the product solves this scenario and link to /features for details.
Avoid content cannibalization: Each use case page targets a unique scenario intent; overlap with features (both Commercial/Consideration) dilutes SEO — differentiate by content angle (scenario vs capability).

用例 = 场景 + 问题 + 结果：讲述完整故事（时间、用户、原因、结果），通过链接跳转至功能详情
不要复制功能页文案：避免重复功能页的能力列表或收益要点，转而描述产品如何解决当前场景的问题，将详情跳转至/features页面
避免内容 cannibalization（内容互斥）：每个用例页对应唯一的场景搜索意图，与功能页（商业/考虑阶段）的内容重叠会削弱SEO效果，要通过内容角度（场景vs能力）做出区分

Organization (Primary → Secondary)

页面组织逻辑（优先级从高到低）

Dimension	Priority	Examples
By Scenario	Primary	Event marketing, Lead nurturing, Churn prevention, Customer onboarding
By Persona/Role	Primary	For Realtors, For CMOs, For Sales Reps
By Business Goal	Secondary	Acquisition, Retention, Upsell/Cross-sell
By Industry	Secondary (ICP)	Use as ICP tag; or as sub-page under Solutions

维度	优先级	示例
按场景划分	最高	活动营销、线索培育、流失预防、客户入职
按用户画像/角色划分	最高	面向房产经纪人、面向CMO、面向销售代表
按业务目标划分	次要	获客、留存、增购/交叉销售
按行业划分	次要（ICP维度）	作为ICP标签使用，或作为解决方案页的子页面

Scenario Examples

场景示例

Event marketing, Lead nurturing, Churn prevention, Customer onboarding, Patient scheduling, Telemedicine, Inventory management, Demand forecasting.

活动营销、线索培育、流失预防、客户入职、患者预约、远程医疗、库存管理、需求预测。

Business Goal Examples

业务目标示例

Acquisition (signups, trials), Retention (reduce churn, re-engagement), Upsell/Cross-sell (expand revenue).

获客（注册、试用）、留存（降低流失、重新激活）、增购/交叉销售（提升营收）。

vs. Solutions vs. Features

用例页 vs 解决方案页 vs 功能页

Page	Answers	Primary Organization
Features	What does it do?	Capabilities
Solutions	What outcome do I get?	By industry, company size, team
Use cases	When would I use it?	By scenario, persona, business goal

Hierarchy: Use cases can be standalone or sub-pages under Solutions. Example: /solutions/healthcare/patient-scheduling (use case under industry solution).

页面类型	回答的问题	核心组织逻辑
功能页	它能做什么？	按能力划分
解决方案页	我能得到什么结果？	按行业、公司规模、团队划分
用例页	我什么时候需要用它？	按场景、用户画像、业务目标划分

层级关系：用例页可以是独立页面，也可以作为解决方案页的子页面。示例：/solutions/healthcare/patient-scheduling（行业解决方案下的用例子页）

When to Use Use Cases vs Solutions

用例页与解决方案页的适用场景

Need	Use
By scenario (Event marketing)	Use Cases
By persona (For Realtors, For CMOs)	Use Cases
By business goal (Acquisition, Retention)	Use Cases
By industry	Solutions
By company size (SMB, Enterprise)	Solutions
By team (Marketing, Sales)	Solutions
Industry-specific application	Use Cases (as Solutions sub-page)

需求	选用页面类型
按场景划分（活动营销）	用例页
按用户画像划分（面向房产经纪人、面向CMO）	用例页
按业务目标划分（获客、留存）	用例页
按行业划分	解决方案页
按公司规模划分（中小微企业、企业级）	解决方案页
按团队划分（营销、销售）	解决方案页
特定行业场景应用	用例页（作为解决方案页的子页面）

Internal Linking

内链规则

Use cases ↔ features ↔ solutions ↔ customer stories
If under a solution: link to parent solution; parent links to use cases

用例页 ↔ 功能页 ↔ 解决方案页 ↔ 客户案例页相互关联
如果用例页归属在某个解决方案下：链接到父级解决方案页，父级页面也要链接到对应的用例页

SEO

SEO规则

Intent: Commercial; "X software for [scenario]" or "[Product] for [role]"
Title: "When to Use [Product] for [Scenario]" or "[Product] for [Role]"
Differentiate: Unique workflows, pain points per scenario/persona

搜索意图：商业意图；匹配“[场景]对应的X软件”或“面向[角色]的[产品]”这类搜索词
标题：“什么时候用[产品]解决[场景]问题”或“面向[角色]的[产品]”
差异化：每个场景/用户画像对应的工作流、痛点都要做到独特，避免重复

Output Format

输出格式

Use case list (scenarios/personas to cover)
Per-page structure (sections, messaging)
Headline options per segment
Internal linking plan (including parent solution if applicable)
SEO metadata

用例列表（需要覆盖的场景/用户画像）
单页结构（模块、内容要点）
各细分板块的标题选项
内链规划（如果适用，包含父级解决方案页的链接）
SEO元数据