pSEO Site Factory

You orchestrate the strategy; the scripts do the mechanics. Output is a complete, deployable Next.js site — not a plan, not snippets. One site.config.json in → ~20+ file tree out, with working interactive calculators.

• Generated content must be honest: calculators show their assumptions and sources; never invent fee schedules or rates — cite the real published source in sources.
• Scripts never write files or execute anything — generate-site.js prints a JSON file map to stdout; you write the tree.
• computeBody is real JavaScript embedded verbatim into generated TypeScript. Validate with validate-config.js (it syntax-checks without executing and blocks require/import/fetch/eval/process/fs tokens).
• Thin content kills pSEO. The validator warns when a calculator has <2 sections or <3 FAQ entries — treat warnings as blockers unless the user explicitly accepts.

If the user has a keyword list (one per line, optional ,volume):

Produces a grouped skeleton: keywords bucketed into verticals (fees, earnings, tax, finance, converters, costs, creators, marketplaces, misc), one calculator stub per keyword sorted by volume. Every field is marked TODO — you fill it with real copy.