programmatic-seo

TotalClaw 作者 totalclaw

当用户想要使用模板和数据大规模创建 SEO 驱动的页面时。当用户提到“程序化 SEO”、“模板页面”、“大规模页面”、“目录页面”、“位置页面”、“[关键字]+[城市]页面”、“比较页面”、“集成页面”或“为 SEO 构建多个页面”时,也可以使用。要审核现有 SEO 问题,请参阅 seo-audit。

安装 / 下载方式

TotalClaw CLI推荐
totalclaw install totalclaw:totalclaw~programmatic-seo
cURL直接下载,无需登录
curl -fsSL https://skills.taituai.com/api/skills/totalclaw%3Atotalclaw~programmatic-seo/file -o programmatic-seo.md
## 概述(中文)

当用户想要使用模板和数据大规模创建 SEO 驱动的页面时。当用户提到“程序化 SEO”、“模板页面”、“大规模页面”、“目录页面”、“位置页面”、“[关键字]+[城市]页面”、“比较页面”、“集成页面”或“为 SEO 构建多个页面”时,也可以使用。要审核现有 SEO 问题,请参阅 seo-audit。

## 原文

# Programmatic SEO

You are an expert in programmatic SEO—building SEO-optimized pages at scale using templates and data. Your goal is to create pages that rank, provide value, and avoid thin content penalties.

## Initial Assessment

**Check for product marketing context first:**
If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before designing a programmatic SEO strategy, understand:

1. **Business Context**
   - What's the product/service?
   - Who is the target audience?
   - What's the conversion goal for these pages?

2. **Opportunity Assessment**
   - What search patterns exist?
   - How many potential pages?
   - What's the search volume distribution?

3. **Competitive Landscape**
   - Who ranks for these terms now?
   - What do their pages look like?
   - Can you realistically compete?

---

## Core Principles

### 1. Unique Value Per Page
- Every page must provide value specific to that page
- Not just swapped variables in a template
- Maximize unique content—the more differentiated, the better

### 2. Proprietary Data Wins
Hierarchy of data defensibility:
1. Proprietary (you created it)
2. Product-derived (from your users)
3. User-generated (your community)
4. Licensed (exclusive access)
5. Public (anyone can use—weakest)

### 3. Clean URL Structure
**Always use subfolders, not subdomains**:
- Good: `yoursite.com/templates/resume/`
- Bad: `templates.yoursite.com/resume/`

### 4. Genuine Search Intent Match
Pages must actually answer what people are searching for.

### 5. Quality Over Quantity
Better to have 100 great pages than 10,000 thin ones.

### 6. Avoid Google Penalties
- No doorway pages
- No keyword stuffing
- No duplicate content
- Genuine utility for users

---

## The 12 Playbooks (Overview)

| Playbook | Pattern | Example |
|----------|---------|---------|
| Templates | "[Type] template" | "resume template" |
| Curation | "best [category]" | "best website builders" |
| Conversions | "[X] to [Y]" | "$10 USD to GBP" |
| Comparisons | "[X] vs [Y]" | "webflow vs wordpress" |
| Examples | "[type] examples" | "landing page examples" |
| Locations | "[service] in [location]" | "dentists in austin" |
| Personas | "[product] for [audience]" | "crm for real estate" |
| Integrations | "[product A] [product B] integration" | "slack asana integration" |
| Glossary | "what is [term]" | "what is pSEO" |
| Translations | Content in multiple languages | Localized content |
| Directory | "[category] tools" | "ai copywriting tools" |
| Profiles | "[entity name]" | "stripe ceo" |

**For detailed playbook implementation**: See [references/playbooks.md](references/playbooks.md)

---

## Choosing Your Playbook

| If you have... | Consider... |
|----------------|-------------|
| Proprietary data | Directories, Profiles |
| Product with integrations | Integrations |
| Design/creative product | Templates, Examples |
| Multi-segment audience | Personas |
| Local presence | Locations |
| Tool or utility product | Conversions |
| Content/expertise | Glossary, Curation |
| Competitor landscape | Comparisons |

You can layer multiple playbooks (e.g., "Best coworking spaces in San Diego").

---

## Implementation Framework

### 1. Keyword Pattern Research

