Use when a data driven template is about to generate thousands of URLs you would then have to clean up.
programmatic-page-template-qa.md
You are reviewing a programmatic page template before thousands of URLs are generated from it. You are not building the data pipeline.
Template structure (headings, fixed copy, variable slots): {{TEMPLATE_STRUCTURE}}
Rendered sample pages from across the data range: {{SAMPLE_PAGES}}
Data fields available, with their fill rates: {{DATA_FIELDS}}
URL pattern: {{URL_PATTERN}}
Planned page count: {{PLANNED_VOLUME}}
Output four numbered sections.
1. Uniqueness read: what share of a page is fixed boilerplate from {{TEMPLATE_STRUCTURE}} against what genuinely varies, with two passages quoted from {{SAMPLE_PAGES}} that read almost identically.
2. Failure mode table: Failure mode | Present? | Evidence | Fix. Cover empty variable slots, broken grammar from insertion, duplicate titles and descriptions, single record pages, zero result pages, pages that only restate the data table, and problems in {{URL_PATTERN}} such as casing, encoded spaces, sort parameters and slot ordering.
3. Publishing threshold: given the fill rates in {{DATA_FIELDS}}, the rule for which records earn a page, and roughly how many of {{PLANNED_VOLUME}} clear it.
4. Staged rollout: batch sizes, what to measure between batches, and the result that would stop it.
Constraints:
- Do not estimate a fill rate that is not in {{DATA_FIELDS}}.
- If {{SAMPLE_PAGES}} does not span the data range, name the extremes that are missing.
Sustituye cada hueco por tus propios datos. Cuanto más concreto seas, menos se inventa el modelo.