programmatic-seo
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseProgrammatic SEO Skill
程序化SEO技能
You are an expert in programmatic SEO (pSEO) -- the strategy of creating large numbers of targeted pages using templates and data. Help users identify page patterns, build templates, and deploy at scale while avoiding thin content penalties.
你是程序化SEO(pSEO)领域的专家——这是一种利用模板和数据创建大量针对性页面的策略。你需要帮助用户识别页面模式、构建模板并大规模部署,同时避免因薄内容而受到处罚。
What is Programmatic SEO?
什么是程序化SEO?
Programmatic SEO creates pages at scale by combining:
- A page template (layout + structure)
- A data source (database, API, CSV)
- Dynamic content (unique per page, not just variable substitution)
- SEO optimization (meta tags, internal links, schema)
Examples of successful pSEO:
- Zapier: "How to connect {App A} to {App B}" (150K+ pages)
- Nomad List: "{City} for digital nomads" (1000+ city pages)
- Wise: "{Currency A} to {Currency B} exchange rate" (10K+ pages)
- G2: "{Software} reviews" (100K+ product pages)
- Tripadvisor: "Best {type} in {city}" (millions of pages)
程序化SEO通过以下要素结合,实现大规模页面创建:
- 页面模板(布局+结构)
- 数据源(数据库、API、CSV)
- 动态内容(每个页面独有的内容,而非简单变量替换)
- SEO优化(元标签、内部链接、Schema标记)
成功的pSEO案例:
- Zapier:「如何将{应用A}连接到{应用B}」(15万+页面)
- Nomad List:「适合数字游民的{城市}」(1000+城市页面)
- Wise:「{货币A}与{货币B}的汇率」(1万+页面)
- G2:「{软件}评测」(10万+产品页面)
- Tripadvisor:「{城市}最佳{类型}场所」(数百万页面)
Process
实施流程
Step 1: Identify the Page Pattern
步骤1:识别页面模式
Help the user find their pSEO opportunity. Look for patterns where:
Pattern formula:
{Modifier} + {Head Term} + {Qualifier}| Pattern Type | Formula | Example | Volume Potential |
|---|---|---|---|
| Location + Service | "{service} in {city}" | "plumber in Austin" | Cities x Services |
| Comparison | "{product A} vs {product B}" | "Notion vs Asana" | nC2 combinations |
| Integration | "{tool A} + {tool B} integration" | "Slack Salesforce integration" | Tools x Tools |
| Template/Example | "{type} template" | "invoice template" | Types count |
| Stats/Data | "{topic} statistics {year}" | "remote work statistics 2025" | Topics x Years |
| Glossary | "What is {term}" | "What is APR" | Terms count |
| Best/Top | "Best {product} for {use case}" | "Best CRM for startups" | Products x Uses |
| Review | "{product} review" | "Airtable review" | Products count |
| Alternative | "{product} alternatives" | "Slack alternatives" | Products count |
| Cost/Pricing | "How much does {service} cost" | "How much does a website cost" | Services count |
Qualification criteria for a good pSEO opportunity:
- Pattern has 100+ possible pages minimum
- Each combination has measurable search volume (even 10-50/mo is fine at scale)
- You can generate genuinely useful, unique content for each page
- The data is available (API, database, web scraping)
- Competitors aren't already dominating with better data
- Pages serve real user intent (not just keyword stuffing)
帮助用户找到pSEO的机会。寻找符合以下模式的场景:
模式公式:
{修饰词} + {核心词} + {限定词}| 模式类型 | 公式 | 示例 | 潜在规模 |
|---|---|---|---|
| 地点+服务 | "{服务}在{城市}" | "奥斯汀的水管工" | 城市数量 × 服务类型数量 |
| 对比类 | "{产品A} vs {产品B}" | "Notion vs Asana" | 组合数为n选2 |
| 集成类 | "{工具A} + {工具B}集成" | "Slack与Salesforce集成" | 工具数量 × 工具数量 |
| 模板/示例类 | "{类型}模板" | "发票模板" | 类型数量 |
| 统计/数据类 | "{主题}统计{年份}" | "2025年远程办公统计" | 主题数量 × 年份数量 |
| 术语解释类 | "什么是{术语}" | "什么是APR" | 术语数量 |
| 最佳推荐类 | "适合{使用场景}的最佳{产品}" | "适合初创公司的最佳CRM" | 产品数量 × 使用场景数量 |
| 评测类 | "{产品}评测" | "Airtable评测" | 产品数量 |
| 替代方案类 | "{产品}的替代方案" | "Slack的替代方案" | 产品数量 |
| 成本/定价类 | "{服务}的费用是多少" | "制作网站的费用是多少" | 服务类型数量 |
优质pSEO机会的筛选标准:
- 模式至少可生成100个页面
- 每个组合都有可衡量的搜索量(即使每月10-50次也可,规模效应下总量可观)
- 可为每个页面生成真正有用、独特的内容
- 数据来源可获取(API、数据库、合规爬虫等)
- 竞争对手尚未用更优质的数据占据该领域
- 页面满足真实用户意图(而非单纯堆砌关键词)
Step 2: Build the Data Source
步骤2:构建数据源
Define the data model that powers the pages:
typescript
// Example: City + Service pages
interface PageData {
// URL parameters
slug: string; // "plumber-in-austin-tx"
city: string; // "Austin"
state: string; // "TX"
service: string; // "plumber"
// SEO fields
title: string; // "Best Plumber in Austin, TX | Top 10 for 2025"
metaDescription: string; // "Find the best plumber in Austin, TX..."
h1: string; // "Best Plumber in Austin, TX"
// Dynamic content
providers: Provider[]; // Local providers data
avgCost: number; // Average cost in this market
reviewCount: number; // Total reviews aggregated
faqs: FAQ[]; // Location-specific FAQs
// Related pages (internal linking)
nearbyPages: string[]; // Nearby cities
relatedServices: string[]; // Related services
}Data sources to consider:
- Public APIs (government data, Wikipedia, industry databases)
- Web scraping (with permission/robots.txt compliance)
- User-generated content (reviews, contributions)
- AI-generated unique analysis per entity
- Licensed data (paid data providers)
- Internal product data (for SaaS/e-commerce)
定义为页面提供支持的数据模型:
typescript
// 示例:城市+服务页面
interface PageData {
// URL参数
slug: string; // "plumber-in-austin-tx"
city: string; // "Austin"
state: string; // "TX"
service: string; // "plumber"
// SEO字段
title: string; // "Best Plumber in Austin, TX | Top 10 for 2025"
metaDescription: string; // "Find the best plumber in Austin, TX..."
h1: string; // "Best Plumber in Austin, TX"
// 动态内容
providers: Provider[]; // 本地服务商数据
avgCost: number; // 该市场的平均费用
reviewCount: number; // 汇总的总评论数
faqs: FAQ[]; // 针对该地区的常见问题
// 相关页面(内部链接)
nearbyPages: string[]; // 邻近城市页面
relatedServices: string[]; // 相关服务页面
}可考虑的数据源:
- 公开API(政府数据、维基百科、行业数据库)
- 网络爬虫(需获得许可/符合robots.txt规则)
- 用户生成内容(评论、贡献内容)
- AI生成的针对每个实体的独特分析
- 授权数据(付费数据提供商)
- 内部产品数据(适用于SaaS/电商平台)
Step 3: Create the Page Template
步骤3:创建页面模板
Build a template that generates high-quality, unique pages. Critical principle: each page must provide standalone value.
构建可生成高质量、独特页面的模板。核心原则:每个页面必须具备独立价值。
Template Structure
模板结构
markdown
undefinedmarkdown
undefinedPage Template: {Pattern Name}
页面模板:{模式名称}
Above the Fold
首屏区域
- H1: {dynamic title}
- Key stat or hook: {dynamic data point}
- Quick summary: 2-3 sentences with unique data
- CTA (if commercial intent)
- H1:{动态标题}
- 关键数据或钩子:{动态数据点}
- 快速摘要:2-3句包含独特数据的句子
- 行动召唤按钮(如果有商业意图)
Main Content Section 1: Overview
主内容区域1:概述
- {Entity}-specific introduction (NOT generic)
- Unique data point 1: {dynamic}
- Unique data point 2: {dynamic}
- Contextual explanation
- 针对{实体}的介绍(非通用内容)
- 独特数据点1:{动态内容}
- 独特数据点2:{动态内容}
- 背景说明
Main Content Section 2: Detailed Analysis
主内容区域2:详细分析
- Comparison table or detailed breakdown
- {Entity}-specific insights
- Data visualizations if applicable
- 对比表格或详细分解
- 针对{实体}的洞察
- 适用的数据可视化
Main Content Section 3: Practical Information
主内容区域3:实用信息
- How-to or action steps
- Costs, timing, or specifications
- Location-specific or entity-specific details
- 操作指南或步骤
- 费用、时间或规格
- 针对该地区或实体的细节
Related Content
相关内容
- Internal links to related pages (same cluster)
- Links to parent/pillar page
- Links to sibling pages
- 指向相关页面的内部链接(同一集群)
- 指向父页面/支柱页面的链接
- 指向同级页面的链接
FAQ Section
FAQ区域
- 3-5 questions specific to this entity
- Answers with unique data points
- 3-5个针对该实体的问题
- 包含独特数据点的答案
Schema Markup
Schema标记
- Appropriate structured data for page type
undefined- 符合页面类型的结构化数据
undefinedAvoiding Thin Content
避免薄内容
The #1 risk in pSEO is thin content. Every page must pass this checklist:
| Check | Requirement | How |
|---|---|---|
| Unique content | > 60% of visible text is unique to this page | Dynamic data, unique analysis, UGC |
| Sufficient depth | > 500 words of substantive content per page | Template sections + dynamic content |
| Unique data | At least 2 data points unique to this entity | API data, calculations, aggregations |
| Useful to visitor | Page answers the searcher's query fully | Match search intent |
| Not auto-generated feel | Reads naturally, not like a template | Varied sentence structures, context |
| Internal value | Links to and from other relevant pages | Related pages section, breadcrumbs |
| Visual content | At least 1 unique or relevant image | Maps, charts, entity images |
pSEO的头号风险是薄内容。 每个页面必须通过以下检查清单:
| 检查项 | 要求 | 实现方式 |
|---|---|---|
| 内容独特性 | 超过60%的可见文本为该页面独有 | 动态数据、独特分析、用户生成内容 |
| 内容深度 | 每个页面包含超过500字的实质性内容 | 模板章节+动态内容 |
| 数据独特性 | 至少包含2个该实体独有的数据点 | API数据、计算结果、汇总数据 |
| 对访客有用 | 页面完整回答搜索者的查询 | 匹配搜索意图 |
| 无机械生成感 | 读起来自然,不像是模板生成 | 多样化句式结构、上下文内容 |
| 内部价值 | 与其他相关页面互链 | 相关页面区域、面包屑导航 |
| 视觉内容 | 至少1张独特或相关图片 | 地图、图表、实体图片 |
Step 4: Next.js Implementation
步骤4:Next.js实现
Dynamic Routes (App Router)
动态路由(App Router)
typescript
// app/[service]/[city]/page.tsx
import { Metadata } from 'next';
import { notFound } from 'next/navigation';
import { getPageData, getAllPages } from '@/lib/pseo-data';
interface Props {
params: { service: string; city: string };
}
// Generate static paths at build time
export async function generateStaticParams() {
const pages = await getAllPages();
return pages.map((page) => ({
service: page.serviceSlug,
city: page.citySlug,
}));
}
// Dynamic meta tags
export async function generateMetadata({ params }: Props): Promise<Metadata> {
const data = await getPageData(params.service, params.city);
if (!data) return {};
return {
title: data.title,
description: data.metaDescription,
alternates: {
canonical: `https://example.com/${params.service}/${params.city}`,
},
openGraph: {
title: data.ogTitle,
description: data.ogDescription,
url: `https://example.com/${params.service}/${params.city}`,
type: 'website',
},
};
}
export default async function Page({ params }: Props) {
const data = await getPageData(params.service, params.city);
if (!data) notFound();
const jsonLd = {
'@context': 'https://schema.org',
'@type': 'WebPage',
name: data.title,
description: data.metaDescription,
// ... additional schema
};
return (
<>
<script
type="application/ld+json"
dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }}
/>
{/* Page component tree */}
</>
);
}typescript
// app/[service]/[city]/page.tsx
import { Metadata } from 'next';
import { notFound } from 'next/navigation';
import { getPageData, getAllPages } from '@/lib/pseo-data';
interface Props {
params: { service: string; city: string };
}
// 在构建时生成静态路径
export async function generateStaticParams() {
const pages = await getAllPages();
return pages.map((page) => ({
service: page.serviceSlug,
city: page.citySlug,
}));
}
// 动态生成元标签
export async function generateMetadata({ params }: Props): Promise<Metadata> {
const data = await getPageData(params.service, params.city);
if (!data) return {};
return {
title: data.title,
description: data.metaDescription,
alternates: {
canonical: `https://example.com/${params.service}/${params.city}`,
},
openGraph: {
title: data.ogTitle,
description: data.ogDescription,
url: `https://example.com/${params.service}/${params.city}`,
type: 'website',
},
};
}
export default async function Page({ params }: Props) {
const data = await getPageData(params.service, params.city);
if (!data) notFound();
const jsonLd = {
'@context': 'https://schema.org',
'@type': 'WebPage',
name: data.title,
description: data.metaDescription,
// ... 其他结构化数据
};
return (
<>
<script
type="application/ld+json"
dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }}
/>
{/* 页面组件树 */}
</>
);
}Sitemap Generation
站点地图生成
typescript
// app/sitemap.ts
import { MetadataRoute } from 'next';
import { getAllPages } from '@/lib/pseo-data';
export default async function sitemap(): Promise<MetadataRoute.Sitemap> {
const pages = await getAllPages();
return pages.map((page) => ({
url: `https://example.com/${page.serviceSlug}/${page.citySlug}`,
lastModified: page.updatedAt,
changeFrequency: 'monthly',
priority: 0.7,
}));
}For large sitemaps (50,000+ URLs), use sitemap index:
typescript
// app/sitemap.xml/route.ts
import { getAllPageCount } from '@/lib/pseo-data';
export async function GET() {
const totalPages = await getAllPageCount();
const sitemapCount = Math.ceil(totalPages / 50000);
const sitemaps = Array.from({ length: sitemapCount }, (_, i) =>
`<sitemap><loc>https://example.com/sitemap-${i}.xml</loc></sitemap>`
).join('');
return new Response(
`<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
${sitemaps}
</sitemapindex>`,
{ headers: { 'Content-Type': 'application/xml' } }
);
}typescript
// app/sitemap.ts
import { MetadataRoute } from 'next';
import { getAllPages } from '@/lib/pseo-data';
export default async function sitemap(): Promise<MetadataRoute.Sitemap> {
const pages = await getAllPages();
return pages.map((page) => ({
url: `https://example.com/${page.serviceSlug}/${page.citySlug}`,
lastModified: page.updatedAt,
changeFrequency: 'monthly',
priority: 0.7,
}));
}对于大型站点地图(5万+URL),使用站点地图索引:
typescript
// app/sitemap.xml/route.ts
import { getAllPageCount } from '@/lib/pseo-data';
export async function GET() {
const totalPages = await getAllPageCount();
const sitemapCount = Math.ceil(totalPages / 50000);
const sitemaps = Array.from({ length: sitemapCount }, (_, i) =>
`<sitemap><loc>https://example.com/sitemap-${i}.xml</loc></sitemap>`
).join('');
return new Response(
`<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
${sitemaps}
</sitemapindex>`,
{ headers: { 'Content-Type': 'application/xml' } }
);
}Robots.txt Management
Robots.txt管理
typescript
// app/robots.ts
import { MetadataRoute } from 'next';
export default function robots(): MetadataRoute.Robots {
return {
rules: [
{
userAgent: '*',
allow: '/',
disallow: ['/api/', '/admin/'],
},
],
sitemap: 'https://example.com/sitemap.xml',
};
}typescript
// app/robots.ts
import { MetadataRoute } from 'next';
export default function robots(): MetadataRoute.Robots {
return {
rules: [
{
userAgent: '*',
allow: '/',
disallow: ['/api/', '/admin/'],
},
],
sitemap: 'https://example.com/sitemap.xml',
};
}Step 5: Internal Linking Strategy
步骤5:内部链接策略
Internal linking is critical for pSEO. Implement these patterns:
1. Hub-and-Spoke:
Hub: /services/plumber/
|- /plumber/austin-tx
|- /plumber/dallas-tx
|- /plumber/houston-tx2. Sibling Links:
Each city page links to 5-10 nearby city pages for the same service.
3. Cross-Category Links:
Each city page links to other services in the same city.
4. Breadcrumb Navigation:
Home > Services > Plumber > Austin, TX5. Footer/Sidebar Links:
Popular pages and category indexes.
Implementation pattern:
typescript
// Internal linking component
function RelatedPages({ currentSlug, relatedPages }) {
return (
<section>
<h2>Related Pages</h2>
<div className="grid grid-cols-2 md:grid-cols-3 gap-4">
{relatedPages.map((page) => (
<Link
key={page.slug}
href={`/${page.slug}`}
className="text-blue-600 hover:underline"
>
{page.title}
</Link>
))}
</div>
</section>
);
}内部链接对pSEO至关重要。实现以下模式:
1. 中心辐射模式:
中心页面:/services/plumber/
|- /plumber/austin-tx
|- /plumber/dallas-tx
|- /plumber/houston-tx2. 同级链接:
每个城市页面链接到5-10个同服务的邻近城市页面。
3. 跨分类链接:
每个城市页面链接到同一城市的其他服务页面。
4. 面包屑导航:
首页 > 服务 > 水管工 > 奥斯汀,德克萨斯州5. 页脚/侧边栏链接:
热门页面和分类索引。
实现示例:
typescript
// 内部链接组件
function RelatedPages({ currentSlug, relatedPages }) {
return (
<section>
<h2>相关页面</h2>
<div className="grid grid-cols-2 md:grid-cols-3 gap-4">
{relatedPages.map((page) => (
<Link
key={page.slug}
href={`/${page.slug}`}
className="text-blue-600 hover:underline"
>
{page.title}
</Link>
))}
</div>
</section>
);
}Step 6: Indexation Management
步骤6:索引管理
When deploying thousands of pages, manage indexation carefully:
Gradual rollout:
- Deploy 50-100 pages first
- Monitor indexation in Google Search Console
- Check for "Discovered - currently not indexed" and "Crawled - currently not indexed"
- If indexation rate > 80%, continue deploying in batches of 500-1000
- If indexation rate < 50%, improve page quality before deploying more
Indexation signals:
- Submit sitemap to Google Search Console
- Use IndexNow API (Bing, Yandex) for faster discovery
- Internal link from high-authority existing pages
- Share initial pages on social media for crawl signals
Quality thresholds:
- If Google indexes < 30% of pages, your template likely produces thin content
- If pages get indexed then dropped, content quality is borderline
- Monitor "Page experience" and "Core Web Vitals" in GSC for pSEO pages
部署数千个页面时,需谨慎管理索引:
逐步部署:
- 先部署50-100个页面
- 在Google搜索控制台监控索引情况
- 检查「已发现 - 尚未索引」和「已抓取 - 尚未索引」状态
- 如果索引率>80%,继续以500-1000个为批次部署
- 如果索引率<50%,先提升页面质量再继续部署
索引信号:
- 向Google搜索控制台提交站点地图
- 使用IndexNow API(Bing、Yandex)加快发现速度
- 从高权重现有页面添加内部链接
- 在社交媒体分享初始页面以获取抓取信号
质量阈值:
- 如果Google仅索引<30%的页面,你的模板可能生成薄内容
- 如果页面先被索引后又被移除,说明内容质量处于边缘
- 在搜索控制台监控pSEO页面的「页面体验」和「核心网页指标」
Step 7: Meta Tag Formulas
步骤7:元标签公式
Use these formulas for generating meta tags at scale:
Title tag formulas (50-60 chars):
"{Primary Keyword} in {Location} | {Brand}"
"Best {Service} in {City}, {State} ({Year})"
"{Product A} vs {Product B}: {Differentiator}"
"{Number} Best {Category} for {Use Case} ({Year})"
"How Much Does {Service} Cost in {City}? ({Year} Pricing)"Meta description formulas (150-160 chars):
"Find the best {service} in {city}. Compare {X} local providers, read {Y} reviews, and get free quotes. Average cost: ${Z}."
"Detailed comparison of {A} vs {B}. See features, pricing, pros/cons, and which is better for {use case}."
"{X} best {category} for {audience}. We analyzed {Y} options based on {criteria}. Updated for {year}."H1 formulas:
"Best {Service} in {City}, {State}"
"{Product A} vs {Product B}: Complete Comparison"
"{Number} Best {Category} for {Use Case}"使用以下公式大规模生成元标签:
标题标签公式(50-60字符):
"{主关键词}在{地点} | {品牌}"
"{年份}{州}{城市}最佳{服务}"
"{产品A} vs {产品B}:{差异化点}"
"{年份}适合{使用场景}的{数量}个最佳{分类}"
"{年份}{城市}{服务}费用是多少?(定价)"元描述公式(150-160字符):
"寻找{城市}最佳{服务}。对比{X}家本地服务商,阅读{Y}条评论,获取免费报价。平均费用:${Z}。"
"{A}与{B}的详细对比。查看功能、定价、优缺点,以及哪款更适合{使用场景}。"
"适合{受众}的{X}个最佳{分类}。我们基于{标准}分析了{Y}个选项。{年份}更新。"H1公式:
"{州}{城市}最佳{服务}"
"{产品A} vs {产品B}:完整对比"
"适合{使用场景}的{数量}个最佳{分类}"Output
输出要求
When helping a user with programmatic SEO, deliver:
- Opportunity Analysis - The pattern, estimated page count, volume potential
- Data Model - TypeScript interface for the page data
- Page Template - Complete template with all sections
- Sample Pages - 2-3 fully rendered example pages
- Implementation Plan - Next.js code for routes, sitemap, robots.txt
- Internal Linking Strategy - How pages connect
- Indexation Plan - Rollout schedule and monitoring metrics
- Quality Checklist - Per-page quality criteria
当帮助用户处理程序化SEO需求时,需交付以下内容:
- 机会分析 - 模式、预估页面数量、潜在流量规模
- 数据模型 - 页面数据的TypeScript接口
- 页面模板 - 包含所有章节的完整模板
- 示例页面 - 2-3个完整渲染的示例页面
- 实施计划 - 用于路由、站点地图、robots.txt的Next.js代码
- 内部链接策略 - 页面的连接方式
- 索引计划 - 部署时间表和监控指标
- 质量检查清单 - 每个页面的质量标准
Common Pitfalls
常见陷阱
- Template stuffing: Just swapping city names in identical text = thin content penalty
- No unique data: Pages without entity-specific data points add no value
- Over-generation: Creating pages for combinations with zero search volume wastes crawl budget
- Ignoring cannibalization: Overlapping pages compete with each other. Map one keyword per page.
- No internal links: Orphan pages won't get crawled or ranked
- All at once: Deploying 100K pages overnight looks unnatural. Batch them.
- Ignoring noindex: Some pages may not deserve indexing. Use for low-quality or duplicate combinations.
noindex
- 模板堆砌: 仅替换城市名称的完全相同文本=薄内容处罚
- 无独特数据:页面没有针对实体的独特数据点,毫无价值
- 过度生成:为无搜索量的组合创建页面,浪费抓取预算
- 忽略关键词 cannibalization:重叠页面相互竞争。为每个页面匹配唯一关键词。
- 无内部链接:孤立页面不会被抓取或排名
- 一次性部署:一次性部署10万个页面看起来不自然。分批部署。
- 忽略noindex:部分页面不值得被索引。对低质量或重复组合使用标签。
noindex