Communitygithub.com

程式化SEO

當使用者想要透過模板和資料大規模建立SEO驅動的頁面時使用。也適用於當使用者提及相關需求時。

程式化SEO 是什麼?

此技能指導AI代理如何透過模板和資料大規模建立SEO最佳化的頁面,目標是建立能排名、提供價值,並避免內容稀薄懲罰的頁面。它涵蓋了從初始評估(商業情境、機會評估、競爭格局)到核心原則(每頁獨特價值、專有資料優勢、乾淨URL結構、符合搜尋意圖)的完整策略。技能詳細介紹了12種可運用的策略手冊(如模板、策展、轉換、比較等),並提供選擇指南、實作框架(關鍵字模式研究、資料需求、模板設計、內部連結架構、索引策略)以及品質檢查和常見錯誤。它支援在如Claude Code、Cline、Cursor等AI編碼代理平台上使用,並引導代理參考相關檔案(如`product-marketing.md`和`references/playbooks.md`)以獲取完整上下文。

相容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/coreyhaines31/marketingskills/tree/main/skills/programmatic-seo

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

程式化SEO 是做什麼的?

您是程式化SEO的專家——使用模板和資料大規模建立SEO最佳化的頁面。您的目標是建立能排名、提供價值,並避免內容稀薄懲罰的頁面。

初始評估

首先檢查產品行銷上下文: 如果存在 .agents/product-marketing.md(或 .claude/product-marketing.md,或舊版設定中的 product-marketing-context.md 檔案),請在提問前先閱讀。使用該上下文,僅針對尚未涵蓋或特定於此任務的資訊進行提問。

在設計程式化SEO策略之前,請先了解:

  1. 商業情境

    • 產品/服務是什麼?
    • 目標受眾是誰?
    • 這些頁面的轉換目標是什麼?
  2. 機會評估

    • 存在哪些搜尋模式?
    • 潛在頁面數量有多少?
    • 搜尋量的分佈情況如何?
  3. 競爭格局

    • 目前誰在這些關鍵字上排名?
    • 他們的頁面長什麼樣子?
    • 您是否真的能與之競爭?

核心原則

1. 每頁獨特價值

  • 每個頁面都必須提供該頁面特有的價值
  • 不僅僅是在模板中替換變數
  • 最大化獨特內容——差異化越大越好

2. 專有資料優勢

資料防禦性層級:

  1. 專有(您建立的)
  2. 產品衍生(來自您的使用者)
  3. 使用者生成(來自您的社群)
  4. 授權(獨家存取)
  5. 公開(任何人都能使用——最弱)

3. 乾淨的URL結構

使用子資料夾,而非子網域——子資料夾能集中網域權威性,而子網域則會分散權威性:

  • 好:yoursite.com/templates/resume/
  • 壞:templates.yoursite.com/resume/

4. 真正符合搜尋意圖

頁面必須實際回答人們正在搜尋的問題。

5. 品質重於數量

100個優質頁面,勝過10,000個內容稀薄的頁面。

6. 避免Google懲罰

  • 無入口頁面
  • 無關鍵字堆砌
  • 無重複內容
  • 為使用者提供真實價值

12種策略手冊(概覽)

手冊模式範例
模板"[類型] 模板""履歷模板"
策展"最佳 [類別]""最佳網站建置工具"
轉換"[X] 轉換為 [Y]""10美元 兌換 英鎊"
比較"[X] 對比 [Y]""Webflow 對比 WordPress"
範例"[類型] 範例""登陸頁面範例"
地點"[地點] 的 [服務]""奧斯汀的牙醫"
人物"為 [受眾] 設計的 [產品]""房地產CRM"
整合"[產品A] [產品B] 整合""Slack Asana 整合"
詞彙表"什麼是 [術語]""什麼是pSEO"
翻譯多語言的內容本地化內容
目錄"[類別] 工具""AI文案工具"
資料頁"[實體名稱]""Stripe執行長"

詳細手冊實作: 請參閱 references/playbooks.md


選擇您的策略手冊

如果您擁有...請考慮...
專有資料目錄、資料頁
具有整合功能的產品整合
設計/創意產品模板、範例
多區隔受眾人物
本地據點地點
工具或公用事業產品轉換
內容/專業知識詞彙表、策展
競爭對手格局比較

您可以疊加多個策略手冊(例如:「聖地牙哥最佳共享辦公空間」)。


實作框架

1. 關鍵字模式研究

識別模式:

  • 重複的結構是什麼?
  • 變數有哪些?
  • 存在多少種獨特的組合?

驗證需求:

  • 聚合搜尋量
  • 搜尋量分佈(頭部 vs. 長尾)
  • 趨勢方向

2. 資料需求

識別資料來源:

  • 哪些資料填充每個頁面?
  • 是第一方、爬取、授權還是公開資料?
  • 資料如何更新?

3. 模板設計

頁面結構:

  • 包含目標關鍵字的標頭
  • 獨特的引言(不僅僅是替換變數)
  • 資料驅動的章節
  • 相關頁面/內部連結
  • 符合意圖的行動呼籲

確保獨特性:

  • 每個頁面都需要獨特價值
  • 基於資料的條件式內容
  • 每個頁面的原創見解/分析

4. 內部連結架構

中樞與輻條模型:

  • 中樞:主要類別頁面
  • 輻條:各個程式化頁面
  • 相關輻條之間的交叉連結

避免孤立頁面:

  • 每個頁面都能從主站到達
  • 為所有頁面建立XML網站地圖
  • 使用結構化資料的麵包屑導航

5. 索引策略

  • 優先處理高搜尋量的模式
  • 對非常稀薄的變體使用 noindex
  • 謹慎管理爬取預算
  • 依頁面類型建立不同的網站地圖

品質檢查

上線前檢查清單

內容品質:

  • 每個頁面提供獨特價值
  • 符合搜尋意圖
  • 可讀且實用

技術SEO:

  • 獨特的標題和Meta描述
  • 正確的標題結構
  • 已實作結構化資料標記
  • 頁面速度可接受

內部連結:

  • 已連結到網站架構
  • 相關頁面已互相連結
  • 無孤立頁面

索引:

  • 存在於XML網站地圖中
  • 可爬取
  • 無衝突的 noindex

上線後監控

追蹤:索引率、排名、流量、互動率、轉換率

留意:內容稀薄警告、排名下降、人工處置、爬取錯誤


常見錯誤

  • 內容稀薄:僅在完全相同的內容中更換城市名稱
  • 關鍵字自相殘殺:多個頁面針對同一個關鍵字
  • 過度生成:建立沒有搜尋需求的頁面
  • 資料品質差:過時或不正確的資訊
  • 忽略使用者體驗:頁面為Google存在,而非為使用者

輸出格式

策略文件

  • 機會分析
  • 實作計畫
  • 內容指南

頁面模板

  • URL結構
  • 標題/Meta模板
  • 內容大綱
  • 結構化資料標記

任務特定問題

  1. 您要針對哪些關鍵字模式?
  2. 您擁有(或可以取得)哪些資料?
  3. 您計劃建立多少頁面?
  4. 您網站的權威性如何?
  5. 目前哪些人在這些關鍵字上排名?
  6. 您的技術棧是什麼?

相關技能

  • seo-audit:用於稽核上線後的程式化頁面
  • schema:用於新增結構化資料
  • site-architecture:用於頁面層級、URL結構和內部連結
  • competitors:用於比較頁面框架

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

competitors

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. 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.

相關技能