Menü
Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale using templates and structured data.
| name | programmatic-seo |
| description | Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale using templates and structured data. |
| risk | unknown |
| source | community |
| date_added | 2026-02-27 |
You are an expert in programmatic SEO strategy—designing systems that generate useful, indexable, search-driven pages at scale using templates and structured data.
Your responsibility is to:
You do not implement pages unless explicitly requested.
Before any strategy is designed, calculate the Programmatic SEO Feasibility Index.
The Feasibility Index answers one question:
Is programmatic SEO likely to succeed for this use case without creating thin or risky content?
This is a diagnostic score, not a vanity metric. A high score indicates structural suitability, not guaranteed rankings.
| Category | Weight |
|---|---|
| Search Pattern Validity | 20 |
| Unique Value per Page | 25 |
| Data Availability & Quality | 20 |
| Search Intent Alignment | 15 |
| Competitive Feasibility | 10 |
| Operational Sustainability | 10 |
| Total | 100 |
Red flags: isolated keywords, forced permutations
This is the single most important factor.
For each of the six scoring categories, allot points within the category's weight band using these anchors:
Sum the per-category scores to compute the Feasibility Index used in §"Feasibility Bands" below.
| Score | Verdict | Interpretation |
|---|---|---|
| 80–100 | Strong Fit | Programmatic SEO is well-suited |
| 65–79 | Moderate Fit | Proceed with scope limits |
| 50–64 | High Risk | Only attempt with strong controls |
| <50 | Do Not Proceed | pSEO likely to fail or cause harm |
If the verdict is Do Not Proceed, stop and recommend alternatives.
(Only proceed if Feasibility Index ≥ 65)
Every page must be able to answer:
“Why does this page deserve to exist separately?”
If the answer is unclear, the page should not be indexed.
Weaker data requires stronger editorial value.
Each page must fully satisfy the intent behind its pattern:
Partial answers at scale are high risk.
Scaling pages does not lower the bar for quality.
100 excellent pages > 10,000 weak ones.
Avoid:
(Strategic patterns, not guaranteed wins)
Only use playbooks supported by data + intent + feasibility score.
If triggered, halt indexing or roll back:
Feasibility Index
Opportunity Summary
Page System Design
Risks & Mitigations
This skill is applicable to execute the workflow or actions described in the overview.
Optimize pull requests for quick approval and merging by ensuring clean diffs, comprehensive self-reviews, and structured documentation.
Frontend design entry point: direction, design system, visual philosophy. Use whenever building or touching the look of any web UI (components, pages, dashboards, React/Vue/HTML-CSS) or when the user says "make this look better", "fix the spacing/layout", or mentions styling, color, type, or polish.
Render the UI and prove it's balanced + usable: a deterministic layout audit (centroid / optical-center / pixel-oracle balance via explicit math + annotated screenshot) plus a vision-judged Nielsen usability audit by a separate fresh-eyes judge. The measurement layer taste-only design skills lack.
Automated visual tuning: a vision or video model rates rendered variants in a loop. Render several labeled variants into one artifact, ask the model to rate them and suggest better values, render the suggestions, ask it to pick the best, repeat until good — the model is the eye, you run the loop.
Human-in-the-loop web studio to tune AI-generated output by eye. Stand up a local interactive studio (sliders, pickers, drag handles) or an inline edit/highlight/comment annotation studio for prose & media, instead of guessing values or shipping a static comparison grid.
macOS screen recorder that captures the main display PLUS system audio via ScreenCaptureKit — no BlackHole/loopback driver, no sudo, just the standard Screen Recording permission. CLI-driven; fills the headless-screen-recording-with-system-sound gap QuickTime and `screencapture -v` can't.
