QuQi
SEO

Programmatic template QA

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
.md herunterladen
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.

Vor dem Start ausfüllen

Ersetzen Sie jeden Platzhalter durch Ihre eigenen Angaben. Je genauer Sie sind, desto weniger erfindet das Modell.

  • {{TEMPLATE_STRUCTURE}}
  • {{SAMPLE_PAGES}}
  • {{DATA_FIELDS}}
  • {{URL_PATTERN}}
  • {{PLANNED_VOLUME}}

So wird das Ergebnis besser

  1. Include a sparse record and a rich one in the samples, since the sparse ones are what get indexed badly.
  2. Set the publishing threshold before launch; pruning later costs far more than never generating the page.
  3. Ship the first batch small enough that you can still fix the template without a mass de-index.