构建 SEO 对比页面:seomachine 竞品替代页完整章节模板体系【免费下载链接】seomachineA specialized Claude Code workspace for creating long-form, SEO-optimized blog content for any business. This system helps you research, write, analyze, and optimize content that ranks well and serves your target audience.项目地址: https://gitcode.com/GitHub_Trending/se/seomachine在 seomachine 这个面向 Claude Code 的 SEO 内容工作区中,竞品对比页Competitor Alternative Pages是捕获 X alternativeA vs B 等高购买意图搜索流量的核心内容形态。本文以 竞品页面章节模板文件 为主体,完整拆解该技能内置的七套即用模板——TL;DR 摘要、段落式对比、功能对比、定价对比、服务与支持、适用人群、迁移路径——以及对比表格的编写规范,并结合 competitor-alternatives 技能定义 与 内容架构文档 说明模板如何与集中式竞品数据联动,帮助读者在真实项目中直接复制出一套诚实、有深度、可维护的对比页写作体系。一、模板文件在 seomachine 技能体系中的位置seomachine 将可复用的专业知识组织在.claude/skills/目录下,competitor-alternatives是其中专门处理竞品对比内容的技能。其 SKILL.md 定义了四种页面形态:形态搜索意图URL 模式[Competitor] Alternative单数用户正打算从某竞品切换/alternatives/[competitor][Competitor] Alternatives复数用户还在调研选项,旅程较早/alternatives/[competitor]-alternativesYou vs [Competitor]用户直接对比你与竞品/vs/[competitor][Competitor A] vs [Competitor B]用户在两个竞品间抉择/compare/[competitor-a]-vs-[competitor-b]四种形态共享同一套必备章节,SKILL.md 在 Essential Sections 一节 列出了 TL;DR、段落式对比、功能对比、定价对比、Who Its For、Migration 六类,并明确指向模板文件:For detailed templates: See references/templates.md即本文的主角 templates.md。该文件开篇即说明其定位:Ready-to-use templates for each section of competitor comparison pages.——为竞品对比页的每个章节提供开箱即用的模板。理解模板必须先理解技能的四条核心原则SKILL.md 第 39–63 行,它们直接约束着下面每一套模板的填空方式:Honesty Builds Trust诚实建立信任:承认竞品的优势、如实陈述自己的局限、不歪曲竞品功能——读者正在做对比,他们会验证你的说法;Depth Over Surface深度优于表面:超越功能清单,解释差异为什么重要,给出使用场景;Help Them Decide帮他们做决定:明确谁最适合你谁最适合竞品,降低评估摩擦;Modular Content Architecture模块化内容架构:竞品数据集中存储,单一事实来源,更新一次、全站生效。后续所有模板都是这四条原则的落地:模板中的[honest tradeoff]、[Who should choose Competitor]等占位符,就是原则 1 和 3 的直接体现。二、TL;DR 摘要:每页必开的扫描者入口模板文件第一节 TL;DR Summary 要求每个对比页都从一个快速摘要开始,服务于只扫前几行就离开的读者:**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].这个三句结构有讲究:第一句先肯定竞品原则 1 的信任建立),第二句给出自己的定位,第三句直接给出双向选择建议——包括明确告诉读者什么时候该选竞品。这与 SKILL.md 中Start every page with a quick summary for scanners—key differences in 2-3 sentences的要求逐字对应。在 Format 3You vs Competitor的页面结构里,TL;DR 被列为第 1 个章节,位置先于所有对比表格SKILL.md 第 116–125 行。三、段落式对比:为什么不能只有表格模板第二节 Paragraph Comparison 针对每个主要对比维度要求写一段完整叙述,而非堆表格:## Features [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.模板的句式骨架是对方做法 → 对方优势及其适用场景 → 对方局限及其影响的人群 → 我方做法 → 我方收益与诚实的取舍 → 适合谁。关键设计点有两个:每个维度都要求先写竞品且写得具体[specific strength]、[use case],再写自己,避免先抑后扬的廉价对比;[honest tradeoff]占位符强制作者披露己方代价,对应核心原则Be accurate about your limitations。这一节与 SKILL.md 的 Paragraph Comparisons 要求一致:Go beyond tables. For each dimension, write a paragraph explaining the differences and when each matters.段落式对比的价值在于回答表格回答不了的问题——差异在什么场景下才重要、对哪类用户重要。四、功能对比章节:从打勾清单到描述局限结论Feature Comparison Section 模板要求Go beyond checkmarks,按功能类别逐块展开:## Feature 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].每块固定五要素:双方 2–3 句做法描述、双方的 Strengths 与 Limitations、以及一个Bottom line双向结论。其中 Limitations 对双方都是必填项——这正是诚实原则在功能层面的执行方式:只列己方 Strengths 的对比页会被读者一眼识别为营销物料。五、定价对比:分层表格 隐藏成本 总量核算Pricing Comparison Section 是模板中信息密度最高的一节,包含三部分内容:## Pricing | | [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 | **Whats 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].三层结构的用意各不相同:分层表格:按 Free tier / Starting price / Business tier / Enterprise 逐档对照,而不是只贴一个起售价;Whats included:同一价格档位下包含的功能不同,单价相同不等于价值相同;Total cost consideration Value comparison:把对比从每席位单价拉高到团队总拥有成本。模板给出固定演算场景——10 人团队的年成本近似值——这让读者可以直接代入自己的团队规模做换算,也强制作者去调研附加费、实施费等隐藏成本。这与 competitor-analysis.md 上下文中要求记录竞品 Pricing: [Brief pricing overview] 的竞品情报字段相呼应:定价信息先沉淀在竞品档案里,再由页面模板消费。六、服务与支持对比:用可验证的证据支撑评价Service Support Comparison 覆盖五个维度并给出评价来源要求:## Service 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].值得注意的是模板明确标注评价的证据来源[G2/Capterra reviews, your research],并要求引用真实用户反馈的主题或原话。这与 SKILL.md 的 Research Process 中Review mining: G2, Capterra, TrustRadius for common praise/complaint themes对应——对比页不是凭空写作,其支持质量描述应由前期的评论挖掘研究喂入。七、Who Its For:双向理想客户画像Who Its For Section 要求为竞品和自己各写一份适合谁清单,且结构完全对称:## Who 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] ## 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]每份清单固定四条:具体用例、团队类型/规模、工作流要求、预算或优先级,最后附 1–2 句的人物画像Persona。SKILL.md 对此的表述是:Be explicit about ideal customer for each option. Honest recommendations build trust.在 Format 3 页面结构中,这一节拆成 Who [You] is best for 和 Who [Competitor] is best for (be honest) 两个独立小节SKILL.md 第 120–121 行,be honest 被直接写进章节标题,可见技能对敢推荐竞品这一点的强调程度。八、迁移章节:把切换变成可执行的路线图Migration Section 是替代页Format 1的决胜章节,模板分四个子块:## Switching 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]四块各解决一个决策疑虑:哪些数据能直接迁移及注意事项、哪些配置需要重做及工作量、我方提供什么迁移支持工具、文档、时间线、过渡期支持、以及已有客户的真实切换证言。在 content-architecture.md 的竞品数据模板 中,migration_from被设计为结构化字段difficulty、data_export、what_transfers、what_doesnt、time_estimate,例如示例竞品 Notion 的档案里写明导出数据格式为 Markdown, CSV, HTML、自动化与集成配置不可迁移、小团队耗时 1–3 天——页面模板中的 What transfers / What needs reconfiguration 两块内容,正是从这类集中数据中读取后展开的,体现了单一事实来源 → 多页复用的模块化架构。九、社会证明:只聚焦切换者Social Proof Section 模板明确Focus on switchers——对比页上的证言应该来自真的从竞品切过来的客户,而非泛泛的好评:## What 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]结构上分两层:带署名、角色、公司的具体切换动机证言至少两条,且要求具体到为什么切换、切换后结果如何),以及量化的 Results after switching 列表。SKILL.md 的调研流程把数据来源指向前期的客户访谈:Customer feedback: Talk to customers who switched (both directions)SKILL.md 第 195 行,both directions 意味着也包括流向竞品的客户,这些反馈既用于改进产品,也用于校准页面上切换原因的叙事是否站得住脚。十、对比表格最佳实践:去打勾化、按类别组织、引入评级模板最后一节 Comparison Table Best Practices 给出三条表格规范:1. 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 |打勾丢失了支持到什么程度这一关键维度;Full support with detail 与 Basic support, limitation 的写法把程度和局限都写进了单元格。2. Organize by Category按类别组织——把功能归入有业务含义的组别:核心功能Core functionality、协作Collaboration、集成Integrations、安全与合规Security compliance、支持与服务Support service。这与第四节模板按[Feature Category]分块展开的做法一致:先分类,再逐类对比。3. Include Ratings Where Useful适当引入星级评级:| Category | You | Competitor | Notes | |----------|-----|-----------|-------| | Ease of use | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐ | [Brief note] | | Feature depth | ⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ | [Brief note] |评级表的关键是保留 Notes 列——每一档星级差异都附带一句简短解释,避免读者把星数当成无依据的自我打分。十一、与仓库其他模块的联动:模板如何被喂数上述模板不是孤立文件,它在 seomachine 中处于三条供应链的交汇点:竞品数据档案 → 模板填空。content-architecture.md 规定为每个竞品建立competitor_data/[name].md单一事实来源,包含定位、全档位定价、功能评级1–5 分、诚实的 strengths/weaknesses、best_for/not_ideal_for、来自评论的 common_complaints、迁移笔记等 YAML 字段完整模板见第 19–95 行。其 Page Generation 一节 明确四种页面各取哪些数据:替代页 竞品数据 己方数据;vs 页 己方 竞品;竞品互比页 两个竞品 己方。模板文件里所有[strength]、[limitation]、[SLA if known]占位符,对应关系就是这些 YAML 字段。竞品情报上下文 → 研究输入。seomachine 的context/目录存放驱动全部内容生成的品牌上下文,其中 competitor-analysis.md 是竞品情报模板,要求按竞品记录定价、SEO 强弱项、内容缺口、被竞品霸榜的关键词含排名与内容类型等,并要求季度/年度维护节奏。CLAUDE.md 将其定位为 Competitive intelligence 上下文文件。对比页写作前,该档案提供对手强在哪、弱在哪、用户抱怨什么的原始素材。规模化 → 程序化 SEO 的 Comparisons 打法。当对比页从 3–5 个扩到几十个时,programmatic-seo 技能 将其纳入 Comparisons playbook[X] vs [Y]模式,如 webflow vs wordpress,见 12 个 Playbooks 总表。该技能的核心约束与对比页模板天然契合:Unique Value Per Page每页必须提供该页独有的价值,不能只是变量替换对应模板中要求具体到[scenario]、[user type]的填空;Avoid Google Penalties无门页、无重复内容约束了模板不能退化成填空机。competitor-alternatives 技能 也在 Related Skills 中把 programmatic-seo 列为批量构建竞品页的配套技能,形成模板写单页、playbook 管规模的分工。此外,仓库提供 examples/castos/ 作为一套完整的真实配置示例播客托管 SaaS 场景,其中 brand-voice、features、internal-links-map 等上下文文件展示了上下文文件如何为内容生成供数的端到端形态——对比页的 CTA、内部链接如从功能页链到相关对比页,SKILL.md 的 Internal Linking 一节要求正是消费这些上下文的环节。十二、落地清单:从模板到上线的核对项综合模板文件与 SKILL.md 的要求,一个合格的对比页应满足:开头是 2–3 句 TL;DR,包含双向选择建议;每个主要维度有段落式叙述,且披露己方[honest tradeoff];功能对比按类别分块,每块含双方 Strengths/Limitations 与 Bottom line;定价对比含分层表、含什么、总拥有成本三段,给出可代入的示例团队规模核算;支持质量描述标注了评论/研究来源;存在对称的 Who Should Choose 对方 / 我方 两节;迁移章节覆盖可迁移项、需重配项、迁移支持、切换者证言四块;对比表格无裸打勾,单元格写程度与局限,重要维度可加星级Notes;页面数据取自集中式竞品档案,价格等功能变更只需在档案中更新一次。这套模板体系的本质,是把诚实的竞品对比从写作风格升格为可复用的工程结构:模板锁定每个章节的信息单元,集中数据保证跨页一致,规模化时交给程序化 SEO playbook 承接。对以 seomachine 作为内容工作区的团队而言,对照本文逐节填空,即可批量产出既能服务真实评估者、又能捕获竞品词搜索流量的对比页内容。【免费下载链接】seomachineA specialized Claude Code workspace for creating long-form, SEO-optimized blog content for any business. This system helps you research, write, analyze, and optimize content that ranks well and serves your target audience.项目地址: https://gitcode.com/GitHub_Trending/se/seomachine创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考