Project Overview
What: Automated SEO/AEO content generation pipeline for Holistic Health Educators (HHE) and the Lily Fields brand.
Why: Competitor analysis shows top holistic certification programs are poorly optimized for AI search engines — first-mover advantage in AEO positioning.
Scale: 60-page backlog across 5 page types. Weekly publishing cadence after an initial rollout of 15–20 core pages.
Voice: All content written in Karen Hurd's brand voice via RAG retrieval from the existing holistic health knowledge base.
System Architecture
| Layer | Technology | Purpose |
|---|---|---|
| Compute | Cloudflare Worker (TypeScript) | API + dashboard serving |
| Database | Cloudflare D1 (SQLite) | Topics, pages, QA scores, audit logs |
| File Storage | Cloudflare R2 | Draft HTML/markdown content |
| Content Generation | Google Gemini Flash | Fast draft generation |
| Quality Scoring | Google Gemini Pro | Deep QA gate enforcement |
| Brand Voice RAG | Existing proxy-chat HTTP API | ChromaDB knowledge base |
| Dashboard | Vanilla HTML/CSS/JS | No build step needed |
Generation Pipeline Flow
Each topic goes through async generation: RAG retrieval → Gemini Flash draft → Gemini Pro QA scoring → D1/R2 storage. The dashboard polls for completion and shows results with full audit trail.
QA Scoring System
Required Gates (Binary Pass/Fail)
| Gate | Pass Criteria |
|---|---|
| H1 count | Exactly 1 |
| H2 count | >= 2 |
| Meta description | Present, 120–160 chars |
| FAQ block | >= 3 Q&A pairs |
| Compliance | No banned health claims |
Scored Checks
- Brand Voice Alignment — 30 pts
- Content Depth — 20 pts
- Internal Links — 15 pts
- BLUF Intro — 15 pts
- Schema Markup — 10 pts
- CTA Block — 10 pts
Page Types
1Program Page
Course overview, curriculum, outcomes, enrollment CTA
2Comparison Page
Feature table, pros/cons, recommendation
3Alternatives Page
Top alternatives list, why-us differentiation
4Career Page
Career path, requirements, salary, how-to-start
5Accreditation Page
Details, standards, credibility markers
Topic Status Flow
Topics progress through the pipeline: pending → generating → qa_pass / qa_fail → approved. In Phase 2, the flow extends to scheduled → published via WordPress CMS integration. Failed QA runs can be retried or re-generated.
Implementation Timeline
Phase 1 — "Prove the Pipeline": 7 implementation chunks, 12 tasks, TDD approach. Scaffold through dashboard + end-to-end testing.
Phase 2 — "Full Stack": WordPress CMS adapter, calendar scheduling, Cloudflare Access auth, and bulk operations.
Outstanding Client Inputs
The following decisions are needed from Blake before implementation can begin. Submit responses via the decision form.
- 60-page topic plan and rollout order
- Gold-standard examples per page type
- Acceptance checklist and scoring rubric
- Cloudflare account access
- Gemini API key
- WordPress site details (Phase 2 prep)