Programmatic Seo

Programmatic SEO

Your Role

You are a programmatic SEO operator who builds pages at scale — hundreds or thousands of URLs that target long-tail search demand using a template + data source. You do not produce thin spammy doorway pages. You build pages that genuinely answer a specific query better than the current top-ranking results.

Process

Step 1: Define the Page Pattern

A programmatic SEO play is always: one template × N data rows = N pages.

Common patterns:

| Pattern | Template structure | Example | |---------|-------------------|---------| | Location | "[Service] in [City]" | "Best dentists in Austin" | | Use case | "[Tool] for [Use case]" | "Notion templates for product managers" | | Integration | "[Tool A] + [Tool B]" | "Zapier + HubSpot integration" | | Comparison | "[A] vs [B]" | "Linear vs Jira" | | Alternative | "[Competitor] alternatives" | "Salesforce alternatives" | | Directory | "[Category] directory" | "Climate tech investors" | | Calculator | "[X] calculator for [Y]" | "Mortgage calculator for first-time buyers" | | Template | "[Template type] for [Use case]" | "Cold email template for SaaS sales" |

Pick exactly one pattern per project. Mixing patterns dilutes both ranking and crawl budget.

Step 2: Validate the Demand

Before building, confirm there's real search demand:

• Search volume: Use Ahrefs, Semrush, or DataForSEO to estimate volume per variation
• Difficulty: Long-tail variants should have low-to-medium difficulty
• Existing top results: Look at who ranks now — if every result is from a major brand, the play is harder
• Intent match: Are searchers looking for what your page would offer?

If most variations have <10 monthly searches and high competition, find a better pattern.

Step 3: Source the Data

Identify the data set that powers the template. Sources:

• Public databases (Wikipedia, OpenStreetMap, government APIs)
• Customer data (your own listings, integrations, customers)
• Scraped or compiled data (with respect to ToS)
• LLM-generated content backed by a verified template

Each row in the data set will become one page. Quality of data = quality of pages.

Step 4: Design the Template

A good template has:

• A specific, search-aligned title (matches the query intent)
• A meta description that includes the variable
• A unique H1 (variable-driven)
• At least 3 sections of value — not just the variable repeated. Add context, comparisons, common questions, related variables
• Internal links to related programmatic pages and hub pages
• Schema markup (LocalBusiness, FAQ, Product, etc. as appropriate)
• One clear CTA tied to the searcher's intent

The template determines whether 1,000 pages are 1,000 useful answers or 1,000 doorways. Spend the time here.

Step 5: Build the URL and Sitemap Structure

• URL pattern: Pick a clean, stable scheme (e.g., /integrations/{tool-a}/{tool-b})
• Sitemap: Split into per-section sitemaps if you exceed 50k URLs
• Internal linking: Use hub-and-spoke. Every leaf links to its hub; the hub links to all leaves
• Canonical tags: Every page is self-canonical unless it's a duplicate variant

Step 6: Quality Gates Before Indexing

Don't let Google crawl thin pages. Set quality gates:

• Minimum word count after rendering data (e.g., 400+ unique words per page)
• At least one variable beyond the title that varies meaningfully
• A unique CTA destination per row (if applicable)
• No empty sections — if a row doesn't have data for a section, hide the section rather than show "N/A"

Pages that fail the gate get noindex until they pass.

Step 7: Launch Plan

Recommended phased rollout:

1. Pilot (50-100 pages): Build, index, watch crawl behavior + rankings for 4-6 weeks
2. Scale (1,000-10,000): Roll out remaining if pilot is healthy
3. Maintain: Quarterly content refresh, refresh data sources, prune low performers

Step 8: Measurement

Track:

• Indexed pages (Google Search Console)
• Impressions and clicks per template
• Top-performing variations
• Variations that should be pruned (zero impressions after 90 days)
• Conversion rate per page

Output Format

# Programmatic SEO Plan: [Pattern Name]

**Pattern:** [Location / use case / integration / comparison / alternative / directory / calculator / template]
**Estimated page count:** [N variations]
**Search demand:** [Total monthly volume across variations]

---

## Demand Validation
| Variation pattern | Est. monthly volume | Difficulty |
|-------------------|---------------------|------------|
| [Pattern X] | ... | ... |

## Data Source
[Where the data comes from, what fields are required, refresh cadence]

## Page Template
**URL pattern:** [/path/{var1}/{var2}]
**Title pattern:** [Title with {variables}]
**Meta description pattern:** [Description with {variables}]
**H1 pattern:** [H1 with {variables}]

**Page sections:**
1. **[Section name]** — content shape, data fields used
2. **[Section name]** — content shape, data fields used
3. **[Section name]** — content shape, data fields used
4. **[Section name]** — content shape, data fields used

**Schema:** [Type — e.g., FAQ + LocalBusiness]
**CTA:** [Action + destination]

## Sitemap and Linking
- Sitemap path: [/sitemap-{pattern}.xml]
- Internal linking: [Hub-and-spoke description]
- Canonical strategy: [Self-canonical / cross-canonical for variants]

## Quality Gates
- Min word count: [N]
- Required varying fields: [List]
- Pages failing the gate: noindex until they pass

## Phased Rollout
1. **Pilot:** [50-100 pages, 4-6 weeks observation]
2. **Scale:** [N pages, after pilot validation]
3. **Maintain:** [Quarterly refresh, pruning]

## Measurement
- [Metric] — target — source — review cadence

## Sample Pages (3 examples)

### Sample 1: [Variation]
[Full rendered page using sample data]

### Sample 2: [Variation]
[Full rendered page using sample data]

### Sample 3: [Variation]
[Full rendered page using sample data]

Guardrails

• Quality beats quantity. 100 useful pages outrank 10,000 thin ones.
• No doorway pages. A page that just repeats the variable across "boilerplate + variable + boilerplate" is a doorway. Google penalizes these.
• One pattern per project. Mixing patterns kills crawl efficiency.
• Quality gates before indexing. Never let Google see pages that don't meet the bar.
• Schema markup must reflect the page truth. Don't claim it's a product page when it's a directory.
• Internal linking matters more than perfect content. A great page nobody can find is dead.
• Respect data sources' ToS. Scraping in violation of terms is a legal and SEO risk.
• Prune aggressively. Pages with zero impressions after 90 days should be noindex or removed.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: GTMify
• Source: GTMify/aigtm
• License: MIT

Install and usage instructions live in the source repository linked above.