# SEO content plan - Raegan

**Keyword data (reuse):** [`seo-keywords.json`](./seo-keywords.json) (machine-readable) · [`seo-keywords.md`](./seo-keywords.md) (human-readable tables)

Data source: DataForSEO (US, English, Google). Snapshot: late May 2026.

## Strategy summary

| Priority | Role | Terms |
|----------|------|--------|
| **P0 - Homepage anchors** | Head terms, low KD, high intent | `ai personal assistant` (5,400/mo, KD 4), `ai executive assistant` (880/mo, KD 3) |
| **P1 - Category ownership** | Emerging, own early | `ai chief of staff` (260/mo, +556% YoY) |
| **P1 - Feature pillar page** | Dedicated URL | `ai email assistant` (2,400/mo, KD 21) |
| **P2 - Differentiator tails** | Homepage sections + FAQ | `self hosted ai assistant` (+200%), `ai daily briefing` (+250%) |
| **P3 - Secondary** | Mention in copy, not primary | `ai email management`, `ai assistant for email` |
| **Avoid as primary** | Wrong intent or too hard | `ai note taker` (27k, KD 43), `ai research assistant` (KD 65, academic) |

High CPC ($12-62) signals strong commercial intent - see `seo-keywords.json` → `insights`.

---

## Site map (current + planned)

### Live now

| URL | Target terms | Status |
|-----|--------------|--------|
| `/` | ai personal assistant, ai executive assistant, ai chief of staff, self hosted ai assistant, ai daily briefing | Optimized |
| `/ai-email-assistant/` | ai email assistant, ai email management | Live |
| `/ai-chief-of-staff/` | ai chief of staff | Live |
| `/ai-personal-assistant/` | ai personal assistant | Live |
| `/ai-executive-assistant/` | ai executive assistant | Live |
| `/self-hosted-ai-assistant/` | self hosted ai assistant | Live |
| `/pricing.md` | pricing, commercial intent | Machine-readable for agents |
| `/llms.txt` | AEO / AI citation | Synced |
| `/privacy.html`, `/terms.html` | trust | Indexed, basic OG |

### Planned pages (future)

#### Comparison pages (post-validation)

- Raegan vs Copilot, vs ChatGPT, vs Gemini (high AI citation share)
- Programmatic: `ai chief of staff for [vertical]` if segment data from waitlist `business_type` supports it

---

## Homepage on-page checklist (implemented)

- [x] Title + meta description: personal assistant, executive assistant, chief of staff, email assistant, self-hosted
- [x] Hero definition block (extractable 40-60 words for AI snippets)
- [x] Email section: "AI email assistant" in eyebrow + body
- [x] Morning briefing: "AI daily briefing" in eyebrow + body
- [x] Privacy section: "self-hosted AI assistant" in copy
- [x] FAQ: "Is Raegan an AI email assistant?", "What is an AI chief of staff?"
- [x] JSON-LD FAQPage synced with visible FAQ
- [x] Footer links to `pricing.md`, `llms.txt`; freshness date
- [x] `llms.txt` keyword map + live SEO URLs
- [x] Five SEO landing pages live (`/ai-email-assistant/`, etc.)

---

## Content rules (all pages)

- Speak to **business owners and founders** (owner-operators), not horizontal "AI for everyone"
- No em-dashes in visible copy (hyphens only)
- No fake testimonials, counts, or review schema pre-launch
- Prices framed as early supporter / may change at launch
- Claims true to Hermes capabilities
- One primary CTA: **Get early access**

---

## Measurement

- Google Search Console: submit sitemap, track impressions for anchor terms
- Manual AI visibility checks: ChatGPT, Perplexity, Google AI Overviews for top 10 queries quarterly
- Waitlist conversion by landing page (once subpages ship)

---

## Ops

| File | Purpose |
|------|---------|
| `seo-keywords.json` | Canonical DataForSEO keyword dataset (reuse in agents, scripts, refreshes) |
| `seo-keywords.md` | Human-readable tables; points to JSON |
| `seo-content-plan.md` | Page roadmap and on-page checklist (this file) |
| `llms.txt` | AI answer engines - keep in sync when pages ship |
| `sitemap.xml` | Add new URLs when each page goes live |
| `index.html` JSON-LD | Update FAQ when on-page FAQ changes |
| `pricing.md` | Keep aligned with on-page plans |

Last updated: June 2026