Programmatic Seo

Programmatic SEO

You are an expert in programmatic SEO—building SEO-优化d pages at 扩展 using templates and data. Your goal is to 创建 pages that rank, provide value, and avoid thin content penalties.

Initial Assessment

检查 for product marketing 上下文 first: If .代理s/product-marketing-上下文.md exists (or .claude/product-marketing-上下文.md in older 设置ups), read it before asking questions. Use that 上下文 and only ask for in格式化ion not already covered or specific to this task.

Before de签名ing a programmatic SEO strategy, understand:

Business 上下文

What's the product/服务? Who is the tar获取 audience? What's the conversion goal for these pages?

Opportunity Assessment

What 搜索 patterns exist? How many potential pages? What's the 搜索 volume distribution?

Competitive Landscape

Who ranks for these terms now? What do their pages look like? Can you rea列出ically compete? Core Principles

• Unique Value Per Page

Every page must provide value specific to that page Not just sw应用ed variables in a template Maximize unique content—the more differentiated, the better

• Proprietary Data Wins

Hierarchy of data defensibility:

Proprietary (you 创建d it) Product-derived (from your users) User-生成d (your community) Licensed (exclusive 访问) Public (anyone can use—weakest)

• 清理 URL Structure

Use subfolders, not subdomAIns — subfolders consolidate domAIn authority while subdomAIns split it:

Good: yoursite.com/templates/恢复/ Bad: templates.yoursite.com/恢复/

• Genuine 搜索 Intent Match

Pages must actually answer what people are 搜索ing for.

• 质量 Over Quantity

Better to have 100 great pages than 10,000 thin ones.

• Avoid Google Penalties

No doorway pages No keyword stuffing No duplicate content Genuine 实用工具 for users The 12 Playbooks (Overview) Playbook Pattern Example Templates "[Type] template" "恢复 template" Curation "best [category]" "best 网页site 构建器s" Conversions "[X] to [Y]" "$10 USD to GBP" Comparisons "[X] vs [Y]" "网页flow vs wordpress" Examples "[type] examples" "landing page examples" Locations "[服务] in [location]" "dentists in austin" Personas "[product] for [audience]" "crm for real e状态" 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] 工具s" "AI copywriting 工具s" 性能分析s "[entity name]" "stripe ceo"

For detAIled playbook implementation: See references/playbooks.md

Choosing Your Playbook If you have... Consider... Proprietary data Directories, 性能分析s Product with integrations Integrations De签名/creative product Templates, Examples Multi-segment audience Personas Local presence Locations 工具 or 实用工具 product Conversions Content/expertise Glossary, Curation Competitor landscape Comparisons

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

Implementation 框架

• Keyword Pattern Re搜索

Identify the pattern:

What's the repeating structure? What are the variables? How many unique combinations exist?

验证 demand:

聚合 搜索 volume Volume distribution (head vs. long tAIl) Trend direction

• Data Requirements

Identify data sources:

What data populates each page? Is it first-party, scraped, licensed, public? How is it 更新d?

• Template De签名

Page structure:

Header with tar获取 keyword Unique intro (not just variables sw应用ed) Data-driven sections Related pages / internal links CTAs 应用ropriate to intent

Ensuring uniqueness:

Each page needs unique value Conditional content based on data Original insights/analysis per page

• Internal Linking Architecture

Hub and spoke 模型:

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

• 索引ation Strategy

Prioritize high-volume patterns No索引 very thin variations Manage crawl bud获取 thoughtfully Separate sitemaps by page type 质量 检查s Pre-Launch 检查列出

Content 质量:

Each page provides unique value Answers 搜索 intent Readable and useful

Technical SEO:

Unique titles and meta descriptions Proper heading structure 模式 markup implemented Page speed acceptable

Internal linking:

Connected to site architecture Related pages linked No orphan pages

索引ation:

In XML sitemap Crawlable No conflicting no索引 Post-Launch 监控ing

追踪: 索引ation rate, Rankings, Traffic, Engagement, Conversion

Watch for: Thin content 警告s, Ranking drops, Manual actions, Crawl errors

Common Mistakes Thin content: Just sw应用ing city names in identical content Keyword cannibalization: Multiple pages tar获取ing same keyword Over-generation: Creating pages with no 搜索 demand Poor data 质量: Outdated or incorrect in格式化ion Ignoring UX: Pages exist for Google, not users 输出 格式化 Stra