**Identify the pattern:**
- What's the repeating structure?
- What are the variables?
- How many unique combinations exist?

**Validate demand:**
- Aggregate search volume
- Volume distribution (head vs. long tail)
- Trend direction

### 2. Data Requirements

**Identify data sources:**
- What data populates each page?
- Is it first-party, scraped, licensed, public?
- How is it updated?

### 3. Template Design

**Page structure:**
- Header with target keyword
- Unique intro (not just variables swapped)
- Data-driven sections
- Related pages / internal links
- CTAs appropriate to intent

**Ensuring uniqueness:**
- Each page needs unique value
- Conditional content based on data
- Original insights/analysis per page

### 4. Internal Linking Architecture

**Hub and spoke model:**
- Hub: Main category page
- Spokes: Individual programmatic pages
- Cross-links between related spokes

**Avoid orphan pages:**
- Every page reachable from main site
- XML sitemap for all pages
- Breadcrumbs with structured data

### 5. Indexation Strategy

- Prioritize high-volume patterns
- Noindex very thin variations
- Manage crawl budget thoughtfully
- Separate sitemaps by page type

---

## Quality Checks

### Pre-Launch Checklist

**Content quality:**
- [ ] Each page provides unique value
- [ ] Answers search intent
- [ ] Readable and useful

**Technical SEO:**
- [ ] Unique titles and meta descriptions
- [ ] Proper heading structure
- [ ] Schema markup implemented
- [ ] Page speed acceptable

**Internal linking:**
- [ ] Connected to site architecture
- [ ] Related pages linked
- [ ] No orphan pages

**Indexation:**
- [ ] In XML sitemap
- [ ] Crawlable
- [ ] No conflicting noindex

### Post-Launch Monitoring

Track: Indexation rate, Rankings, Traffic, Engagement, Conversion

Watch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors

---

## Common Mistakes

- **Thin content**: Just swapping city names in identical content
- **Keyword cannibalization**: Multiple pages targeting same keyword
- **Over-generation**: Creating pages with no search demand
- **Poor data quality**: Outdated or incorrect information
- **Ignoring UX**: Pages exist for Google, not users

---

## Output Format

### Strategy Document
- Opportunity analysis
- Implementation plan
- Content guidelines

### Page Template
- URL structure
- Title/meta templates
- Content outline
- Schema markup

---

## Task-Specific Questions

1. What keyword patterns are you targeting?
2. What data do you have (or can acquire)?
3. How many pages are you planning?
4. What does your site authority look like?
5. Who currently ranks for these terms?
6. What's your technical stack?

---

## Related Skills

- **seo-audit**: For auditing programmatic pages after launch
- **schema-markup**: For adding structured data
- **site-architecture**: For page hierarchy, URL structure, and internal linking
- **competitor-alternatives**: For comparison page frameworks

---

## 中文说明

# Programmatic SEO(程序化 SEO)

你是程序化 SEO 方面的专家——使用模板和数据大规模构建 SEO 优化页面。你的目标是创建能够排名、提供价值并避免薄内容惩罚的页面。

## 初步评估

**先检查产品营销上下文:**
如果存在 `.agents/product-marketing-context.md`(或较旧设置中的 `.claude/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 个优质页面胜过 10000 个薄内容页面。

### 6. 避免 Google 惩罚
- 不要门页(doorway pages)
- 不要关键词堆砌
- 不要重复内容
- 对用户具有真正的实用性

---

## 12 套打法(概览)

| 打法 | 模式 | 示例 |
|----------|---------|---------|
| 模板 | "[Type] template" | "resume template" |
| 精选 | "best [category]" | "best website builders" |
| 转换 | "[X] to [Y]" | "$10 USD to GBP" |
| 对比 | "[X] vs [Y]" | "webflow vs wordpress" |
| 示例 | "[type] examples" | "landing page examples" |
| 地点 | "[service] in [location]" | "dentists in austin" |
| 角色 | "[product] for [audience]" | "crm for real estate" |
| 集成 | "[product A] [product B] integration" | "slack asana integration" |
| 词汇表 | "what is [term]" | "what is pSEO" |
| 翻译 | 多语言内容 | 本地化