When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages a
复制下面这句话，粘贴给 Claude Code、Codex、Cursor 等 AI 编程工具，它会读取安装说明并在你确认后完成安装。
请阅读 https://ai.atlankj.com/install/asset/gh-programmatic-seo-8d5856a40891 ，按照其中的说明把「programmatic-seo」安装到你（当前 AI 工具）中。执行前先告诉我将运行的命令和写入的位置，等我确认。
查看 AI 将读取的安装说明正在读取 GitHub 原文…
内容来自 GitHub 原始文件，由原作者维护。在 GitHub 查看
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.
Before designing a programmatic SEO strategy, understand:
Business Context
Opportunity Assessment
Competitive Landscape
Every page must provide value specific to that page:
The best pSEO uses data competitors can't easily replicate:
Hierarchy of data defensibility:
Always use subfolders, not subdomains:
yoursite.com/templates/resume/templates.yoursite.com/resume/Subfolders pass authority to your main domain. Subdomains are treated as separate sites by Google.
URL best practices:
Pages must actually answer what people are searching for:
Beyond mixing and matching data point permutations, these are the proven playbooks for programmatic SEO:
Pattern: "[Type] template" or "free [type] template" Example searches: "resume template", "invoice template", "pitch deck template"
What it is: Downloadable or interactive templates users can use directly.
Why it works:
Value requirements:
URL structure: /templates/[type]/ or /templates/[category]/[type]/
Pattern: "best [category]" or "top [number] [things]" Example searches: "best website builders", "top 10 crm software", "best free design tools"
What it is: Curated lists ranking or recommending options in a category.
Why it works:
Value requirements:
URL structure: /best/[category]/ or /[category]/best/
Pattern: "[X] to [Y]" or "[amount] [unit] in [unit]" Example searches: "$10 USD to GBP", "100 kg to lbs", "pdf to word"
What it is: Tools or pages that convert between formats, units, or currencies.
Why it works:
Value requirements:
URL structure: /convert/[from]-to-[to]/ or /[from]-to-[to]-converter/
Pattern: "[X] vs [Y]" or "[X] alternative" Example searches: "webflow vs wordpress", "notion vs coda", "figma alternatives"
What it is: Head-to-head comparisons between products, tools, or options.
Why it works:
Value requirements:
URL structure: /compare/[x]-vs-[y]/ or /[x]-vs-[y]/
See also: competitor-alternatives skill for detailed frameworks
Pattern: "[type] examples" or "[category] inspiration" Example searches: "saas landing page examples", "email subject line examples", "portfolio website examples"
What it is: Galleries or collections of real-world examples for inspiration.
Why it works:
Value requirements:
URL structure: /examples/[type]/ or /[type]-examples/
Pattern: "[service/thing] in [location]" Example searches: "coworking spaces in san diego", "dentists in austin", "best restaurants in brooklyn"
What it is: Location-specific pages for services, businesses, or information.
Why it works:
Value requirements:
URL structure: /[service]/[city]/ or /locations/[city]/[service]/
Pattern: "[product] for [audience]" or "[solution] for [role/industry]" Example searches: "payroll software for agencies", "crm for real estate", "project management for freelancers"
What it is: Tailored landing pages addressing specific audience segments.
Why it works:
Value requirements:
URL structure: /for/[persona]/ or /solutions/[industry]/
Pattern: "[your product] [other product] integration" or "[product] + [product]" Example searches: "slack asana integration", "zapier airtable", "hubspot salesforce sync"
What it is: Pages explaining how your product works with other tools.
Why it works:
Value requirements:
URL structure: /integrations/[product]/ or /connect/[product]/
Pattern: "what is [term]" or "[term] definition" or "[term] meaning" Example searches: "what is pSEO", "api definition", "what does crm stand for"
What it is: Educational definitions of industry terms and concepts.
Why it works:
Value requirements:
URL structure: /glossary/[term]/ or /learn/[term]/
Pattern: Same content in multiple languages Example searches: "qué es pSEO", "was ist SEO", "マーケティングとは"
What it is: Your content translated and localized for other language markets.
Why it works:
Value requirements:
URL structure: /[lang]/[page]/ or yoursite.com/es/, /de/, etc.
Pattern: "[category] tools" or "[type] software" or "[category] companies" Example searches: "ai copywriting tools", "email marketing software", "crm companies"
What it is: Comprehensive directories listing options in a category.
Why it works:
Value requirements:
URL structure: /directory/[category]/ or /[category]-directory/
Pattern: "[person/company name]" or "[entity] + [attribute]" Example searches: "stripe ceo", "airbnb founding story", "elon musk companies"
What it is: Profile pages about notable people, companies, or entities.
Why it works:
Value requirements:
URL structure: /people/[name]/ or /companies/[name]/
| If you have... | Consider... |
|---|---|
| Proprietary data | Stats, 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 |
| International potential | Translations |
| Competitor landscape | Comparisons |
You can layer multiple playbooks:
Identify the pattern:
Validate demand:
Assess competition:
Identify data sources:
Data schema design:
For "[Service] in [City]" pages:
city:
- name
- population
- relevant_stats
service:
- name
- description
- typical_pricing
local_providers:
- name
- rating
- reviews_count
- specialty
local_data:
- regulations
- average_prices
- market_size
Page structure:
Ensuring uniqueness:
Template example:
H1: [Service] in [City]: [Year] Guide
Intro: [Dynamic paragraph using city stats + service context]
Section 1: Why [City] for [Service]
[City-specific data and insights]
Section 2: Top [Service] Providers in [City]
[Data-driven list with unique details]
Section 3: Pricing for [Service] in [City]
[Local pricing data if available]
Section 4: FAQs about [Service] in [City]
[Common questions with city-specific answers]
Related: [Service] in [Nearby Cities]
Hub and spoke model:
Avoid orphan pages:
Breadcrumbs:
Prioritize important pages:
Crawl budget management:
Sitemap strategy:
Content quality:
Technical SEO:
Internal linking:
Indexation:
Track:
Watch for:
Opportunity Analysis:
Implementation Plan:
Content Guidelines:
URL structure: /category/variable/
Title template: [Variable] + [Static] + [Brand]
Meta description template: [Pattern with variables]
H1 template: [Pattern]
Content outline: Section by section
Schema markup: Type and required fields
Specific pre-launch checks for this implementation
If you need more context: