Content Distribution Engine: 3-Phase Repurposing System
One piece of flagship content becomes 30+ platform assets in three phases. The content is written once. Distribution is systematic, not improvised.
Phase 1: Source Extraction
Extract the core assets from the flagship piece before repurposing begins.
From any article, video transcript, or podcast episode, extract:
SOURCE EXTRACTION REPORT:
- Core argument (1 sentence): [the main point]
- 5 key stats or data points: [list with source]
- 3 quotable moments (1-2 sentences each): [exact quotes]
- 5 key insights or takeaways: [bulleted list]
- Primary keyword: [exact phrase]
- Secondary keywords (3-5): [list]
- Target audience: [definition]
- CTA goal: [what action should follow]
Do not skip this step. Repurposing from memory produces thin content.
Phase 2: 10 Platform-Specific Formats
| Format | Platform | Length | Source Asset Used | |--------|----------|--------|-------------------| | 1. Full article | Blog | Full length | Full source | | 2. GMB post | Google Business Profile | 150-300 words | Core argument + CTA | | 3. Video script | YouTube (long-form) | 5-15 min | Full source, scripted | | 4. Short-form script | Shorts / TikTok | 30-60 seconds | 1 key insight | | 5. Podcast episode notes | Podcast platform | 200-400 words | Key insights + timestamps | | 6. Press release | PR wire | 400-600 words | Core argument + news angle | | 7. Social post set | Facebook, LinkedIn, X | Platform-native | 3 key insights (1 per platform) | | 8. Image caption | Instagram | 150-300 words | 1 quotable moment | | 9. Q&A post | Facebook Groups | 100-200 words | 1 stat + discussion question | | 10. FAQ schema | Schema.org JSON-LD | 5-7 Q&A pairs | Key insights as FAQ |
Format-Specific Rules
GMB Post: 150-300 words. Primary keyword in first sentence. Phone number in last paragraph. No hashtags.
Video Script: Hook (30 seconds) → Content (per-section structure from article) → CTA (30 seconds). No reading the article verbatim — script the rhythm differently.
Short-Form Script: Single idea from the source. Hook in 2 seconds. Demo or delivery in 20-45 seconds. CTA last 5 seconds.
Press Release: Inverted pyramid. News angle (why now?). Quote from business owner or expert. Contact info. Boilerplate. AP style.
Social Posts: Platform-native format (see social-post-system.mdx). Never paste the same copy to all three platforms.
FAQ Schema: 5-7 questions derived from PAA data for the primary keyword. Answer each in 40-80 words. Export as JSON-LD.
Phase 3: Geo-Unique Variants
For multi-location clients, generate location-specific variants of the top-performing formats:
Formats that get geo-variants:
- Blog article (1 per primary city)
- GMB post (1 per GMB listing)
- Short-form video script (1 per market if content is local)
- FAQ schema (city-name variants in questions)
Minimum variation per geo-variant:
- H1 and title tag: 100% different (city-modified)
- Intro paragraph: 100% rewrite
- 1 local stat or reference unique to that city
- CTA references the specific location
Jaccard similarity target between variants: 0.75-0.85. (See content-variation-engine-jaccard.mdx)
Distribution Calendar
| Day | Platform | Format | Content | |-----|----------|--------|---------| | 1 | Blog | Full article | Flagship piece | | 1 | Email | Newsletter | Summary + link | | 2 | GMB | Post | Core argument version | | 3 | Facebook | Native post | Insight 1 | | 4 | LinkedIn | Post | Insight 2 | | 5 | X/Twitter | Thread | Insight 3 as thread | | 5 | Instagram | Caption | Quotable moment | | 7 | YouTube | Video | Full script | | 10 | Podcast | Episode notes | Key insights | | 14 | PR wire | Press release | News-angle version |
What NOT to Repurpose
Not every piece of content has distribution value:
- Skip distribution for: thin content under 800 words, content that ranked below position 20 for 90+ days, topic-specific content with no evergreen angle
- Repurpose priority: content already ranking positions 4-15 (boosts signal), content with highest time-on-page, content tied to a core service or keyword cluster
#content-sop #distribution #repurposing #content-ops