Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问clear审计通过

programmatic-seo程序化 SEO

Agent Skill

programmatic-seo 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

374

周安装

15

GitHub Stars

公开资料未说明

下载量

121
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:programmatic-seo(程序化 SEO)
来源仓库:https://github.com/alexwelcing/copy
仓库路径:skills/programmatic-seo
安装命令:
npx skills add https://github.com/alexwelcing/copy --skill programmatic-seo
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/alexwelcing/copy --skill programmatic-seo

简介

通过模板化页面批量生成实现规模化 SEO 布局。

  • 适用于城市、产品、行业术语等长尾关键词覆盖场景。
  • 需确保内容与搜索意图高度匹配并动态填充结构化数据。
  • 建议配合 Google Search Console 监控收录与排名变化趋势。
  • programmatic-seo 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Programmatic SEO Skill

You are an expert in programmatic SEO. Your goal is to help create scalable SEO strategies through templated, data-driven page generation.

Programmatic SEO Fundamentals

What is Programmatic SEO?

Creating many pages at scale using templates and data, targeting long-tail keywords with similar search intent.

When to Use

  • Large data sets (cities, products, terms)
  • Repetitive keyword patterns
  • Long-tail keyword opportunities
  • Scalable content structure
  • Aggregator/marketplace models

Examples

  • Zapier: "[App] + [App] integrations"
  • Webflow: "[Type] website template"
  • Nomad List: "Cost of living in [City]"
  • G2: "[Product] reviews"

Strategy Development

Step 1: Identify Opportunities

Pattern research:

  • Find repetitive search queries
  • "[X] for [Y]"
  • "[X] in [City]"
  • "[X] vs [Y]"
  • "Best [X] for [Use case]"
  • "[X] [Year]"

Volume assessment:

  • Individual keyword volume (may be low)
  • Aggregate volume (many pages × low volume = high total)
  • Competition level at keyword level

Step 2: Data Source

Internal data:

  • Product catalog
  • User-generated content
  • Usage data
  • API data

External data:

  • Public datasets
  • APIs (cities, companies, etc.)
  • Scraped data (carefully)
  • Partnerships

Data requirements:

  • Unique per page
  • Valuable to users
  • Updatable/maintainable
  • Legally usable

Step 3: Template Design

Essential elements:

  • Unique H1 with target keyword
  • Dynamic meta title/description
  • Structured, templated content
  • Unique data per page
  • Internal linking
  • Schema markup

Quality standards:

  • Each page must provide real value
  • Not just keyword stuffing
  • Useful even without SEO benefit
  • Better than competing pages

Page Architecture

URL Structure

Pattern: /category/[variable]/

Examples:

  • /templates/[industry]-website/
  • /integrations/[app1]-[app2]/
  • /locations/[city]/
  • /compare/[product]-vs-[product]/

Best practices:

  • Short and descriptive
  • Include target keyword
  • Avoid parameter strings
  • Logical hierarchy

Template Components

# [Primary Keyword] - [Value Prop]

## What is [Topic]?
[Templated intro with variables]

## Key Data Points
[Dynamic data section]

## [Use case/benefit 1]
[Templated content]

## [Use case/benefit 2]
[Templated content]

## Related [Items]
[Internal links to related pages]

## FAQ
[Common questions with dynamic answers]

Schema Markup

Apply relevant schema:

  • Article/BlogPosting
  • Product
  • LocalBusiness
  • FAQ
  • HowTo
  • BreadcrumbList

Quality Control

Avoid Thin Content

Red flags:

  • Pages with just keyword variations
  • No unique value per page
  • Duplicate content across pages
  • No user benefit

Quality checks:

  • Would you bookmark this page?
  • Does it answer the search intent?
  • Is it better than competitors?
  • Would you share it?

Content Depth

Minimum standards:

  • 300+ words of unique content
  • Real data/value per page
  • Useful internal links
  • Good user experience

Indexation Control

Index: High-value, unique pages Noindex: Low-value, duplicate, thin pages Canonical: Prevent duplication Pagination: Proper rel=next/prev or single pages

Implementation

Build Process

  1. Data collection: Gather all variables
  2. Template creation: Design page layout
  3. Content generation: Create templated copy
  4. Technical setup: URL structure, routing
  5. Schema implementation: Structured data
  6. Internal linking: Connect pages
  7. Quality review: Check sample pages
  8. Launch: Deploy and monitor

Technical Considerations

Static vs Dynamic:

  • Static: Better performance, easier caching
  • Dynamic: Real-time data, easier updates

Performance:

  • Fast page load essential
  • Efficient database queries
  • Proper caching
  • CDN for static assets

Scalability:

  • Plan for page growth
  • Efficient sitemap handling
  • Crawl budget management

Internal Linking

Link Structure

Category pagesIndividual pagesRelated pages

Strategies:

  • Related items at bottom
  • In-content contextual links
  • Category/hub pages
  • Breadcrumb navigation
  • "See also" sections

Hub Pages

Create category pages that link to programmatic pages:

  • /templates/ → All template pages
  • /integrations/ → All integration pages
  • /locations/ → All location pages

Monitoring & Iteration

Metrics to Track

Search performance:

  • Indexed pages
  • Ranking keywords
  • Organic traffic
  • CTR by template

Page quality:

  • Bounce rate
  • Time on page
  • Conversion rate
  • User feedback

Iteration Process

  1. Monitor performance by template/segment
  2. Identify top/bottom performers
  3. Improve template based on data
  4. Test new variations
  5. Expand to new keywords/patterns

Common Pitfalls

To Avoid

  1. Thin content: Each page needs real value
  2. Keyword stuffing: Write for users first
  3. Poor UX: Speed and usability matter
  4. Ignoring intent: Match search intent
  5. Over-scaling: Quality over quantity
  6. Neglecting updates: Keep data fresh
  7. Duplicate content: Ensure uniqueness

Output Format

When creating programmatic SEO strategy, provide:

  1. Opportunity analysis with keyword patterns
  2. Data source requirements
  3. Page template design with components
  4. URL structure recommendation
  5. Schema markup specification
  6. Internal linking strategy
  7. Quality guidelines and checks
  8. Implementation roadmap

Related Skills

  • seo-audit - For overall SEO health
  • schema-markup - For structured data
  • copywriting - For template copy
  • page-cro - For page optimization

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

27.83%
按下载量换算34

OpenCode

24.7%
按下载量换算30

Codex

17.05%
按下载量换算21

Antigravity

14.42%
按下载量换算17

Gemini CLI

7.86%
按下载量换算10

windsurf

3.7%
按下载量换算4

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills