# Channel Playbooks

Use this file only when the marketing task needs channel-specific routing.

## SEO And Search Visibility

Inputs:

- page or site scope
- current goal
- known queries or audience questions
- available evidence: GSC, analytics, crawl output, manual SERP notes, or
  public search observations

Checklist:

- Separate technical, content, intent, internal-linking, and authority issues.
- Classify actions as refresh, expand, merge, kill, double-down, no-op, or
  manual review.
- Flag thin content, duplicate intent, unsupported claims, stale examples,
  missing schema, broken metadata, and weak next step.
- Do not invent search volume, CTR, position, impressions, or AI-citation loss.

## Paid Ads And Conversion

Inputs:

- offer
- audience
- promise
- proof
- objections
- landing page
- budget gate

Checklist:

- Build 5-12 angles before writing polished ads.
- Each angle needs a buyer anxiety, promise, proof, creative concept, CTA, and
  landing-page fit.
- Separate copy readiness from spend readiness.
- Require explicit approval before account access, launch, budget changes, or
  conversion tracking edits.

## Email, Newsletter, And Lifecycle

Inputs:

- list/source consent status
- segment or reader
- message goal
- proof
- send boundary

Checklist:

- Draft sequence purpose before subject lines.
- Separate welcome, activation, nurture, retention, winback, launch, and
  editorial newsletter jobs.
- Mark manual-send, scheduler, and sender-reputation boundaries.
- Do not generate mass outreach as if consent, deliverability, or compliance
  were solved.

## Launch And Release

Inputs:

- product or feature
- audience
- proof asset
- channels
- launch date or window
- support/reply plan

Checklist:

- Sequence teaser, announcement, proof, follow-up, and after-action review.
- Keep launch claims tied to shipped evidence.
- Prepare replies for technical questions, buyer value, thanks, and objections.
- Measure what changed after launch, not just what was posted.

## Community, PR, Partnerships, And Directories

Inputs:

- target communities or outlets
- norms
- value offered
- proof
- relationship status

Checklist:

- Start with fit and contribution, not extraction.
- Name the community norm or editorial constraint.
- Treat directory submission as a manual checklist unless a runtime lane is
  approved.
- Do not mass-post, astroturf, scrape member lists, or automate outreach.

## Analytics And Experiments

Inputs:

- decision to inform
- metric
- denominator
- data source
- expected review date

Checklist:

- Define the decision before the dashboard.
- Separate leading indicators from lagging outcomes.
- Record sample size, denominator, time window, and caveats.
- For experiments, write hypothesis, variant, guardrail metric, stop rule, and
  interpretation plan before changing production.
