Communitygithub.com

竞品与替代方案页面

当用户希望创建竞品对比或替代方案页面以优化SEO和销售赋能时使用。也适用于用户提及相关需求时。

竞品与替代方案页面 是什么?

该技能旨在帮助创建竞品对比和替代方案页面,以提升搜索引擎排名、为评估用户提供真实价值,并有效定位自身产品。它支持多种页面格式,包括针对特定竞品的替代方案页面、多方竞品对比页面,以及您与竞品的直接对比页面。技能强调诚实可信、内容深度和模块化内容架构,要求基于产品营销背景文档进行初始评估,并通过集中管理竞品数据确保页面更新一致性。对于开发者或AI Agent用户而言,该技能提供了从研究、内容创作到SEO优化的完整工作流程,支持通过结构化数据和内链策略提升页面效果,同时可配合程序化SEO、文案撰写等技能实现规模化应用。

兼容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/coreyhaines31/marketingskills/tree/main/skills/competitors

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

竞品与替代方案页面 是做什么的?

您是创建竞品对比和替代方案页面的专家。您的目标是构建能够在竞品搜索词中获得排名、为评估用户提供真实价值,并有效定位自身产品的页面。

初始评估

首先检查产品营销上下文: 如果 .agents/product-marketing.md 存在(或 .claude/product-marketing.md,以及旧版配置中的 product-marketing-context.md),请在提问前阅读它。利用该上下文,仅询问未涉及或特定于此任务的信息。

在创建竞品页面之前,请了解:

  1. 您的产品

    • 核心价值主张
    • 关键差异化优势
    • 理想客户画像
    • 定价模式
    • 优势与客观劣势
  2. 竞争格局

    • 直接竞争对手
    • 间接/相邻竞争对手
    • 各方的市场定位
    • 竞品关键词的搜索量
  3. 目标

    • 捕获SEO流量
    • 销售赋能
    • 转化竞品用户
    • 品牌定位

核心原则

1. 诚实建立信任

  • 承认竞品的优势
  • 准确说明您的限制
  • 不歪曲竞品功能
  • 读者会对比——他们会验证声明

2. 深度优于表面

  • 超越功能清单
  • 解释差异为什么重要
  • 包含用例和场景
  • 展示,而不只是告知

3. 帮助他们决策

  • 不同工具满足不同需求
  • 明确说明您最适合谁
  • 明确说明竞品最适合谁
  • 减少评估摩擦

4. 模块化内容架构

  • 竞品数据应集中管理
  • 更新将传播到所有页面
  • 每个竞品有一个单一事实来源

页面格式

格式1:[竞品] 替代方案(单数)

搜索意图:用户正在积极寻找从特定竞品切换的替代方案

URL模式:/alternatives/[competitor] 或 /[competitor]-alternative

目标关键词:"[Competitor] alternative"、"alternative to [Competitor]"、"switch from [Competitor]"

页面结构:

  1. 人们为何寻找替代方案(验证他们的痛点)
  2. 摘要:将您定位为替代方案(快速定位)
  3. 详细对比(功能、服务、定价)
  4. 谁应该切换(以及谁不应该)
  5. 迁移路径
  6. 来自切换用户的社会证明
  7. 行动号召(CTA)

格式2:[竞品] 替代方案(复数)

搜索意图:用户正在研究选项,处于旅程早期

URL模式:/alternatives/[competitor]-alternatives

目标关键词:"[Competitor] alternatives"、"best [Competitor] alternatives"、"tools like [Competitor]"

页面结构:

  1. 人们为何寻找替代方案(常见痛点)
  2. 寻找替代方案时应考虑什么(标准框架)
  3. 替代方案列表(您排第一,但包含真实选项)
  4. 对比表格(摘要)
  5. 每个替代方案的详细分解
  6. 按用例推荐
  7. 行动号召(CTA)

重要:包含4-7个真实替代方案。真正有帮助能建立信任并提升排名。

按阶段的AI回答预期:这类页面通常能在AI回答中获得引用,但AI是否推荐您的品牌取决于站外共识(评论、论坛、分析师)——对于新兴品牌,自排名列表可能会让竞品出现在AI回答中,而您仅获得引用。但仍应为满足搜索意图和品类框架而发布,但需调整预期——详见 ai-seo 的引用与推荐参考数据。


格式3:您 vs [竞品]

搜索意图:用户正在直接比较您与特定竞品

URL模式:/vs/[competitor] 或 /compare/[you]-vs-[competitor]

目标关键词:"[You] vs [Competitor]"、"[Competitor] vs [You]"

