Content Engine Lift: 32 Posts in 60 Days with Briefs, Entities & Link Pass

32 posts in 60 days — without burning the team. This case playbook shows how a 6-person marketing team shipped a clustered content engine with AI briefs, entity checklists, and a ruthless internal-link pass. Two tracks: Manager Mode for cadence and KPIs, Builder Mode for schemas, prompts, and workflows.

Manager Mode — cadence, staffing, KPIs, budget

Use this section to set a realistic 60-day plan and prove impact fast.

Baseline (Week 0)

• Inventory: 41 existing posts, no clusters, weak internal links.
• Traffic mix: 72% branded, 28% non-brand.
• Cadence: 1 post/week; editors overloaded with briefs.

60-day timeline

1. Week 1: select 3 clusters (e.g., AI video, RAG, CRM copilots); freeze seed list; define brief rubric.
2. Week 2: generate AI briefs (JSON) with entities/H2s/FAQs/sources; editors approve.
3. Weeks 3–8: publish 3–5 posts/week; run link pass same day; weekly KPI review & pruning.

Roles

• SEO Lead: owns clusters, approves briefs, runs SERP diffs.
• Writers (2–3): draft from briefs; add screenshots and examples.
• Ops: imports briefs to CMS, runs link pass, updates dashboards.

Track these four KPIs weekly and decide on cluster expansions or cuts every 14 days.

Budget tiers

• Starter: entity-aware brief tool + free link mapper; manual CMS import.
• Pro: brief tool + SERP diff + link graph with CSV/JSON exports.
• Enterprise: APIs for briefs and link updates, role permissions, audit logs.

Builder Mode — clusters → briefs → outlines → publish → link pass

This appendix gives you the exact artifacts to replicate the 60-day content engine.

Seed & cluster SOP

• Collect 30–40 seeds per cluster; include nav/info/transactional queries.
• Deduplicate; split intents (guide vs comparison vs checklist).
• Freeze each cluster for 30 days to avoid thrash; log SERP snapshot date.

Brief schema (JSON)

Use a strict schema so exports import cleanly into your CMS and writer templates.

{
  "cluster_id":"clu_ai_video",
  "target_keyword":"ai video editing software",
  "search_intent":"commercial",
  "page_type":"comparison|how_to|guide|checklist",
  "entities_required":["non-linear editing","b-roll","speech-to-text","gpu encoding"],
  "h2s":[
    "What matters in AI video editors",
    "Top options compared",
    "Pricing & limits",
    "FAQ"
  ],
  "questions":["Is on-device faster?","Do free plans watermark exports?"],
  "sources":[
    {"title":"Vendor Docs","url":"https://..."},
    {"title":"Independent Review","url":"https://..."}
  ],
  "internal_link_targets":[
    {"slug":"/blog/ai-video-editors/","anchor":"AI video editors"},
    {"slug":"/blog/transcription-translation/","anchor":"transcription & translation"}
  ],
  "meta":{"slug":"best-ai-video-editors","priority":1}
}

Brief generation prompt (deterministic)

System:
Return ONLY JSON exactly matching the Brief schema. No extra text.
User:
Goal: Create a content brief for {{target_keyword}}.
Constraints:
- Include entities_required (5–10 items).
- Provide H2s and 4–8 questions from SERP intent.
- Add 2+ credible sources with titles and URLs.
- Propose 2–3 internal_link_targets (slug + anchor).
Schema: {{BRIEF_SCHEMA_JSON}}
Return ONLY valid JSON.

Outline & drafting SOP (writer-friendly)

1. Load brief → confirm H2s cover intent; add missing entities.
2. Write intro, then each H2 with 2–4 short paragraphs and a mini-checklist.
3. Add 2–3 source callouts (stats, quotes) with links.
4. Insert internal links from targets; add 2 cross-links to older posts.
5. Final pass: claims safety (no medical/financial promises), tone, and examples.

Link pass SOP (same day as publish)

• Add 5–8 links from existing pages → new page (anchors from brief).
• Add 3–7 links from new page → hub/sibling pages.
• Verify no orphan pages; update sitemap if manual.

Quality guardrails

• Blocked claims: medical/financial promises require sources and editor approval.
• Duplication check: reject outlines overlapping existing slugs by ≥60% headings.
• Entity pass: fail drafts missing required entities for the cluster.

Publishing automation (outline)

1. Briefs → CMS: import JSON to draft with H2s and internal link placeholders.
2. Images: generate or select; add alt text with entities.
3. Publish: schedule 3–5/week; run link pass job after publish webhook.
4. Metrics: log page slug, publish date, links added, and clicks at 28/56 days.

FAQ — 60-day content engine

Do we generate full articles with AI?
No — AI makes briefs and checklists; humans draft and fact-check.

How big should clusters be?
Start ~12 seeds each; prune losers at Day 28; expand winners with adjacent intents.

When do links move the needle?
Immediately for crawlability and in weeks for authority distribution.

How do we avoid sameness?
Require 2 “evidence” blocks per post (screenshots, mini-tests, quotes) and a uniqueness check vs top 5 SERP.

Further reading

• AI SEO Tools — clusters, entities, and internal linking.
• Content Brief Generators — H2s, questions, sources, fact prompts.
• Evaluations & Guardrails — tests & filters to keep claims safe.

Final thoughts

Clusters focus your work, briefs raise quality, and a disciplined link pass compounds results. Ship 3–5 posts per week, measure entity coverage and links per page, and review winners at Day 28/56. That’s how a small team hits 32 posts in 60 days — and keeps them ranking.