Plan, specify, build, audit, or scale search pages generated from structured data: location and service pages, integration and compatibility pages, comparison sets, use-case and role pages, glossaries, galleries, directories, and data explorers, each with a data contract, template contract, index rules, quality sampling, and bounded rollout. Use for programmatic SEO where every page can carry distinct utility; use search-health for site-wide diagnosis.
Installs into .claude/skills of the current project.
Are you the author of Template Pages?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/mtent-template-pages)
---
name: template-pages
description: Plan, specify, build, audit, or scale search pages generated from structured data: location and service pages, integration and compatibility pages, comparison sets, use-case and role pages, glossaries, galleries, directories, and data explorers, each with a data contract, template contract, index rules, quality sampling, and bounded rollout. Use for programmatic SEO where every page can carry distinct utility; use search-health for site-wide diagnosis.
license: MIT
metadata:
version: "2.0.0"
author: MTEnt
---
# Template Pages
Scale data-backed usefulness, not name-swapped doorway pages.
If `.agents/marketing-context.md` exists, read it first; it is the truth file every skill in this hub shares, and its evidence states are constraints. Read [programmatic-system.md](references/programmatic-system.md) for playbook families, the selection test, data and template contracts, indexing rules, quality checks, and rollout.
## Operating contract
1. Define audience, repeated intent family, page job, reliable data, product relationship, and the number of genuinely useful combinations.
2. Choose a playbook only when page-level uniqueness can be explained for a sample page.
3. Specify source ownership, freshness, missing-data behavior, template, URL, canonical, internal links, and index eligibility.
4. Validate normal, sparse, extreme, duplicate, stale, and error cases.
5. Launch a bounded cohort and expand only when quality and observed behavior hold.
Do not index thin permutations, fabricate local presence, or generate unsupported comparisons at scale.
## Return
Playbook choice, intent map, data schema, template specification, sample pages, index rules, internal linking, validation, rollout, monitoring, ownership, and retirement.
