NEO Campaign Strategy Standard Deliverable Set

Origin: Extracted from knowledge/lessons/seo/neo-workflow.md during knowledge restructure (2026-05-20). The procedure body is preserved verbatim below.

SEO NEO campaign-strategy standard deliverable set

From legacy section: SEO NEO / Workbook

Pattern: Putnam Place's seoneo/campaign-strategy/ had only bucket-1 content (Cloud Poster + Wiki Stack) but the readme and file-index claimed it was "complete." Comparing to fully-built clients (Rock Academy, YA Skin, Tali Kogan), every complete campaign-strategy folder has a standard 6-file set: Implementation Checklist, Setup Guide, GBP Blast keywords (per bucket), RYB settings, NAP/Blurb HTML embed, and Social Media Links. Rule: When asked to complete a client's seoneo/campaign-strategy/, the canonical deliverable set is: (1) <Client>_SEO_Implementation_Checklist.md — CWV/schema/GBP/NAP pre-launch fixes, (2) <Client>_Setup_Guide.md — per-wizard paste-ready config for Cloud Poster, Wiki Stack, GBP Blast, RD 100, RYB, Hades, (3) <Client>_GBP_BLAST_Keywords.txt — keyword blocks per bucket, (4) <Client>_RANK_YOUR_BRAND_Settings.txt — NAP + hours + categories + descriptions + primary/brand keywords, (5) <Client>_NAP_Blurb.html — standard + extended AI-learning embed, (6) <Client>_Social_Media_Links.txt — canonical + recommended socials. The excel-workbook/ counterpart standard is 11 sheets per the file-index spec. Source everything from neo-onboarding-package.md — no new facts. Elevate this to CLAUDE.md or a neo-complete-strategy skill if this pattern repeats. Date: 2026-04-21

---

/neo-content-bucket complete deliverable — 6 SEO NEO fields per bucket

From legacy section: SEO NEO / Workbook

Rule: A complete /neo-content-bucket deliverable has SIX SEO NEO fields, not five: (1) Articles, (2) Short Descriptions [3–5 spintax blocks, 150–300 chars rendered, brand-relevant, semantic-triple-bearing], (3) Author Bio, (4) Blog Details (Name + Subdomain), (5) Comments (5: 1 short / 3 medium / 1 long), (6) NAP/Blurb (per-location). Each bucket markdown is SELF-CONTAINED — every field inlined, plus a "How to Paste Into SEO NEO" table mapping each section to its SEO NEO destination. Cross-bucket assets (Bio/Blog/Comments) can be the same shared spintax pool, but they still appear inline in every bucket file — never just a "see xlsx Sheet X" footnote. Per-bucket-tailored: Short Descriptions, NAP/Blurb (location-specific). The skill spec at .claude/commands/neo-content-bucket.md needs an update adding Short Descriptions as a required output between "Articles" and "Author Bio". Date: 2026-05-05

---

/neo-project-setup scope: scaffold only (workbook is separate)

From legacy section: SEO NEO / Workbook

Rule: /neo-project-setup outputs folder + 6 markdown root files only. The Excel_Workbook/ subfolder is "empty, ready for workbook file" per the skill spec. The workbook itself must be built separately. If a SEO NEO project has docs claiming the workbook exists, always verify the .xlsx file is actually present before trusting any "complete" status. Date: 2026-04-20