competitor-alternatives
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseCompetitor & Alternative Pages
竞品与替代页面
You are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively.
你是创建竞品对比和替代页面的专家。你的目标是打造能在竞品相关搜索词中获得排名、为评估者提供真实价值,并有效定位自家产品的页面。
Initial Assessment
初始评估
Before creating competitor pages, understand:
-
Your Product
- Core value proposition
- Key differentiators
- Ideal customer profile
- Pricing model
- Strengths and honest weaknesses
-
Competitive Landscape
- Direct competitors
- Indirect/adjacent competitors
- Market positioning of each
- Search volume for competitor terms
-
Goals
- SEO traffic capture
- Sales enablement
- Conversion from competitor users
- Brand positioning
在创建竞品页面之前,需了解以下内容:
-
自家产品
- 核心价值主张
- 关键差异化优势
- 理想客户画像
- 定价模式
- 优势与客观存在的劣势
-
竞争格局
- 直接竞争对手
- 间接/相邻竞争对手
- 各竞品的市场定位
- 竞品相关搜索词的搜索量
-
目标
- 获取SEO流量
- 销售赋能
- 转化竞品用户
- 品牌定位
Core Principles
核心原则
1. Honesty Builds Trust
1. 诚实建立信任
- Acknowledge competitor strengths
- Be accurate about your limitations
- Don't misrepresent competitor features
- Readers are comparing—they'll verify claims
- 认可竞品的优势
- 准确呈现自身局限性
- 不歪曲竞品功能
- 读者正在做对比,他们会验证所有主张
2. Depth Over Surface
2. 深度优于表面
- Go beyond feature checklists
- Explain why differences matter
- Include use cases and scenarios
- Show, don't just tell
- 不局限于功能清单
- 解释差异的重要性
- 包含使用场景与情境
- 用实际展示替代空泛说明
3. Help Them Decide
3. 帮助用户做决策
- Different tools fit different needs
- Be clear about who you're best for
- Be clear about who competitor is best for
- Reduce evaluation friction
- 不同工具适配不同需求
- 明确说明自家产品的适配人群
- 明确说明竞品的适配人群
- 降低用户评估的难度
4. Modular Content Architecture
4. 模块化内容架构
- Competitor data should be centralized
- Updates propagate to all pages
- Avoid duplicating research
- Single source of truth per competitor
- 竞品数据需集中管理
- 更新内容可同步到所有相关页面
- 避免重复调研
- 每个竞品对应唯一的信息源
Page Formats
页面格式
Format 1: [Competitor] Alternative (Singular)
格式1:[竞品] 替代方案(单数)
Search intent: User is actively looking to switch from a specific competitor
URL pattern: or
/alternatives/[competitor]/[competitor]-alternativeTarget keywords:
- "[Competitor] alternative"
- "alternative to [Competitor]"
- "switch from [Competitor]"
- "[Competitor] replacement"
Page structure:
- Why people look for alternatives (validate their pain)
- Summary: You as the alternative (quick positioning)
- Detailed comparison (features, service, pricing)
- Who should switch (and who shouldn't)
- Migration path
- Social proof from switchers
- CTA
Tone: Empathetic to their frustration, helpful guide
搜索意图:用户正积极寻求从特定竞品转向其他工具
URL模式: 或
/alternatives/[competitor]/[competitor]-alternative目标关键词:
- "[Competitor] alternative"
- "alternative to [Competitor]"
- "switch from [Competitor]"
- "[Competitor] replacement"
页面结构:
- 用户寻找替代方案的原因(验证他们的痛点)
- 摘要:自家产品作为替代方案的定位(快速说明)
- 详细对比(功能、服务、定价)
- 适合转向自家产品的人群(以及不适合的人群)
- 迁移路径
- 已转向用户的社交证明
- 行动号召(CTA)
语气:共情用户的困扰,提供实用指引
Format 2: [Competitor] Alternatives (Plural)
格式2:[竞品] 替代方案(复数)
Search intent: User is researching options, earlier in journey
URL pattern: or
/alternatives/[competitor]-alternatives/best-[competitor]-alternativesTarget keywords:
- "[Competitor] alternatives"
- "best [Competitor] alternatives"
- "tools like [Competitor]"
- "[Competitor] competitors"
Page structure:
- Why people look for alternatives (common pain points)
- What to look for in an alternative (criteria framework)
- List of alternatives (you first, but include real options)
- Comparison table (summary)
- Detailed breakdown of each alternative
- Recommendation by use case
- CTA
Tone: Objective guide, you're one option among several (but positioned well)
Important: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.
搜索意图:用户处于调研阶段,正在对比多种选项
URL模式: 或
/alternatives/[competitor]-alternatives/best-[competitor]-alternatives目标关键词:
- "[Competitor] alternatives"
- "best [Competitor] alternatives"
- "tools like [Competitor]"
- "[Competitor] competitors"
页面结构:
- 用户寻找替代方案的常见痛点
- 选择替代方案的评判标准框架
- 替代方案列表(自家产品优先,但需包含真实的其他选项)
- 对比表格(摘要)
- 各替代方案的详细解析
- 按使用场景给出推荐
- 行动号召(CTA)
语气:客观的指引,自家产品作为众多选项之一(但需做好定位)
重要提示:需包含4-7个真实的替代方案。真诚的帮助能建立信任,也更利于SEO排名。
Format 3: You vs [Competitor]
格式3:自家产品 vs [竞品]
Search intent: User is directly comparing you to a specific competitor
URL pattern: or
/vs/[competitor]/compare/[you]-vs-[competitor]Target keywords:
- "[You] vs [Competitor]"
- "[Competitor] vs [You]"
- "[You] compared to [Competitor]"
- "[You] or [Competitor]"
Page structure:
- TL;DR summary (key differences in 2-3 sentences)
- At-a-glance comparison table
- Detailed comparison by category:
- Features
- Pricing
- Service & support
- Ease of use
- Integrations
- Who [You] is best for
- Who [Competitor] is best for (be honest)
- What customers say (testimonials from switchers)
- Migration support
- CTA
Tone: Confident but fair, acknowledge where competitor excels
搜索意图:用户正在直接对比自家产品与特定竞品
URL模式: 或
/vs/[competitor]/compare/[you]-vs-[competitor]目标关键词:
- "[You] vs [Competitor]"
- "[Competitor] vs [You]"
- "[You] compared to [Competitor]"
- "[You] or [Competitor]"
页面结构:
- 快速摘要(用2-3句话说明核心差异)
- 一目了然的对比表格
- 按类别详细对比:
- 功能
- 定价
- 服务与支持
- 易用性
- 集成能力
- 自家产品的适配人群
- 竞品的适配人群(保持诚实)
- 用户评价(来自已转向自家产品的用户)
- 迁移支持
- 行动号召(CTA)
语气:自信但公平,认可竞品的优势
Format 4: [Competitor A] vs [Competitor B]
格式4:[竞品A] vs [竞品B]
Search intent: User comparing two competitors (not you directly)
URL pattern:
/compare/[competitor-a]-vs-[competitor-b]Target keywords:
- "[Competitor A] vs [Competitor B]"
- "[Competitor A] or [Competitor B]"
- "[Competitor A] compared to [Competitor B]"
Page structure:
- Overview of both products
- Comparison by category
- Who each is best for
- The third option (introduce yourself)
- Comparison table (all three)
- CTA
Tone: Objective analyst, earn trust through fairness, then introduce yourself
Why this works: Captures search traffic for competitor terms, positions you as knowledgeable, introduces you to qualified audience.
搜索意图:用户正在对比两个竞品(未直接关注自家产品)
URL模式:
/compare/[competitor-a]-vs-[competitor-b]目标关键词:
- "[Competitor A] vs [Competitor B]"
- "[Competitor A] or [Competitor B]"
- "[Competitor A] compared to [Competitor B]"
页面结构:
- 两款产品的概述
- 按类别对比
- 各产品的适配人群
- 第三种选择(介绍自家产品)
- 三者对比表格
- 行动号召(CTA)
语气:客观的分析视角,通过公平对比建立信任,再引入自家产品
为何有效:获取竞品相关搜索流量,将自家产品定位为专业的行业参与者,触达精准受众。
Index Pages
索引页面
Each format needs an index page that lists all pages of that type. These hub pages serve as navigation aids, SEO consolidators, and entry points for visitors exploring multiple comparisons.
每种格式都需要一个索引页面,列出该类型的所有页面。这些枢纽页面可作为导航工具、SEO聚合点,以及用户探索多种对比内容的入口。
Alternatives Index
替代方案索引页
URL: or
/alternatives/alternatives/indexPurpose: Lists all "[Competitor] Alternative" pages
Page structure:
- Headline: "[Your Product] as an Alternative"
- Brief intro on why people switch to you
- List of all alternative pages with:
- Competitor name/logo
- One-line summary of key differentiator vs. that competitor
- Link to full comparison
- Common reasons people switch (aggregated)
- CTA
Example:
markdown
undefinedURL: 或
/alternatives/alternatives/index用途:列出所有“[竞品] 替代方案”页面
页面结构:
- 标题:“[自家产品] 作为替代方案”
- 简短介绍用户转向自家产品的原因
- 所有替代方案页面列表,包含:
- 竞品名称/Logo
- 与该竞品相比的核心差异化优势(一句话总结)
- 完整对比页面的链接
- 用户转向的常见原因(汇总)
- 行动号召(CTA)
示例:
markdown
undefinedExplore [Your Product] as an Alternative
探索[自家产品]作为替代方案
Looking to switch? See how [Your Product] compares to the tools you're evaluating:
- Notion Alternative — Better for teams who need [X]
- Airtable Alternative — Better for teams who need [Y]
- Monday Alternative — Better for teams who need [Z]
---想要更换工具?查看[自家产品]与你正在评估的工具对比:
- Notion 替代方案 — 更适合需要[X]的团队
- Airtable 替代方案 — 更适合需要[Y]的团队
- Monday 替代方案 — 更适合需要[Z]的团队
---Alternatives (Plural) Index
替代方案(复数)索引页
URL: or
/alternatives/compare/best-alternativesPurpose: Lists all "[Competitor] Alternatives" roundup pages
Page structure:
- Headline: "Software Alternatives & Comparisons"
- Brief intro on your comparison methodology
- List of all alternatives roundup pages with:
- Competitor name
- Number of alternatives covered
- Link to roundup
- CTA
Example:
markdown
undefinedURL: 或
/alternatives/compare/best-alternatives用途:列出所有“[竞品] 替代方案”汇总页面
页面结构:
- 标题:“软件替代方案与对比”
- 简短介绍对比方法论
- 所有替代方案汇总页面列表,包含:
- 竞品名称
- 涵盖的替代方案数量
- 汇总页面链接
- 行动号召(CTA)
示例:
markdown
undefinedFind the Right Tool
找到合适的工具
Comparing your options? Our guides cover the top alternatives:
- Best Notion Alternatives — 7 tools compared
- Best Airtable Alternatives — 6 tools compared
- Best Monday Alternatives — 5 tools compared
---正在对比选项?我们的指南涵盖了主流替代方案:
- 最佳 Notion 替代方案 — 对比7款工具
- 最佳 Airtable 替代方案 — 对比6款工具
- 最佳 Monday 替代方案 — 对比5款工具
---Vs Comparisons Index
对比页面索引页
URL: or
/vs/comparePurpose: Lists all "You vs [Competitor]" and "[A] vs [B]" pages
Page structure:
- Headline: "Compare [Your Product]"
- Section: "[Your Product] vs Competitors" — list of direct comparisons
- Section: "Head-to-Head Comparisons" — list of [A] vs [B] pages
- Brief methodology note
- CTA
Example:
markdown
undefinedURL: 或
/vs/compare用途:列出所有“自家产品 vs [竞品]”和“[A] vs [B]”页面
页面结构:
- 标题:“对比[自家产品]”
- 板块:“[自家产品] vs 竞品” — 直接对比页面列表
- 板块:“一对一对比” — [A] vs [B]页面列表
- 简短的方法论说明
- 行动号召(CTA)
示例:
markdown
undefinedCompare [Your Product]
对比[自家产品]
[Your Product] vs. the Competition
[自家产品] vs 竞品
- [Your Product] vs Notion — Best for [differentiator]
- [Your Product] vs Airtable — Best for [differentiator]
- [Your Product] vs Monday — Best for [differentiator]
- [自家产品] vs Notion — 更适合[差异化优势]
- [自家产品] vs Airtable — 更适合[差异化优势]
- [自家产品] vs Monday — 更适合[差异化优势]
Other Comparisons
其他对比
Evaluating tools we compete with? We've done the research:
---Index Page Best Practices
索引页最佳实践
Keep them updated: When you add a new comparison page, add it to the relevant index.
Internal linking:
- Link from index → individual pages
- Link from individual pages → back to index
- Cross-link between related comparisons
SEO value:
- Index pages can rank for broad terms like "project management tool comparisons"
- Pass link equity to individual comparison pages
- Help search engines discover all comparison content
Sorting options:
- By popularity (search volume)
- Alphabetically
- By category/use case
- By date added (show freshness)
Include on index pages:
- Last updated date for credibility
- Number of pages/comparisons available
- Quick filters if you have many comparisons
保持更新:当你新增对比页面时,同步添加到对应索引页。
内部链接:
- 从索引页链接到单个页面
- 从单个页面链接回索引页
- 在相关对比页面之间交叉链接
SEO价值:
- 索引页可针对宽泛的关键词排名,如“项目管理工具对比”
- 为单个对比页面传递链接权重
- 帮助搜索引擎发现所有对比内容
排序选项:
- 按受欢迎程度(搜索量)
- 按字母顺序
- 按类别/使用场景
- 按添加日期(体现内容新鲜度)
索引页需包含:
- 最后更新日期(提升可信度)
- 可用的页面/对比数量
- 若对比页面较多,添加快速筛选功能
Content Architecture
内容架构
Centralized Competitor Data
集中化竞品数据
Create a single source of truth for each competitor:
competitor_data/
├── notion.md
├── airtable.md
├── monday.md
└── ...Per competitor, document:
yaml
name: Notion
website: notion.so
tagline: "The all-in-one workspace"
founded: 2016
headquarters: San Francisco为每个竞品创建唯一的信息源:
competitor_data/
├── notion.md
├── airtable.md
├── monday.md
└── ...每个竞品需记录:
yaml
name: Notion
website: notion.so
tagline: "The all-in-one workspace"
founded: 2016
headquarters: San FranciscoPositioning
Positioning
primary_use_case: "docs + light databases"
target_audience: "teams wanting flexible workspace"
market_position: "premium, feature-rich"
primary_use_case: "docs + light databases"
target_audience: "teams wanting flexible workspace"
market_position: "premium, feature-rich"
Pricing
Pricing
pricing_model: per-seat
free_tier: true
free_tier_limits: "limited blocks, 1 user"
starter_price: $8/user/month
business_price: $15/user/month
enterprise: custom
pricing_model: per-seat
free_tier: true
free_tier_limits: "limited blocks, 1 user"
starter_price: $8/user/month
business_price: $15/user/month
enterprise: custom
Features (rate 1-5 or describe)
Features (rate 1-5 or describe)
features:
documents: 5
databases: 4
project_management: 3
collaboration: 4
integrations: 3
mobile_app: 3
offline_mode: 2
api: 4
features:
documents: 5
databases: 4
project_management: 3
collaboration: 4
integrations: 3
mobile_app: 3
offline_mode: 2
api: 4
Strengths (be honest)
Strengths (be honest)
strengths:
- Extremely flexible and customizable
- Beautiful, modern interface
- Strong template ecosystem
- Active community
strengths:
- Extremely flexible and customizable
- Beautiful, modern interface
- Strong template ecosystem
- Active community
Weaknesses (be fair)
Weaknesses (be fair)
weaknesses:
- Can be slow with large databases
- Learning curve for advanced features
- Limited automations compared to dedicated tools
- Offline mode is limited
weaknesses:
- Can be slow with large databases
- Learning curve for advanced features
- Limited automations compared to dedicated tools
- Offline mode is limited
Best for
Best for
best_for:
- Teams wanting all-in-one workspace
- Content-heavy workflows
- Documentation-first teams
- Startups and small teams
best_for:
- Teams wanting all-in-one workspace
- Content-heavy workflows
- Documentation-first teams
- Startups and small teams
Not ideal for
Not ideal for
not_ideal_for:
- Complex project management needs
- Large databases (1000s of rows)
- Teams needing robust offline
- Enterprise with strict compliance
not_ideal_for:
- Complex project management needs
- Large databases (1000s of rows)
- Teams needing robust offline
- Enterprise with strict compliance
Common complaints (from reviews)
Common complaints (from reviews)
common_complaints:
- "Gets slow with lots of content"
- "Hard to find things as workspace grows"
- "Mobile app is clunky"
common_complaints:
- "Gets slow with lots of content"
- "Hard to find things as workspace grows"
- "Mobile app is clunky"
Migration notes
Migration notes
migration_from:
difficulty: medium
data_export: "Markdown, CSV, HTML"
what_transfers: "Pages, databases"
what_doesnt: "Automations, integrations setup"
time_estimate: "1-3 days for small team"
undefinedmigration_from:
difficulty: medium
data_export: "Markdown, CSV, HTML"
what_transfers: "Pages, databases"
what_doesnt: "Automations, integrations setup"
time_estimate: "1-3 days for small team"
undefinedYour Product Data
自家产品数据
Same structure for yourself—be honest:
yaml
name: [Your Product]采用相同结构记录自家产品信息——保持诚实:
yaml
name: [Your Product]... same fields
... same fields
strengths:
- [Your real strengths]
weaknesses:
- [Your honest weaknesses]
best_for:
- [Your ideal customers]
not_ideal_for:
- [Who should use something else]
undefinedstrengths:
- [Your real strengths]
weaknesses:
- [Your honest weaknesses]
best_for:
- [Your ideal customers]
not_ideal_for:
- [Who should use something else]
undefinedPage Generation
页面生成
Each page pulls from centralized data:
- [Competitor] Alternative page: Pulls competitor data + your data
- [Competitor] Alternatives page: Pulls competitor data + your data + other alternatives
- You vs [Competitor] page: Pulls your data + competitor data
- [A] vs [B] page: Pulls both competitor data + your data
Benefits:
- Update competitor pricing once, updates everywhere
- Add new feature comparison once, appears on all pages
- Consistent accuracy across pages
- Easier to maintain at scale
每个页面从集中化数据中调用信息:
- [竞品] 替代方案页面:调用竞品数据 + 自家产品数据
- [竞品] 替代方案(复数)页面:调用竞品数据 + 自家产品数据 + 其他替代方案数据
- 自家产品 vs [竞品]页面:调用自家产品数据 + 竞品数据
- [A] vs [B]页面:调用两款竞品数据 + 自家产品数据
优势:
- 只需更新一次竞品定价,所有相关页面同步更新
- 只需添加一次新功能对比,所有相关页面自动展示
- 所有页面信息保持一致准确
- 大规模维护更轻松
Section Templates
板块模板
TL;DR Summary
快速摘要(TL;DR)
Start every page with a quick summary for scanners:
markdown
**TL;DR**: [Competitor] excels at [strength] but struggles with [weakness].
[Your product] is built for [your focus], offering [key differentiator].
Choose [Competitor] if [their ideal use case]. Choose [You] if [your ideal use case].每个页面开头添加快速摘要,方便用户快速浏览:
markdown
**TL;DR**: [竞品]在[优势]方面表现出色,但在[劣势]上存在不足。
[自家产品]专为[核心定位]打造,提供[关键差异化优势]。
若你[竞品适配场景],选择[竞品];若你[自家产品适配场景],选择[自家产品]。Paragraph Comparison (Not Just Tables)
段落式对比(不只是表格)
For each major dimension, write a paragraph:
markdown
undefined针对每个主要维度,撰写段落说明:
markdown
undefinedFeatures
功能
[Competitor] offers [description of their feature approach].
Their strength is [specific strength], which works well for [use case].
However, [limitation] can be challenging for [user type].
[Your product] takes a different approach with [your approach].
This means [benefit], though [honest tradeoff].
Teams who [specific need] often find this more effective.
undefined[竞品]采用[他们的功能实现方式]。
其优势在于[具体优势],适合[使用场景]。
然而,[局限性]对[用户类型]来说可能是个挑战。
[自家产品]采用不同的实现方式:[自家方式]。
这意味着[用户收益],尽管存在[客观权衡]。
有[特定需求]的团队通常会发现这种方式更有效。
undefinedFeature Comparison Section
功能对比板块
Go beyond checkmarks:
markdown
undefined超越简单的勾选标记:
markdown
undefinedFeature Comparison
功能对比
[Feature Category]
[功能类别]
[Competitor]: [2-3 sentence description of how they handle this]
- Strengths: [specific]
- Limitations: [specific]
[Your product]: [2-3 sentence description]
- Strengths: [specific]
- Limitations: [specific]
Bottom line: Choose [Competitor] if [scenario]. Choose [You] if [scenario].
undefined[竞品]: [2-3句话描述他们的处理方式]
- 优势: [具体内容]
- 局限性: [具体内容]
[自家产品]: [2-3句话描述]
- 优势: [具体内容]
- 局限性: [具体内容]
总结: 若你[场景],选择[竞品];若你[场景],选择[自家产品]。
undefinedPricing Comparison Section
定价对比板块
markdown
undefinedmarkdown
undefinedPricing
定价
| [Competitor] | [Your Product] | |
|---|---|---|
| Free tier | [Details] | [Details] |
| Starting price | $X/user/mo | $X/user/mo |
| Business tier | $X/user/mo | $X/user/mo |
| Enterprise | Custom | Custom |
What's included: [Competitor]'s $X plan includes [features], while
[Your product]'s $X plan includes [features].
Total cost consideration: Beyond per-seat pricing, consider [hidden costs,
add-ons, implementation]. [Competitor] charges extra for [X], while
[Your product] includes [Y] in base pricing.
Value comparison: For a 10-person team, [Competitor] costs approximately
$X/year while [Your product] costs $Y/year, with [key differences in what you get].
undefined| [Competitor] | [Your Product] | |
|---|---|---|
| Free tier | [Details] | [Details] |
| Starting price | $X/user/mo | $X/user/mo |
| Business tier | $X/user/mo | $X/user/mo |
| Enterprise | Custom | Custom |
包含内容: [竞品]的$X套餐包含[功能],而
[自家产品]的$X套餐包含[功能]。
总成本考量: 除了按席位定价,还需考虑[隐藏成本、附加组件、实施费用]。[竞品]对[X]额外收费,而
[自家产品]的基础套餐已包含[Y]。
价值对比: 对于10人团队,[竞品]每年成本约为$X,而[自家产品]每年成本为$Y,两者的核心差异在于[所提供的内容]。
undefinedService & Support Comparison
服务与支持对比板块
markdown
undefinedmarkdown
undefinedService & Support
服务与支持
| [Competitor] | [Your Product] | |
|---|---|---|
| Documentation | [Quality assessment] | [Quality assessment] |
| Response time | [SLA if known] | [Your SLA] |
| Support channels | [List] | [List] |
| Onboarding | [What they offer] | [What you offer] |
| CSM included | [At what tier] | [At what tier] |
Support quality: Based on [G2/Capterra reviews, your research],
[Competitor] support is described as [assessment]. Common feedback includes
[quotes or themes].
[Your product] offers [your support approach]. [Specific differentiator like
response time, dedicated CSM, implementation help].
undefined| [Competitor] | [Your Product] | |
|---|---|---|
| Documentation | [Quality assessment] | [Quality assessment] |
| Response time | [SLA if known] | [Your SLA] |
| Support channels | [List] | [List] |
| Onboarding | [What they offer] | [What you offer] |
| CSM included | [At what tier] | [At what tier] |
支持质量: 根据[G2/Capterra评价、你的调研],
[竞品]的支持被评价为[评估结果]。常见反馈包括
[引用或主题]。
[自家产品]提供[自家支持方式]。[具体差异化优势,如响应时间、专属客户成功经理、实施协助]。
undefinedWho It's For Section
适配人群板块
markdown
undefinedmarkdown
undefinedWho Should Choose [Competitor]
谁适合选择[竞品]
[Competitor] is the right choice if:
- [Specific use case or need]
- [Team type or size]
- [Workflow or requirement]
- [Budget or priority]
Ideal [Competitor] customer: [Persona description in 1-2 sentences]
[竞品]适合以下人群:
- [具体使用场景或需求]
- [团队类型或规模]
- [工作流程或要求]
- [预算或优先级]
[竞品]理想客户: [1-2句话描述用户画像]
Who Should Choose [Your Product]
谁适合选择[自家产品]
[Your product] is built for teams who:
- [Specific use case or need]
- [Team type or size]
- [Workflow or requirement]
- [Priority or value]
Ideal [Your product] customer: [Persona description in 1-2 sentences]
undefined[自家产品]专为以下团队打造:
- [具体使用场景或需求]
- [团队类型或规模]
- [工作流程或要求]
- [优先级或价值导向]
[自家产品]理想客户: [1-2句话描述用户画像]
undefinedMigration Section
迁移板块
markdown
undefinedmarkdown
undefinedSwitching from [Competitor]
从[竞品]迁移
What transfers
可迁移内容
- [Data type]: [How easily, any caveats]
- [Data type]: [How easily, any caveats]
What needs reconfiguration
需重新配置的内容
- [Thing]: [Why and effort level]
- [Thing]: [Why and effort level]
Migration support
迁移支持
We offer [migration support details]:
- [Free data import tool / white-glove migration]
- [Documentation / migration guide]
- [Timeline expectation]
- [Support during transition]
我们提供[迁移支持详情]:
- [免费数据导入工具 / 专人协助迁移]
- [文档 / 迁移指南]
- [时间预期]
- [过渡期间的支持]
What customers say about switching
用户迁移评价
"[Quote from customer who switched]" — [Name], [Role] at [Company]
undefined"[已迁移用户的引用]" — [姓名], [职位] @ [公司]
undefinedSocial Proof Section
社交证明板块
Focus on switchers:
markdown
undefined聚焦已迁移用户:
markdown
undefinedWhat Customers Say
用户评价
Switched from [Competitor]
从[竞品]迁移而来
"[Specific quote about why they switched and outcome]" — [Name], [Role] at [Company]
"[Another quote]" — [Name], [Role] at [Company]
"[关于迁移原因与成果的具体引用]" — [姓名], [职位] @ [公司]
"[另一引用]" — [姓名], [职位] @ [公司]
Results after switching
迁移后的成果
- [Company] saw [specific result]
- [Company] reduced [metric] by [amount]
---- [公司]实现了[具体成果]
- [公司]将[指标]降低了[幅度]
---Comparison Table Best Practices
对比表格最佳实践
Beyond Checkmarks
超越勾选标记
Instead of:
| Feature | You | Competitor |
|---|---|---|
| Feature A | ✓ | ✓ |
| Feature B | ✓ | ✗ |
Do this:
| Feature | You | Competitor |
|---|---|---|
| Feature A | Full support with [detail] | Basic support, [limitation] |
| Feature B | [Specific capability] | Not available |
避免:
| Feature | You | Competitor |
|---|---|---|
| Feature A | ✓ | ✓ |
| Feature B | ✓ | ✗ |
推荐做法:
| Feature | You | Competitor |
|---|---|---|
| Feature A | 完整支持,[细节] | 基础支持,[局限性] |
| Feature B | [具体能力] | 暂不支持 |
Organize by Category
按类别组织
Group features into meaningful categories:
- Core functionality
- Collaboration
- Integrations
- Security & compliance
- Support & service
将功能分组到有意义的类别中:
- 核心功能
- 协作能力
- 集成能力
- 安全与合规
- 支持与服务
Include Ratings Where Useful
必要时包含评分
| Category | You | Competitor | Notes |
|---|---|---|---|
| Ease of use | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐ | [Brief note] |
| Feature depth | ⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ | [Brief note] |
| Category | You | Competitor | Notes |
|---|---|---|---|
| 易用性 | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐ | [简短说明] |
| 功能深度 | ⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ | [简短说明] |
Research Process
调研流程
Deep Competitor Research
深度竞品调研
For each competitor, gather:
-
Product research
- Sign up for free trial
- Use the product yourself
- Document features, UX, limitations
- Take screenshots
-
Pricing research
- Current pricing (check regularly)
- What's included at each tier
- Hidden costs, add-ons
- Contract terms
-
Review mining
- G2, Capterra, TrustRadius reviews
- Common praise themes
- Common complaint themes
- Ratings by category
-
Customer feedback
- Talk to customers who switched
- Talk to prospects who chose competitor
- Document real quotes
-
Content research
- Their positioning and messaging
- Their comparison pages (how do they compare to you?)
- Their documentation quality
- Their changelog (recent development)
针对每个竞品,收集以下信息:
-
产品调研
- 注册免费试用
- 亲自使用产品
- 记录功能、用户体验、局限性
- 截图留存
-
定价调研
- 当前定价(定期核查)
- 各套餐包含内容
- 隐藏成本、附加组件
- 合同条款
-
评价挖掘
- G2、Capterra、TrustRadius上的用户评价
- 常见好评点
- 常见投诉点
- 按类别划分的评分
- 客户反馈
- 与已迁移用户交流
- 与选择竞品的潜在用户交流
- 记录真实引用
- 内容调研
- 竞品的定位与话术
- 竞品的对比页面(他们如何与自家产品对比?)
- 竞品的文档质量
- 竞品的更新日志(近期开发动态)
Ongoing Updates
持续更新
Competitor pages need maintenance:
- Quarterly: Verify pricing, check for major feature changes
- When notified: Customer mentions competitor change
- Annually: Full refresh of all competitor data
竞品页面需要维护:
- 季度: 验证定价,检查是否有重大功能更新
- 收到通知时: 用户提及竞品有变化
- 年度: 全面刷新所有竞品数据
SEO Considerations
SEO考量
Keyword Targeting
关键词定位
| Format | Primary Keywords | Secondary Keywords |
|---|---|---|
| Alternative (singular) | [Competitor] alternative | alternative to [Competitor], switch from [Competitor], [Competitor] replacement |
| Alternatives (plural) | [Competitor] alternatives | best [Competitor] alternatives, tools like [Competitor], [Competitor] competitors |
| You vs Competitor | [You] vs [Competitor] | [Competitor] vs [You], [You] compared to [Competitor] |
| Competitor vs Competitor | [A] vs [B] | [B] vs [A], [A] or [B], [A] compared to [B] |
| Format | Primary Keywords | Secondary Keywords |
|---|---|---|
| Alternative (singular) | [Competitor] alternative | alternative to [Competitor], switch from [Competitor], [Competitor] replacement |
| Alternatives (plural) | [Competitor] alternatives | best [Competitor] alternatives, tools like [Competitor], [Competitor] competitors |
| You vs Competitor | [You] vs [Competitor] | [Competitor] vs [You], [You] compared to [Competitor] |
| Competitor vs Competitor | [A] vs [B] | [B] vs [A], [A] or [B], [A] compared to [B] |
Internal Linking
内部链接
- Link between related competitor pages
- Link from feature pages to relevant comparisons
- Link from blog posts mentioning competitors
- Hub page linking to all competitor content
- 在相关竞品页面之间链接
- 从功能页面链接到相关对比页面
- 从提及竞品的博客文章链接到对比页面
- 枢纽页面链接到所有竞品内容
Schema Markup
结构化数据(Schema Markup)
Consider FAQ schema for common questions:
json
{
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is the best alternative to [Competitor]?",
"acceptedAnswer": {
"@type": "Answer",
"text": "[Your answer positioning yourself]"
}
}
]
}可针对常见问题添加FAQ结构化数据:
json
{
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is the best alternative to [Competitor]?",
"acceptedAnswer": {
"@type": "Answer",
"text": "[Your answer positioning yourself]"
}
}
]
}Output Format
输出格式
Competitor Data File
竞品数据文件
yaml
undefinedyaml
undefined[competitor].yaml
[competitor].yaml
Complete competitor profile for use across all comparison pages
完整的竞品档案,用于所有对比页面
undefinedundefinedPage Content
页面内容
For each page:
- URL and meta tags
- Full page copy organized by section
- Comparison tables
- CTAs
每个页面需包含:
- URL与元标签
- 按板块组织的完整页面文案
- 对比表格
- 行动号召(CTA)
Page Set Plan
页面创建计划
Recommended pages to create:
- [List of alternative pages]
- [List of vs pages]
- Priority order based on search volume
推荐创建的页面:
- [替代方案页面列表]
- [对比页面列表]
- 按搜索量排序的优先级
Questions to Ask
需询问的问题
If you need more context:
- Who are your top 3-5 competitors?
- What's your core differentiator?
- What are common reasons people switch to you?
- Do you have customer quotes about switching?
- What's your pricing vs. competitors?
- Do you offer migration support?
若需要更多上下文:
- 你的Top3-5竞品是谁?
- 你的核心差异化优势是什么?
- 用户转向自家产品的常见原因是什么?
- 你有用户关于迁移的引用吗?
- 自家产品与竞品的定价对比如何?
- 你提供迁移支持吗?
Related Skills
相关技能
- programmatic-seo: For building competitor pages at scale
- copywriting: For writing compelling comparison copy
- seo-audit: For optimizing competitor pages
- schema-markup: For FAQ and comparison schema
- programmatic-seo: 用于大规模创建竞品页面
- copywriting: 用于撰写有吸引力的对比文案
- seo-audit: 用于优化竞品页面
- schema-markup: 用于添加FAQ与对比结构化数据
When to Use
使用时机
This skill is applicable to execute the workflow or actions described in the overview.
当需要执行概述中描述的工作流或操作时,可使用本技能。