Programmatic SEO Architect Prompt Template

ROLE: You are a senior full-stack engineer and technical SEO architect who has built and scaled programmatic SEO systems to 100,000+ pages for SaaS and marketplace products. CONTEXT: My Next.js project is generating programmatic pages from structured data, but I'm running into issues — Google is either ignoring the pages, flagging them for thin/duplicate content, or my architecture doesn't scale cleanly. I need a comprehensive audit and rebuild plan. TASK: Audit and design a scalable programmatic SEO system for my Next.js project that handles [PAGE_COUNT] pages safely and ranks well in search. RULES: • Cover all 8 areas below — do not skip any even if brief • For each area, provide: a diagnosis of common issues, your recommended approach, and at least one code snippet or concrete example • Recommend specific Next.js rendering strategies (SSG/ISR/SSR) per page type with justification • All code examples must be production-quality TypeScript using Next.js App Router conventions • Flag the 3 highest-risk areas for this specific use case CONSTRAINTS: Focus on Next.js App Router (not Pages Router). Use TypeScript in all code examples. Prioritise indexability and Core Web Vitals over feature completeness. EDITABLE VARIABLES: • [PROJECT_DESCRIPTION] — framework version, current page count, main content type (e.g. "Next.js 14, 5,000 location pages for a local services directory") • [PAGE_COUNT] — target scale of programmatic pages • [SCHEMA_TYPE] — the structured data type that fits your pages (Article, FAQ, Product, LocalBusiness, etc.) • [CURRENT_PROBLEM] — what's going wrong right now (GSC errors, low impressions, duplication warnings) OUTPUT FORMAT: 1. AUDIT — Issues, risks, and architectural gaps 2. ARCHITECTURE — Dynamic routing strategy + folder structure + template pattern 3. SEO FOUNDATIONS — Per-page metadata implementation with code example 4. STRUCTURED DATA — JSON-LD schema example for [SCHEMA_TYPE] 5. INTERNAL LINKING — Hub-and-spoke system design 6. SITEMAP STRATEGY — Sitemap index + grouped sitemaps code 7. PERFORMANCE — Rendering strategy recommendation + Core Web Vitals notes 8. SAFEGUARDS — Thin content checks, duplicate slug prevention, content variation rules QUALITY BAR: After implementing this architecture, every new page added to the system should be automatically SEO-correct with zero manual intervention needed. The system should scale from 100 to 10,000 pages without architectural changes.