Communitygithub.com

競爭者分析與替代頁面

當使用者想要建立競爭者比較或替代頁面,以應用於 SEO 和銷售輔助時使用。也適用於使用者提到相關需求時。

競爭者分析與替代頁面 是什麼?

此技能專注於建立深度、誠實且有說服力的競爭者比較與替代頁面。它旨在幫助開發者或 AI 代理使用者創建能為評估中的潛在客戶提供真正價值的資源,同時提升產品的 SEO 排名與銷售轉換率。技能明確指出需要先讀取產品行銷背景檔案,以減少不必要的提問,並強調「誠實建立信任」的核心原則。支援多種頁面格式,包括單一替代方案、多重替代方案、直接對比(你 vs 競爭者)以及競爭者之間的比較,每個格式都有對應的搜尋意圖、URL 模式和目標關鍵字。技能也涵蓋深入的研究流程、內容架構(中心化資料管理)、SEO 考量(關鍵字定位、內部連結、結構化資料)以及與其他技能(如 programmatic-seo、copywriting)的整合,確保整個流程從研究到產出都能有效率地進行。

相容平台✓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. 行動呼籲

格式 2:[競爭者] 替代方案(複數)

搜尋意圖:使用者正在研究選項,處於較早的旅程階段

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

目標關鍵字:「[Competitor] alternatives」、「best [Competitor] alternatives」、「tools like [Competitor]」

頁面結構:

  1. 人們為何尋找替代方案(常見痛點)
  2. 在替代方案中應尋找什麼(標準框架)
  3. 替代方案列表(您排第一,但包含真實選項)
  4. 比較表(摘要)
  5. 每個替代方案的詳細分解
  6. 按使用案例的推薦
  7. 行動呼籲

重要:包含 4-7 個真實的替代方案。提供真正幫助能建立信任並獲得更好的排名。

各階段的 AI 答案期望:這些頁面通常在 AI 答案中獲得引用,但 AI 是否會從中推薦您的品牌取決於站外共識(評論、論壇、分析師)——對於新興品牌,自行排序的列表可能會讓競爭者出現在 AI 答案中,而您只獲得引用。仍應為了搜尋意圖和類別框架而發布,但需設定相應的期望——請參閱 ai-seo 的引用與推薦對比參考資料。


格式 3:您的產品 vs [競爭者]

搜尋意圖:使用者正在直接比較您的產品與特定競爭者

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

目標關鍵字:「[You] vs [Competitor]」、「[Competitor] vs [You]」

頁面結構:

  1. TL;DR 摘要(2-3 句說明關鍵差異)
  2. 一覽比較表
  3. 按類別詳細比較(功能、定價、支援、易用性、整合)
  4. 您的產品最適合誰
  5. 競爭者最適合誰(誠實以對)
  6. 客戶心聲(來自轉換者的推薦)
  7. 遷移支援
  8. 行動呼籲

格式 4:[競爭者 A] vs [競爭者 B]

搜尋意圖:使用者正在比較兩個競爭者(而非直接比較您的產品)

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

頁面結構:

  1. 兩個產品的概覽
  2. 按類別比較
  3. 各自最適合誰
  4. 第三個選項(介紹您的產品)
  5. 比較表(三者)
  6. 行動呼籲

為什麼有效:捕獲競爭者相關詞彙的搜尋流量,並將您定位為專家。


必要章節

TL;DR 摘要

每個頁面都以快速摘要開始,方便掃讀者——2-3 句說明關鍵差異。

段落式比較

超越表格。針對每個維度,撰寫一段文字解釋差異以及何時每個維度重要。

功能比較

針對每個類別:描述每個選項如何處理、列出優勢和限制、給出底線建議。

定價比較

包含逐層級比較、包含的項目、隱藏成本,以及針對範例團隊規模的總成本計算。

適用對象

明確說明每個選項的理想客戶。誠實的推薦能建立信任。

遷移章節

涵蓋可轉移的內容、需要重新配置的內容、提供的支援,以及來自轉換客戶的引言。

詳細範本請參考:references/templates.md


內容架構

集中式競爭者資料

為每個競爭者建立單一事實來源,包含:

  • 定位和目標受眾
  • 定價(所有層級)
  • 功能評分
  • 優勢和劣勢
  • 最適合 / 不適合
  • 常見抱怨(來自評論)
  • 遷移備註

資料結構和範例請參考:references/content-architecture.md


研究流程

深度競爭者研究

針對每個競爭者,收集:

  1. 產品研究:註冊、使用、記錄功能/使用者體驗/限制
  2. 定價研究:當前定價、包含項目、隱藏成本
  3. 評論挖掘:G2、Capterra、TrustRadius 上的常見讚美/抱怨主題
  4. 客戶回饋:與轉換的客戶交流(雙向)
  5. 內容研究:他們的定位、他們的比較頁面、他們的更新日誌

持續更新

  • 每季:驗證定價,檢查重大功能變更
  • 收到通知時:客戶提到競爭者發生變化
  • 每年:全面刷新所有競爭者資料

SEO 考量

關鍵字定位

格式主要關鍵字
替代方案(單數)[Competitor] alternative, alternative to [Competitor]
替代方案(複數)[Competitor] alternatives, best [Competitor] alternatives
您的產品 vs 競爭者[You] vs [Competitor], [Competitor] vs [You]
競爭者 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.

相關技能