programmatic-seo

작성자: sentry

사용자가 템플릿과 데이터를 사용하여 SEO 기반 페이지를 대규모로 생성하려는 경우. 또한 사용자가 "programmatic SEO", "템플릿 페이지", "페이지..."를 언급할 때 사용합니다.

npx skills add https://github.com/getsentry/webvitals.com --skill programmatic-seo

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 .claude/product-marketing-context.md exists, 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)

PlaybookPatternExample
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"
TranslationsContent in multiple languagesLocalized content
Directory"[category] tools""ai copywriting tools"
Profiles"[entity name]""stripe ceo"

For detailed playbook implementation: See references/playbooks.md


Choosing Your Playbook

If you have...Consider...
Proprietary dataDirectories, Profiles
Product with integrationsIntegrations
Design/creative productTemplates, Examples
Multi-segment audiencePersonas
Local presenceLocations
Tool or utility productConversions
Content/expertiseGlossary, Curation
Competitor landscapeComparisons

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
  • competitor-alternatives: For comparison page frameworks

sentry의 다른 스킬

architecture-review
sentry
직원 수준의 코드베이스 건강 검토. 모놀리식 모듈, 무음 실패, 타입 안전성 격차, 테스트 커버리지 구멍, LLM 친화성 문제를 찾습니다.
pi-agent-integration
sentry
Integrate `@mariozechner/pi-agent-core` as the agent abstraction inside another library or runtime. Use when implementing or refactoring Pi Agent wrappers,…
sentry-debug-issue
sentry
Sentry 이슈를 디버깅하고 수정합니다 — (링크, ID 또는 검색으로) 찾고, 전체 컨텍스트(스택 트레이스, 브레드크럼, 트레이스, 로그)를 가져오고, 선택적으로 Seer 근본 원인 분석을 실행합니다…
sentry-svelte-sdk
sentry
Svelte 및 SvelteKit을 위한 완전한 Sentry SDK 설정입니다. "Svelte에 Sentry 추가", "SvelteKit에 Sentry 추가", "@sentry/sveltekit 설치" 또는 구성 요청 시 사용하세요.
sentry-svelte-sdk
sentry
Svelte 및 SvelteKit을 위한 완전한 Sentry SDK 설정입니다. "Svelte에 Sentry 추가", "SvelteKit에 Sentry 추가", "@sentry/sveltekit 설치" 또는 구성 요청 시 사용하세요.
skill-scanner
sentry
에이전트 스킬의 보안 문제를 스캔합니다. "스킬 스캔" 요청 시 사용하세요.
prompt-optimizer
sentry
에이전트 프롬프트, 시스템 프롬프트, 개발자 프롬프트 및 재사용 가능한 프롬프트 템플릿을 생성, 최적화, 반복적으로 개선합니다. 개선 요청 시 사용합니다.
commit
sentry
commit — AI 에이전트를 위한 설치 가능한 스킬로, getsentry/sentry-docs에서 게시했습니다.