domains / families / marketing / programmatic-seo
When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy. When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," "templated landing pages," or "which CMS for pSEO." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.
The copies overlap on the core pSEO workflow (assessment, data hierarchy, playbooks, template design, internal linking, and indexation), but each contains material steps the others lack. coreyhaines31 and LeoYeAI are near-identical reproductions of the same procedure, while kostja94 adds an AI-assisted generation layer, a page-skill matrix, and a Contextus context-loading step. nowork-studio is a thin wrapper that delegates to a separate WORKFLOW.md and adds an argument-hint for site URL and pattern. Crowning one copy would hide the AI-enhanced differentiation approach and the external workflow reference.