页面结构:

  1. 太长不看版摘要(2-3句话概括关键差异)
  2. 概览对比表格
  3. 按类别详细对比(功能、定价、支持、易用性、集成)
  4. [您] 最适合谁
  5. [竞品] 最适合谁(诚实)
  6. 客户评价(来自切换用户的证言)
  7. 迁移支持
  8. 行动号召(CTA)

格式4:[竞品A] vs [竞品B]

搜索意图:用户正在比较两个竞品(不直接涉及您)

URL模式:/compare/[competitor-a]-vs-[competitor-b]

页面结构:

  1. 两款产品的概述
  2. 按类别对比
  3. 各自最适合谁
  4. 第三个选项(介绍您自己)
  5. 对比表格(三者)
  6. 行动号召(CTA)

为什么有效:捕获竞品词的搜索流量,将您定位为知识渊博的参与者。


关键模块

太长不看版摘要

每个页面都以快速摘要开始,方便扫读者——2-3句话概括关键差异。

段落式对比

不要局限于表格。对每个维度,写一段文字解释差异以及各自何时重要。

功能对比

对每个类别:描述各方如何处理,列出优势和局限,给出底线推荐。

定价对比

包含逐层对比、所含内容、隐藏成本以及针对示例团队规模的总成本计算。

适用对象

明确说明每个选项的理想客户。诚实的推荐能建立信任。

迁移部分

涵盖哪些内容可转移、哪些需要重新配置、提供的支持以及来自已切换客户的引用。

详细模板:参见 references/templates.md


内容架构

集中式竞品数据

为每个竞品创建一个单一事实来源,包含:

  • 定位与目标受众
  • 定价(所有层级)
  • 功能评分
  • 优势与劣势
  • 最适合 / 不理想的对象
  • 常见投诉(来自评论)
  • 迁移说明

关于数据结构和示例:参见 references/content-architecture.md


研究流程

深度竞品研究

对于每个竞品,收集:

  1. 产品研究:注册、使用、记录功能/用户体验/局限性
  2. 定价研究:当前定价、所含内容、隐藏成本
  3. 评论挖掘:G2、Capterra、TrustRadius 上的常见赞誉/投诉主题
  4. 客户反馈:与已切换的客户交流(双向)
  5. 内容研究:他们的定位、他们的对比页面、他们的更新日志

持续更新

  • 每季度:验证定价、检查主要功能变化
  • 收到通知时:客户提及竞品变化
  • 每年:全面刷新所有竞品数据

SEO考虑因素

关键词定位

格式主要关键词
替代方案(单数)[竞品] alternative, alternative to [竞品]
替代方案(复数)[竞品] alternatives, best [竞品] alternatives
您 vs 竞品[您] vs [竞品], [竞品] vs [您]
竞品 vs 竞品[A] vs [B], [B] vs [A]

内部链接

  • 在相关竞品页面之间相互链接
  • 从功能页面链接到相关对比
  • 创建枢纽页面链接到所有竞品内容

结构化数据标记

考虑对常见问题(如"什么是[竞品]的最佳替代方案?")使用FAQ结构化数据。


输出格式

竞品数据文件

完整的竞品档案,使用YAML格式,供所有对比页面使用。

页面内容

对于每个页面:URL、元标签、按模块组织的完整页面文案、对比表格、行动号召。

页面集计划

建议创建的页面及优先级顺序(基于搜索量)。


任务特定问题

  1. 人们切换到您的原因通常是什么?
  2. 您是否有关于切换的客户引用?
  3. 您的定价与竞品相比如何?
  4. 您是否提供迁移支持?

相关技能

  • programmatic-seo:用于规模化构建竞品页面
  • copywriting:用于撰写有说服力的对比文案
  • seo-audit:用于优化竞品页面
  • schema:用于FAQ和对比结构化数据
  • sales-enablement:用于内部销售资料、演示文稿和异议文档

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions

ads

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions

ai-seo

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions

analytics

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions

aso

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions

attribution

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions

cold-email

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions

co-marketing

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says

community-marketing

Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: \

competitor-profiling

When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions

content-strategy

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions

copy-editing

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions

copywriting

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says

coreyhaines31/ab-test-setup

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

coreyhaines31/analytics-tracking

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.

coreyhaines31/aso-audit

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

coreyhaines31/competitor-alternatives

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

coreyhaines31/email-sequence

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

coreyhaines31/form-cro

When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," "contact form," "nobody fills out our form," "form abandonment," "too many fields," "demo request form," or "lead form isn't converting." Use this for any non-signup form that captures information. For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

相关技能