Content Writing Playbook
Platform and channel-specific guidance for AI-generated content across LinkedIn, X/Twitter, and SEO blogs. This guide mirrors the runtime prompt assets used by the Content Calendar plugin.
Universal Principles
All content generated by PIE plugins should follow these rules:
- BLUF (Bottom Line Up Front): Lead with the answer, metric, or contrarian claim. No preambles.
- Active voice only. Strip passive constructs.
- Information density: Every sentence introduces new information. If it merely restates the previous sentence, cut it.
- Conversational authority: Write peer-to-peer, not professor-to-student.
- No AI clichés. Avoid words like delve, tapestry, unleash, supercharge, revolutionize, myriad, plethora, and filler phrases like "In the fast-paced world of..." or "Let's dive in."
- Show, don't tell. Replace adjectives with specific metrics: "412% MRR increase in 14 days", not "massive growth".
- Visual pacing: Max 2–3 sentences per block. Use hard line breaks, strategic whitespace, and varied sentence lengths (short, medium, punchline).
LinkedIn
LinkedIn's 2026 algorithm is governed by Depth Scoring. Dwell time accounts for ~40% of algorithmic weight.
Hook-Rehook Architecture
- Line 1 (Hook): 6–8 words. Curiosity gap, contrarian reveal, or credibility statement.
- Line 2 (Rehook): 5–6 words. Validates or flips the hook. Separated by a blank line.
I lost $50,000 ignoring this one B2B sales rule.
Actually, I ignored it for three years.Structure
- Hook — Bold claim or data point
- Story — First-person expertise grounded in the user's industry
- Lesson — Fast, actionable takeaway
Rules
- Optimal length: 150–250 words
- Short sentences (under 55 characters) with intentional line breaks
- Text-only posts outperform text+image for engagement
- Bold for metrics only, italic for internal monologue
- Never use engagement bait: "Comment YES", "Thoughts?", "Link in the first comment"
- Place external links at the very bottom of the post
- Stay within a single niche topic for interest graph authority
- End with a pointed question that drives multi-sentence peer replies
Format Selection
| Format | Best For |
|---|---|
| Text-only | Daily authority building, high comment volume |
| Document carousel (6–9 slides) | Dwell-time multiplication (2–3x) |
| Vertical video (<60s, captioned) | Feed priority |
X/Twitter
X's 2026 algorithm uses Grok's semantic mapping and anti-bot systems. Content must be structurally flawless and formatted for deep dwell time.
Signal Weights
| Signal | Multiplier |
|---|---|
| Likes | 1x |
| Bookmarks | 10–20x |
| Link Clicks | 11x |
| Profile Clicks | 12x |
| Replies | 13.5x |
| Retweets | 20x |
| Author Engagement | 75–150x |
Thread Formatting
- First sentence: Must explicitly name the core topic for Grok SimCluster matching
- Open with a curiosity gap or contrarian claim with extreme specificity
- Short, punchy 1–2 sentence lines separated by hard line breaks
- Structure the opening so the best part sits just below the "Show More" truncation
- Every tweet must be self-contained (standalone value)
Value Frameworks
Choose one per thread:
| Framework | Optimizes For |
|---|---|
| Educational | Bookmarks (step-by-step guides, resource lists) |
| Polarizing | Replies (contrarian stance against industry norms) |
| Entertaining | Reposts (fast-paced storytelling, curated visuals) |
Anti-Bot Rules
- No external links in the main post. Stage links as a reply after initial engagement.
- No engagement bait: "Drop a dot", "Like if you agree", "Follow me for more", "Link in bio"
- Use organic CTA questions: "Which tactic are you testing this week?"
- The first 60 minutes need ~100 interaction points to reach the global "For You" feed
SEO Blog Posts
Google's 2026 algorithm evaluates content on Trust and Intent Completion via E-E-A-T.
Architecture
Above the Fold:
- H1: Exact problem + outcome (no vague or clickbait titles)
- 1–2 sentence direct answer matching search intent
- Credibility node: who wrote this and why they are qualified
- Table of Contents with jump links (mandatory for 800+ words)
Core Blocks (MECE):
- Numbered steps, decision trees, required inputs
- Experience Layer: first-hand notes ("When we tried X, Y broke")
- Edge cases ("If X, do Y instead") to prevent pogo-sticking
- LSI keywords integrated naturally into H2s and H3s
Governance Footer:
- Accurate "Last Updated" badge stating what changed
- AI disclosure statement
Word Count by Intent
| Intent | Words |
|---|---|
| Informational/Definitions | 200–600 |
| How-To/Tutorials | 800–1,800 |
| Pillar Guides | 1,800–4,000+ |
Output Fields
Blog drafts should include:
title— H1 targeting the primary keywordmeta_description— 150–160 character snippetseo_keyword— Primary target keywordbody— Full structured content with H2/H3 headings
Risk Avoidance
- Never programmatically generate hundreds of low-value, tightly targeted pages
- No "parasite SEO" (publishing on high-authority domains to exploit ranking signals)
- If AI assisted in drafting, disclose it in the governance footer
Pre-Flight QA Checklist
Before publishing any draft, verify:
- BLUF Verification — Primary value stated within first 30 words?
- Forbidden Lexicon Sweep — No AI cliché words or phrases?
- Show Don't Tell — Metrics instead of adjectives?
- Visual Pacing — No text block exceeds 3 sentences without a break?
- Hook-Rehook (LinkedIn) — 6–8 word hook + blank line + 5–6 word rehook?
- Grok Match (X) — Core topic explicit in first sentence?
- Link Staging (X) — No external link in main post body?
- E-E-A-T Layer (Blog) — Includes first-hand experience notes?
- Anti-Bait Filter — No banned engagement bait phrases?
- Intent Completion (Blog) — H2s, H3s, and bullets give a complete answer alone?