HHE SEO/AEO Pipeline — Decision Form

Decision 1

60-Page Topic Plan

How would you like to provide the 60-page topic plan and rollout order?

A) Share existing spreadsheet/document Recommended

Send the topic list you already have. We'll import it into the pipeline's topic queue. Preferred format: CSV or spreadsheet with columns for Title, Page Type, Target Keyword, Priority, Persona, CTA Type.

B) Collaborative session to build the list

We schedule a working session to build the topic queue together, mapping each topic to page types and keywords.

C) I'll provide it later

Defer this decision. Note: implementation can begin on the pipeline infrastructure, but we can't test real content until the topic list is loaded.

Decision 2

Gold-Standard Examples

Can you share gold-standard examples for each of the 5 page types?

A) Yes, I have examples ready Recommended

Share one exemplary page per type (program, comparison, alternatives, career, accreditation). These calibrate the prompt templates and QA scoring.

B) I need help identifying good examples

We'll review existing HHE/competitor pages together to select the best references for each type.

C) I'll provide them during development

Defer until prompt template work begins. Note: templates will be generic until calibrated with real examples.

Decision 3

Acceptance Checklist & Scoring

Do you have an acceptance checklist and scoring rubric to share?

A) Yes, I'll share my checklist Recommended

Share the document. We'll validate against our proposed QA gates and scoring weights (75-point threshold, brand voice 30pts, content depth 20pts, etc.).

B) Use the proposed scoring as-is

The current spec defines 5 required gates + 6 scored checks totaling 100 points, with a 75-point pass threshold. We'll start with this and adjust based on output quality.

C) Let's define it together

We'll review the proposed scoring system and customize thresholds, weights, and compliance rules together.

Decision 4

Cloudflare Account

How should we handle Cloudflare infrastructure (Workers, D1, R2)?

A) I'll provide existing Cloudflare account access

Share API token or login credentials for Wrangler CLI deployment. The dashboard will live on a subdomain you choose (e.g., content.lilyfields.com).

B) Create a new account, I'll provide billing Recommended

John creates a new Cloudflare account specifically for this project. Blake provides a payment card. Clean separation of concerns.

C) Deploy on John's account initially

Start development on John's Cloudflare account, transfer to HHE's account later. Fastest to start, but requires migration.

Decision 5

Gemini API Key

How should we provision the Google Gemini API key?

A) I'll provide Google Cloud / AI Studio credentials

Share an existing Google AI Studio API key with Gemini Flash and Pro access.

B) John provisions, Blake reimburses Recommended

John creates an API key on his Google Cloud account. Expected cost: ~$2-5/day during active generation. Flash is very affordable; Pro used only for QA scoring.

Decision 6

WordPress Details (Phase 2)

Can you share WordPress site details for the CMS adapter?

A) Yes, here are the details

Share: WordPress site URL, REST API credentials (application password), target post type/category structure, any custom fields.

B) Not ready yet, will share later Recommended

This isn't blocking Phase 1. Share when ready — we need it before starting Phase 2 (WordPress integration).

C) We might not use WordPress

If a different CMS is preferred, let us know. The adapter pattern makes CMS swappable.