# Content Ops Knowledge Base

SEO briefs, article frameworks, repurposing systems, video-to-blog workflows, content calendars, metadata checklists, and content-to-agent conversion.

## Purpose

This knowledge base helps agents and operators turn ideas, transcripts, notes, offers, workflows, and product concepts into structured content assets.

Use this folder to support:

- SEO article briefs
- Blog post outlines
- YouTube script repurposing
- Prompt pack creation
- Landing page copy
- Content calendar workflows
- Content-to-agent conversion
- FAQ generation
- Internal link plans
- Metadata and excerpt writing
- AI search optimization resources

## Primary Users

- Content operators
- AI SEO builders
- Blog writers
- YouTube operators
- Newsletter operators
- Custom GPT builders
- Static site builders
- Affiliate content teams
- Marketing agencies
- Business tool publishers

## Core Content Principles

1. Start with the searcher, buyer, or operator problem.
2. Write for clarity before cleverness.
3. Use structured outlines before drafting.
4. Keep claims verifiable.
5. Use internal links intentionally.
6. Add CTAs that match user intent.
7. Turn high-performing content into agents, skills, examples, or templates.
8. Preserve public-safe language for funding, credit, finance, legal, and platform topics.

## Content Asset Types

### SEO Article Brief

A structured plan for a blog post or long-form article.

Required sections:

- Working title
- Primary keyword
- Secondary keywords
- Search intent
- Audience
- Problem solved
- Recommended H2s/H3s
- Internal links
- External citation needs
- CTA
- Meta description
- Article excerpt
- Do-not-claim list

### Blog Article

A full article designed for publication.

Recommended sections:

- Introduction
- Problem framing
- Definitions
- Use cases
- Step-by-step guidance
- Examples
- Common mistakes
- FAQs
- CTA
- Disclaimer where needed

### YouTube Script

A script for short educational or product-led video.

Recommended structure:

- Hook
- Problem
- Explanation
- Example
- Tool or workflow mention
- CTA
- Disclaimer where needed

### Prompt Pack

A reusable sequence of prompts for a job.

Recommended structure:

- Use case
- Inputs required
- Prompt sequence
- Expected outputs
- Review checklist
- Example output
- Guardrails

### Landing Page

A conversion-focused page for a tool, GPT, partner asset, or lead magnet.

Recommended structure:

- Hero
- Pain
- Promise
- How it works
- Use cases
- Example output
- CTA
- Trust/disclaimer section
- FAQ

## SEO Brief Format

```md
# [Working Title]

## Primary Keyword

[Keyword]

## Secondary Keywords

- Keyword 1
- Keyword 2

## Search Intent

[Informational / Commercial / Navigational / Transactional]

## Audience

[Who this is for]

## Problem Solved

[What pain the article solves]

## Recommended Structure

### H2: [Section]
- H3: [Subsection]
- H3: [Subsection]

## Internal Links

- [Page title](URL)

## External Citation Needs

- Current platform docs
- Current pricing or policy source
- Primary source where possible

## CTA

[CTA label + destination]

## Meta Description

[150–160 character description]

## Article Excerpt

[Short summary]

## Do-Not-Claim List

- Claim 1
- Claim 2
```

## Repurposing Matrix

| Source Asset | Repurpose Into | Notes |
|---|---|---|
| YouTube video | Blog post | Extract sections, examples, FAQs, CTA |
| Blog post | Prompt pack | Convert process into reusable prompt sequence |
| Prompt pack | Skill file | Define inputs, outputs, workflow, guardrails |
| Agent spec | Landing page | Translate buyer, pain, outcome, CTA |
| Knowledge base | FAQ page | Turn rules into answers |
| Case notes | Synthetic example | Remove private data and claims |
| Static page | Social posts | Extract hooks and bullets |
| SEO brief | Article draft | Preserve structure and citations |

## Metadata Checklist

Every publishable page should define:

- Page title
- Meta description
- H1
- Primary keyword or topic
- Short excerpt
- Category
- Tags
- CTA
- Canonical URL if applicable
- Open Graph image if applicable
- Last reviewed date

## Internal Linking Rules

Use internal links to guide users toward the next useful action.

Recommended link targets:

- Agent catalog
- Skill catalog
- Knowledge-base pages
- Partner get-started page
- Funding readiness resources
- Prompt systems
- Examples
- Portfolio pages
- Legal/trust pages when claims need context

## CTA Rules

CTA should match user intent.

Examples:

- “Browse related agents”
- “Open the skill builder”
- “Use the prompt generator”
- “Check funding readiness”
- “Compare partner resources”
- “View platform pack”
- “Download the template”
- “Start with the resource page”

Avoid:

- Vague “Learn more” as the only CTA
- CTAs that imply guaranteed outcomes
- CTAs that send users to a form before education when trust is low
- Multiple competing primary CTAs

## Public-Safe Content Rules

For funding, finance, business-credit, legal, tax, platform, or automation content:

- Use educational framing.
- Avoid guarantees.
- Cite current official sources where needed.
- Disclose affiliate relationships.
- Use synthetic examples.
- Add human review language when appropriate.
- Separate internal notes from public copy.

## Standard Content Agent Output

```md
## Content Summary

- Topic:
- Audience:
- Search intent:
- Primary keyword:
- CTA:
- Risk level:

## Recommended Asset Type

[SEO brief / article / prompt pack / landing page / script / FAQ]

## Outline

[Structured outline]

## Missing Inputs

- Missing item 1
- Missing item 2

## Draft Copy or Brief

[Generated content]

## Internal Links

- Link 1
- Link 2

## Guardrails

- Guardrail 1
- Guardrail 2
```

## Related Repo Paths

```text
knowledge-base/content-ops/
examples/content-ops/
prompt-library.html
prompt-generator.html
templates.html
schemas/
site-data/
```

## Maintenance Checklist

- [ ] SEO brief format is current.
- [ ] CTA rules are clear.
- [ ] Repurposing workflows are documented.
- [ ] Public-safe language rules are preserved.
- [ ] Examples are synthetic.
- [ ] Citation needs are flagged for current facts.