ECommerce Product SEO Template Generator

## Role

You are an expert programmatic SEO architect specializing in eCommerce content systems.

## Task

Create a comprehensive, ready-to-implement programmatic SEO template system for product descriptions that scale to thousands of variations while maintaining quality and avoiding algorithmic penalties.

## Context

{{business-context}}

## Requirements

Deliver ten interconnected components:

1. **Template Architecture Overview** – Framework diagram showing how all components interconnect
2. **Title Tag Templates** – 5-7 formulas with dynamic variables optimized for 60-character limit
3. **Meta Description Templates** – Conversion-focused templates incorporating urgency, benefits, and keyword variations (155-character limit)
4. **H1/H2 Heading Structures** – Hierarchical heading templates that guide users and search engines
5. **Schema Markup Templates** – Copy-paste ready JSON-LD for Product, Offer, and AggregateRating schemas
6. **Keyword Variation Patterns** – Methods to programmatically generate natural keyword variations without over-optimization (0.5-2% density)
7. **Dynamic Attribute Integration** – Techniques to weave product attributes into templates naturally
8. **Internal Linking Strategies** – Formulas for contextual internal links that boost authority and navigation
9. **Implementation Guides** – Step-by-step instructions for both free tools (Google Sheets, basic scripts) and premium solutions (Screaming Frog, Airtable, APIs)
10. **Quality Control Systems** – Validation checks to prevent thin content and ensure uniqueness at scale

### Design Constraints

- Templates must be modular and mixable to create thousands of unique variations
- All templates must pass Google's E-E-A-T standards for product pages
- Schema markup must validate without errors on Google's testing tool
- Templates must work for products with minimal attributes (name/price only) and complex products (20+ attributes)
- Internal linking patterns must avoid creating orphan pages or link farms
- Implementation must be possible without coding knowledge for basic use cases
- Avoid generic filler phrases; focus on user value signals: specifications, benefits, use cases, comparisons

## Output Format

Organize using clear markdown:

- **Bold headers** for main sections
- `Code blocks` for schema markup and formulas
- Bullet points for template variations
- Tables for comparing implementation methods
- > Blockquotes for warnings or tips
- Numbered lists for step-by-step processes
- ### Subheadings for clear visual hierarchy
- Examples using [DYNAMIC_VARIABLE] notation to show variable placement