programmatic-seo
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSEO: Programmatic SEO
SEO：Programmatic SEO
Guides programmatic SEO—creating large numbers of SEO-optimized pages automatically using templates and structured data, rather than writing each page manually. Works like a mail merge for web pages: one template + data yields hundreds or thousands of unique pages targeting long-tail keyword patterns.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
指导Programmatic SEO实践——通过模板和结构化数据自动创建大量SEO优化页面，而非手动撰写每个页面。这就像是网页版的邮件合并：一个模板加上数据，就能生成数百或数千个针对长尾关键词模式的独特页面。
调用时机：首次使用时，如有必要，先用1-2句话说明本技能涵盖的内容及其重要性，再提供主要输出内容。后续使用或用户要求跳过介绍时，直接提供主要输出。
Definition
定义
Programmatic SEO = Building a single template and populating it with data from a database, API, or spreadsheet to generate hundreds or thousands of unique pages. Each page targets a long-tail keyword (e.g., "best SEO tool in [city]," "[App A] + [App B] integration").
Key differences from traditional SEO: Technical (SEOs + engineers); long-tail focus; data-driven (data quality = success); automation; built for scale.
Programmatic SEO = 构建单个模板，并用数据库、API或电子表格中的数据填充，以生成数百或数千个独特页面。每个页面针对一个长尾关键词（例如“[城市]最佳SEO工具”、“[应用A]+[应用B]集成”）。
与传统SEO的主要区别：技术导向（SEO人员+工程师协作）；聚焦长尾关键词；数据驱动（数据质量是成功关键）；自动化；为规模化运营而生。
Three-Part Framework
三部分框架
| Component | Role |
|---|---|
| Templates | Reusable page structures: layout, headings, internal links, content blocks; conditional logic for empty fields |
| Data | Structured information: locations, products, prices, features—must be accurate, complete, and add genuine value |
| Automation | Systems connecting data to templates; pages generated dynamically or published in bulk |
| 组件 | 作用 |
|---|---|
| 模板 | 可复用的页面结构：布局、标题、内部链接、内容模块；支持空字段的条件逻辑 |
| 数据 | 结构化信息：地点、产品、价格、功能——必须准确、完整且具备真实价值 |
| 自动化 | 连接数据与模板的系统；页面可动态生成或批量发布 |
Template Structure (Recommended)
推荐模板结构
| Section | Purpose |
|---|---|
| Intro | Introduction; matches user intent |
| Evidence block | Data-driven content unique to each page (tables, lists, verified stats); differentiates from thin content |
| Decision | Comparison, recommendation, or next steps |
| FAQ | Frequently asked questions |
| CTA | Call-to-action |
Evidence block = Real, structured data per page (business listings, pricing, reviews, verified stats). Ensures each page delivers genuine value, not recycled boilerplate with swapped variables.
| 板块 | 用途 |
|---|---|
| 引言 | 页面介绍；匹配用户搜索意图 |
| 证据模块 | 每个页面独有的数据驱动内容（表格、列表、已验证统计数据）；与低质量内容形成差异化 |
| 决策建议 | 对比、推荐或下一步行动指引 |
| 常见问题（FAQ） | 用户常问问题集合 |
| 行动号召（CTA） | 引导用户执行特定操作 |
证据模块 = 每个页面配备真实的结构化数据（商家信息、定价、评论、已验证统计数据）。确保每个页面都能提供真实价值，而非仅替换变量的重复模板内容。
Data Foundation
数据基础要求
| Requirement | Practice |
|---|---|
| Provenance | Log data sources; track origin |
| Freshness rules | e.g., ratings every 90 days, prices every 30 days |
| First-party / licensed | Prefer over scraped content |
| Clean & merge | Deduplicate; ensure depth |
| 要求 | 实践方案 |
|---|---|
| 数据源溯源 | 记录数据来源；追踪信息源头 |
| 数据更新规则 | 例如：评分每90天更新，价格每30天更新 |
| 优先使用自有/授权数据 | 优于爬取的公开内容 |
| 数据清洗与合并 | 去重；确保数据深度 |
Ideal Use Cases
理想适用场景
| Use case | Example |
|---|---|
| Location-specific pages | "Plumber in [city]," "Best restaurants in [neighborhood]" with real local data |
| Product comparison | "[Product A] vs [Product B]" with structured specs |
| Alternatives pages | "[Competitor] alternatives" at scale; 50+ competitors; see alternatives-page-generator |
| Software integration | "[App A] + [App B]" integration pages (e.g., Zapier 50K+ pages) |
| Free tools | "[X] checker," "[Y] calculator," "[Z] generator" — standalone tool pages; toolkit hub; same ICP as main product; lead gen |
| Travel / destination | City + attraction combinations with reviews, photos |
| E-commerce | Category pages, product variations (size, color, material) |
| FAQ / Q&A | Pages powered by user question databases |
| Salary / pricing | Comparison pages with structured data |
Avoid when: Site structure is weak; page differences are superficial (city/name swaps only); content requires original expertise or UGC participation.
| 适用场景 | 示例 |
|---|---|
| 地域专属页面 | “[城市] plumber（管道工）”、“[街区]最佳餐厅”搭配真实本地数据 |
| 产品对比页面 | “[产品A] vs [产品B]”搭配结构化参数 |
| 竞品替代页面 | 批量生成「[竞品]替代方案」页面；支持50+竞品；可参考alternatives-page-generator |
| 软件集成页面 | “[应用A]+[应用B]”集成页面（例如Zapier的5万+页面） |
| 免费工具页面 | “[X]检测工具”、“[Y]计算器”、“[Z]生成器”——独立工具页面；工具集枢纽；与主产品目标用户一致；用于获客 |
| 旅游/目的地页面 | 城市+景点组合页面，搭配评论、照片 |
| 电商页面 | 分类页面、产品变体页面（尺寸、颜色、材质） |
| FAQ/问答页面 | 基于用户问题数据库生成的页面 |
| 薪资/定价对比页面 | 搭配结构化数据的对比页面 |
避免场景：网站结构薄弱；页面差异仅为表面化（仅替换城市/名称）；内容需要原创专业知识或用户生成内容（UGC）参与。
Real-World Examples
实际案例
Examples are illustrative; no endorsement implied.
| Company | Scale | Pattern |
|---|---|---|
| Zapier | 50,000+ pages | "[App A] + [App B]" integration |
| Airbnb | — | Location search; destination × property |
| Review platforms | — | User reviews + automated comparison pages |
| Travel sites | — | Destination, hotel, flight, activity pages |
| NomadList | 2,000+ city pages | Cost-of-living, internet speed (dynamic data) |
| Semrush, Ahrefs | 50+ free tools | SEO checker, keyword tool, backlink checker; toolkit hub + per-tool pages |
案例仅作说明，不代表背书。
| 公司 | 规模 | 模式 |
|---|---|---|
| Zapier | 50,000+页面 | “[应用A]+[应用B]”集成 |
| Airbnb | — | 地点搜索；目的地×房源组合 |
| 评论平台 | — | 用户评论+自动化对比页面 |
| 旅游网站 | — | 目的地、酒店、航班、活动页面 |
| NomadList | 2,000+城市页面 | 生活成本、网速（动态数据） |
| Semrush, Ahrefs | 50+免费工具 | SEO检测工具、关键词工具、反向链接检测工具；工具集枢纽+单工具页面 |
Content Requirements
内容要求
| Requirement | Purpose |
|---|---|
| 300+ words per page | Avoid thin content penalties |
| Unique, verifiable data | Each page must add meaningful page-specific content beyond simple data swaps |
| Evidence block | Tables, lists, examples with real numbers/attributes on every page |
| Semantic HTML | Proper structure; conditional logic to avoid empty or repetitive sections |
| Internal linking | Link related programmatic pages; compounds traffic and indexation |
| 要求 | 目的 |
|---|---|
| 单页300+单词 | 避免低质量内容处罚 |
| 独特、可验证的数据 | 每个页面除简单数据替换外，必须添加有意义的专属内容 |
| 证据模块 | 每个页面配备表格、列表、带真实数字/属性的示例 |
| 语义化HTML | 合理的页面结构；通过条件逻辑避免空内容或重复板块 |
| 内部链接 | 关联相关程序化页面；提升流量与索引效率 |
Technical Considerations
技术考量
| Topic | Practice |
|---|---|
| Selective indexation | Don't index all pages; use noindex rules for low-value pages |
| Sitemap segmentation | By country, language, division; manage crawl budget |
| URL structure | Descriptive URLs; clean hierarchy; see url-structure |
| Schema | JSON-LD: Product, Place, FAQ, ItemList per page type |
| Performance | Caching, static generation; Core Web Vitals |
| 主题 | 实践方案 |
|---|---|
| 选择性索引 | 不要索引所有页面；对低价值页面使用noindex规则 |
| 站点地图分段 | 按国家、语言、业务板块拆分；优化抓取预算 |
| URL结构 | 描述性URL；清晰的层级结构；可参考url-structure |
| Schema标记 | 针对不同页面类型使用JSON-LD：Product、Place、FAQ、ItemList |
| 性能优化 | 缓存、静态生成；符合Core Web Vitals要求 |
Critical Pitfalls
关键陷阱
| Pitfall | Consequence |
|---|---|
| Thin content | Minimal info beyond keyword; generic copy; placeholder sections → penalties |
| Duplicate pages | Same content with only data swaps → thin content penalties |
| Index bloat | Generating pages that should never be indexable → crawl budget waste |
| Large dumps | Publishing many similar pages at once → spam signals |
| Filter URLs | Using filters instead of unique URLs/titles → cannibalization |
Pages with only a title, one paragraph, and swapped city names will not rank and may incur Google penalties.
| 陷阱 | 后果 |
|---|---|
| 低质量内容 | 除关键词外信息极少；通用文案；占位板块 → 搜索引擎处罚 |
| 页面重复 | 仅替换数据的相同内容 → 低质量内容处罚 |
| 索引冗余 | 生成不应被索引的页面 → 浪费抓取预算 |
| 批量垃圾发布 | 一次性发布大量相似页面 → 触发垃圾内容信号 |
| 过滤型URL | 使用筛选器而非独立URL/标题 → 关键词内耗 |
仅包含标题、一段文案和替换城市名称的页面无法获得排名，甚至可能遭到Google处罚。
Step-by-Step Workflow
分步工作流程
- Research — Niche, intent; include low-volume keywords; SEO tools, question databases
- Collect data — Provenance log, freshness rules; first-party/licensed; define template fields
- Choose stack — Next.js + DB, Webflow CMS, WordPress, headless; API + template reuse
- Design template — Intro, Evidence, Decision, FAQ, CTA; schema; conditional logic
- Build database — Map fields to template slots; hide empties
- Generate pages — Descriptive URLs; optimize performance
- Deploy & monitor — Sitemaps; indexation, rankings, CTR, bounce, conversions
- Optimize — Prune weak pages; refresh data; A/B test layout, CTA
- 调研 — 细分领域、用户意图；纳入低流量关键词；使用SEO工具、问题数据库
- 收集数据 — 记录数据源、更新规则；优先使用自有/授权数据；定义模板字段
- 选择技术栈 — Next.js+数据库、Webflow CMS、WordPress、无头CMS；API+模板复用
- 设计模板 — 引言、证据模块、决策建议、FAQ、CTA；Schema标记；条件逻辑
- 构建数据库 — 映射字段到模板插槽；隐藏空内容
- 生成页面 — 描述性URL；优化性能
- 部署与监控 — 站点地图；索引状态、排名、点击率、跳出率、转化率
- 优化迭代 — 淘汰低表现页面；更新数据；A/B测试布局、CTA
Best Practices
最佳实践
| Practice | Purpose |
|---|---|
| Quality over scale | Each page must provide genuinely unique, verifiable value |
| Launch in batches | Small batches you can measure; avoid large dumps |
| Strong IA | Internal links to related guides/categories |
| Visual elements | Tables, maps, comparisons where relevant |
| Match intent | Avoid generic template text; precise user intent |
| 实践 | 目的 |
|---|---|
| 质量优先于规模 | 每个页面必须提供真正独特、可验证的价值 |
| 分批上线 | 小批量发布以便效果衡量；避免一次性大量发布 |
| 清晰的信息架构（IA） | 关联相关指南/分类页面的内部链接 |
| 视觉元素 | 按需添加表格、地图、对比内容 |
| 匹配用户意图 | 避免通用模板文案；精准贴合用户需求 |
Timeline & Expectations
时间线与预期
- Typical time to ranking: ~6 months
- Reported gains: 40%+ traffic increases from well-designed topic clusters
- AI search: Structured, data-rich content performs better in AI Overviews and citation layers
- 典型排名周期：约6个月
- 已报告收益：设计完善的主题集群可带来40%以上的流量增长
- AI搜索适配：结构化、数据丰富的内容在AI概览和引用层表现更优
Output Format
输出格式
- Template design (Intro, Evidence, Decision, FAQ, CTA; required data fields)
- Data requirements (provenance, freshness, accuracy)
- Internal linking (hub-and-spoke, related pages)
- Indexation strategy (selective indexation, sitemap segmentation)
- Checklist for audit
- 模板设计（引言、证据模块、决策建议、FAQ、CTA；必填数据字段）
- 数据要求（数据源溯源、更新频率、准确性）
- 内部链接策略（ hub-and-spoke模式、关联页面）
- 索引策略（选择性索引、站点地图分段）
- 审计检查清单
Related Skills
相关技能
- template-page-generator: Template structure; aggregation (gallery) + detail pages; programmatic template design; user-facing templates (CMS, design, vibe coding)
- landing-page-generator: Conversion-focused programmatic pages; programmatic landing pages; LP structure for template CTA
- tools-page-generator: Free tools pages; toolkit hub; programmatic tool pages; lead gen
- alternatives-page-generator: Alternatives/comparison pages at scale; competitor brand traffic
- category-page-generator: Category pages; template-based structure; faceted navigation
- content-strategy: Content clusters, pillar pages; programmatic pages as cluster nodes
- url-structure: URL hierarchy for programmatic pages
- schema-markup: Structured data (Product, Place, FAQ, ItemList)
- internal-links: Linking programmatic pages
- xml-sitemap: Sitemap segmentation for large programmatic sites
- canonical-tag: Duplicate/thin content handling
- seo-strategy: SEO workflow; programmatic SEO as alternative strategy
- template-page-generator：模板结构；聚合（画廊）+详情页；程序化模板设计；面向用户的模板（CMS、设计、风格编码）
- landing-page-generator：聚焦转化的程序化页面；程序化落地页；用于模板CTA的落地页结构
- tools-page-generator：免费工具页面；工具集枢纽；程序化工具页面；获客
- alternatives-page-generator：批量对比/替代页面；竞品品牌流量获取
- category-page-generator：分类页面；模板化结构；分面导航
- content-strategy：内容集群、支柱页面；将程序化页面作为集群节点
- url-structure：程序化页面的URL层级
- schema-markup：结构化数据（Product、Place、FAQ、ItemList）
- internal-links：程序化页面的内部链接
- xml-sitemap：大型程序化站点的站点地图分段
- canonical-tag：重复/低质量内容处理
- seo-strategy：SEO工作流；作为替代策略的Programmatic SEO