Template Architecture
Template architecture defines how programmatic pages are structured, how metadata is generated, and how content is differentiated across pages.
Learning Focus
After this lesson you can design page templates, metadata generation rules, and content modules for programmatic pages.
This lesson covers the seven template architecture areas (leaves 9.2.1–9.2.7): page template design, metadata generation rules, heading generation rules, internal linking logic, schema generation logic, unique content modules, and conversion module design.
Page Template Design
Design a template structure that generates unique, valuable pages.
Template components:
| Component | Description | Requirement |
|---|---|---|
| Hero section | Page title, intro | Generated from data |
| Main content | Body of the page | Mix of dynamic and static content |
| Supporting modules | FAQ, related content, CTAs | Dynamic based on page topic |
| Metadata | Title, description, schema | Generated from data + rules |
| Navigation | Breadcrumbs, internal links | Dynamic based on page category |
Template types:
| Template Type | Best For | Example |
|---|---|---|
| Single-entity page | One product, person, or listing | "Widget Pro 2000" |
| List page | Multiple entities | "Plumbers in Austin, TX" |
| Comparison page | Comparing entities | "Email platform X vs Y" |
| Location page | Location-based content | "Email Marketing Agencies in Chicago" |
Metadata Generation Rules
Core Concept
Define rules for generating unique titles, descriptions, and H1s for each page.
Metadata generation patterns:
| Page Type | Title Pattern | Description Pattern |
|---|---|---|
| List page | "[Category] in [Location] — [Site Name]" | "Find the best [category] in [location]. Compare [X] providers..." |
| Single entity | "[Entity Name] — [Category]" | "Learn about [entity name], a [category] that [key feature]..." |
| Comparison | "[Entity A] vs [Entity B]: [Topic] Comparison" | "Compare [Entity A] and [Entity B] for [use case]..." |
Metadata rules:
- Each generated title must be unique across all pages.
- Aim to keep titles within recommended character limits (50-60 characters). Google truncates by pixel width, not character count.
- Descriptions must be unique and relevant.
- H1s should be descriptive and match the primary query pattern.
Heading Generation Rules
Generate heading structure dynamically from data.
Heading patterns:
| Page Type | Heading Structure |
|---|---|
| List page | H1: topic → H2: "Best [category] in [location]" → H3: per-listing headings |
| Single entity | H1: entity name → H2: "Overview" → H2: "Features" → H2: "Reviews" |
| Comparison | H1: comparison → H2: "About [A]" → H2: "About [B]" → H2: "Comparison" → H2: "Verdict" |
Heading uniqueness:
- Each H2/H3 should be unique per page where possible.
- Use dynamic insertion of keywords into headings.
- Avoid identical heading structures across all pages.
Internal Linking Logic
Define automated internal linking rules.
Linking rules:
| Rule | Implementation |
|---|---|
| Category links | Every page links to its parent category |
| Location links | Every location page links to broader location |
| Related pages | "Related [category] in [nearby location]" |
| Breadcrumbs | Auto-generated from data hierarchy |
| Content links | Contextual links where relevant data exists |
Linking quality checks:
- No link to noindexed or thin pages from high-authority pages.
- Link anchor text is descriptive and relevant.
- Link density is appropriate (not too many, not too few).
Schema Generation Logic
Generate structured data dynamically from template data.
Schema types by page type:
| Page Type | Schema Types |
|---|---|
| Single entity | Product, Person, LocalBusiness, or service-specific schema |
| List page | ItemList with listItem pointing to each entity |
| Comparison | Product (for each product) |
| Location page | LocalBusiness with geo coordinates |
Schema generation rules:
- Every page should have at least one relevant schema type where applicable. Schema is valuable but not mandatory for all page types. Simple content pages may not benefit from structured data.
- Schema properties are populated from structured data.
- Schema validates against Rich Results Test.
- Cross-page schema (ItemList) correctly references individual entity pages.
Unique Content Modules
Design content modules that can be dynamically populated to differentiate each page.
Content module types:
| Module | Source | Purpose |
|---|---|---|
| Intro paragraph | Data fields + templates | Unique intro for each page |
| Feature list | Structured data attributes | Distinguish entities |
| FAQ | Data-driven questions | Address common queries per topic |
| Statistics | Data-derived metrics | Add credibility |
| User reviews | Aggregated review data | Social proof |
| Related listings | Nearby or similar entities | Cross-linking |
Content variation requirements:
- Content should be substantially differentiated from other pages on the same topic. While no fixed uniqueness threshold exists publicly, aim for clear differentiation in angle, depth, or data. Use canonical tags for intentionally overlapping content.
- Use multiple data sources to generate unique content.
- Combine static (written) content with dynamic (data-generated) content.
Conversion Module Design
Design conversion elements appropriate for each programmatic page type.
Conversion modules by page type:
| Page Type | Primary Conversion | Module |
|---|---|---|
| List page | Click-through to listing page | "View details" link per listing |
| Single entity | Lead generation or purchase | "Contact", "Buy now", "Get quote" |
| Comparison | Demo or trial signup | "Try [product] free" |
| Location page | Local action | "Call now", "Get directions" |
Conversion module testing:
- A/B test conversion modules on the first 500 pages.
- Optimize placement, copy, and design based on results.
- Roll out winning modules to remaining pages.
Workflow
- Design the page template structure: hero section (data-generated), main content modules (dynamic + static mix), supporting modules (FAQ, related content, CTAs), metadata, navigation (breadcrumbs, internal links).
- Define metadata generation rules: unique title per page (50-60 character target), unique description (150-160 character target), unique H1. Write generation patterns that produce distinct, human-readable output.
- Build content variation modules: intro paragraphs, feature lists, statistics, reviews, and FAQs populated from structured data. Ensure each page's output is substantially differentiated.
- Implement schema generation: Product, LocalBusiness, ItemList, or FAQPage schema generated from template data. Validate all schema types with Rich Results Test on sample pages.
- Define internal linking logic: category-to-child, location-to-nearby, breadcrumbs, and related content links. Ensure links point only to quality, indexed pages.
Common Mistakes
warning
- Identical content structure with only keyword substitution: Changing the city name or product name in an otherwise identical template produces thin content. Build multiple varied sentence templates and rotate their use.
warning
- Non-unique metadata generation: Title tags that differ only by a single word (e.g., "Plumbers in [City]" with identical descriptions) create near-duplicate metadata that may be filtered from results.
- No schema validation: Generating schema from template data without Rich Results Test validation can produce invalid schema at scale. Validate on a sample of 50-100 pages before full rollout.
- Linking to thin or noindexed pages: "Related listings" or "nearby locations" modules that link to pages below the quality threshold waste link equity and create crawl paths to low-value pages.
- Static templates with no content modules: A single template with one static paragraph and data substitution creates near-identical pages. Use multiple dynamic content modules and sentence variations.
Checklist
- Design page template with dynamic content modules and varied sentence structures
- Define unique metadata generation rules per page type
- Build at least 3-4 content modules (intro, features, stats, FAQ) with data-driven variation
- Implement schema generation with Rich Results Test validation on samples
- Define internal linking rules: breadcrumbs, category links, related content
- Ensure links only point to quality pages above the indexation threshold
- Test template output on 50-100 pages before full rollout
- Spot-check generated pages monthly for content uniqueness and quality