claude-plugin-wordpress-manager 2.9.1 → 2.12.0

package/servers/wp-rest-bridge/build/wordpress.js

@@ -39,6 +39,8 @@ const bufSiteClients = new Map();
 const sgSiteClients = new Map();
 const plSiteClients = new Map();
 const slackBotClients = new Map();
+const liSiteClients = new Map();
+const twSiteClients = new Map();
 let activeSiteId = '';
 const parsedSiteConfigs = new Map();
 const MAX_CONCURRENT_PER_SITE = 5;
@@ -111,6 +113,14 @@ export async function initWordPress() {
             await initSlackBotClient(site.id, site.slack_bot_token);
             logToStderr(`Initialized Slack Bot for site: ${site.id}`);
         }
+        if (site.linkedin_access_token) {
+            await initLinkedInClient(site.id, site.linkedin_access_token);
+            logToStderr(`Initialized LinkedIn for site: ${site.id}`);
+        }
+        if (site.twitter_bearer_token) {
+            await initTwitterClient(site.id, site.twitter_bearer_token);
+            logToStderr(`Initialized Twitter for site: ${site.id}`);
+        }
     }
     activeSiteId = defaultSite || sites[0].id;
     logToStderr(`Active site: ${activeSiteId}`);
@@ -234,6 +244,30 @@ async function initSlackBotClient(id, botToken) {
     });
     slackBotClients.set(id, client);
 }
+async function initLinkedInClient(id, accessToken) {
+    const client = axios.create({
+        baseURL: 'https://api.linkedin.com/rest/',
+        headers: {
+            'Content-Type': 'application/json',
+            'Authorization': `Bearer ${accessToken}`,
+            'LinkedIn-Version': '202401',
+            'X-Restli-Protocol-Version': '2.0.0',
+        },
+        timeout: DEFAULT_TIMEOUT_MS,
+    });
+    liSiteClients.set(id, client);
+}
+async function initTwitterClient(id, bearerToken) {
+    const client = axios.create({
+        baseURL: 'https://api.twitter.com/2/',
+        headers: {
+            'Content-Type': 'application/json',
+            'Authorization': `Bearer ${bearerToken}`,
+        },
+        timeout: DEFAULT_TIMEOUT_MS,
+    });
+    twSiteClients.set(id, client);
+}
 // ── Site Management ──────────────────────────────────────────────────
 /**
  * Get the active site's client, or a specific site's client
@@ -647,6 +681,66 @@ export async function makeSlackBotRequest(method, endpoint, data, siteId) {
         limiter.release();
     }
 }
+// ── LinkedIn Interface ──────────────────────────────────────────
+export function hasLinkedIn(siteId) {
+    const id = siteId || activeSiteId;
+    return liSiteClients.has(id);
+}
+export async function makeLinkedInRequest(method, endpoint, data, siteId) {
+    const id = siteId || activeSiteId;
+    const client = liSiteClients.get(id);
+    if (!client) {
+        throw new Error(`LinkedIn not configured for site "${id}". Add linkedin_access_token to WP_SITES_CONFIG.`);
+    }
+    const limiter = getLimiter(id);
+    await limiter.acquire();
+    try {
+        const response = await client.request({ method, url: endpoint, data: method !== 'GET' ? data : undefined, params: method === 'GET' ? data : undefined });
+        return response.data;
+    }
+    finally {
+        limiter.release();
+    }
+}
+export function getLinkedInPersonUrn(siteId) {
+    const id = siteId || activeSiteId;
+    const sites = JSON.parse(process.env.WP_SITES_CONFIG || '[]');
+    const site = sites.find((s) => s.id === id);
+    if (!site?.linkedin_person_urn) {
+        throw new Error(`LinkedIn person URN not configured for site "${id}". Add linkedin_person_urn to WP_SITES_CONFIG.`);
+    }
+    return site.linkedin_person_urn;
+}
+// ── Twitter/X Interface ─────────────────────────────────────────
+export function hasTwitter(siteId) {
+    const id = siteId || activeSiteId;
+    return twSiteClients.has(id);
+}
+export async function makeTwitterRequest(method, endpoint, data, siteId) {
+    const id = siteId || activeSiteId;
+    const client = twSiteClients.get(id);
+    if (!client) {
+        throw new Error(`Twitter not configured for site "${id}". Add twitter_bearer_token to WP_SITES_CONFIG.`);
+    }
+    const limiter = getLimiter(id);
+    await limiter.acquire();
+    try {
+        const response = await client.request({ method, url: endpoint, data: method !== 'GET' ? data : undefined, params: method === 'GET' ? data : undefined });
+        return response.data;
+    }
+    finally {
+        limiter.release();
+    }
+}
+export function getTwitterUserId(siteId) {
+    const id = siteId || activeSiteId;
+    const sites = JSON.parse(process.env.WP_SITES_CONFIG || '[]');
+    const site = sites.find((s) => s.id === id);
+    if (!site?.twitter_user_id) {
+        throw new Error(`Twitter user ID not configured for site "${id}". Add twitter_user_id to WP_SITES_CONFIG.`);
+    }
+    return site.twitter_user_id;
+}
 // ── Plugin Repository (External API) ────────────────────────────────
 /**
  * Search the WordPress.org Plugin Repository

package/skills/wordpress-router/references/decision-tree.md

@@ -1,4 +1,4 @@
-# Router decision tree (v16 — development + local environment + operations + multisite + CI/CD + monitoring + webhooks + content repurposing + programmatic SEO + content attribution + multi-language network + social/email distribution + search console + content optimization + analytics + alerting + workflows)
+# Router decision tree (v18 — development + local environment + operations + multisite + CI/CD + monitoring + webhooks + content repurposing + programmatic SEO + content attribution + multi-language network + social/email distribution + search console + content optimization + analytics + alerting + workflows + LinkedIn + Twitter/X + content generation + structured data)
 
 This routing guide covers WordPress **development**, **local environment**, and **operations** workflows.
 
@@ -14,7 +14,7 @@ Keywords that indicate **local environment**:
 local site, Studio, LocalWP, Local by Flywheel, wp-env, local WordPress, start site, stop site, create local site, local development, symlink plugin, local database, switch PHP version, localhost, local preview, detect environment, WASM, SQLite local
 
 Keywords that indicate **operations**:
-deploy, push to production, audit, security check, backup, restore, migrate, move site, create post, manage content, site status, check plugins, performance check, SEO audit, WooCommerce, prodotto, ordine, coupon, negozio, catalogo, inventario, vendite, carrello, multisite, network, sub-site, sub-sito, domain mapping, super admin, network activate, monitor, uptime, health report, trend, scansione periodica, alerting, performance baseline, fleet, all sites, network health, cross-site, webhook, outbound notification, event propagation, Zapier, content sync, repurpose content, social posts from blog, content atomization, newsletter from posts, content distribution, programmatic SEO, template pages, city pages, location pages, bulk page generation, scalable landing pages, content ROI, attribution, which content drives sales, conversion tracking, UTM tracking, revenue per post, multilingual, multi-language, hreflang, international SEO, translate site, language sites, localize content, social publish, schedule post, Buffer, email campaign, Mailchimp, SendGrid, transactional email, content distribution, newsletter send, Google Search Console, GSC, keyword tracking, keyword rankings, search analytics, indexing status, URL inspection, sitemap submit, search performance, SERP data, optimize content, headline scoring, readability analysis, SEO score, content scoring, meta optimization, content freshness, content triage, bulk optimize, Flesch-Kincaid, keyword density, Google Analytics, GA4, traffic analytics, pageviews, sessions, user analytics, Plausible, privacy analytics, Core Web Vitals, CWV, LCP, INP, CLS, PageSpeed, page speed, site speed, performance score, Slack alert, email alert, notification channel, alert threshold, severity routing, escalation, incident notification, uptime alert, error alert, performance alert, scheduled report, health digest, alert cooldown, alert dedup, workflow trigger, automation, scheduled event, content lifecycle, cron trigger, hook trigger, workflow rule, automate, trigger management
+deploy, push to production, audit, security check, backup, restore, migrate, move site, create post, manage content, site status, check plugins, performance check, SEO audit, WooCommerce, prodotto, ordine, coupon, negozio, catalogo, inventario, vendite, carrello, multisite, network, sub-site, sub-sito, domain mapping, super admin, network activate, monitor, uptime, health report, trend, scansione periodica, alerting, performance baseline, fleet, all sites, network health, cross-site, webhook, outbound notification, event propagation, Zapier, content sync, repurpose content, social posts from blog, content atomization, newsletter from posts, content distribution, programmatic SEO, template pages, city pages, location pages, bulk page generation, scalable landing pages, content ROI, attribution, which content drives sales, conversion tracking, UTM tracking, revenue per post, multilingual, multi-language, hreflang, international SEO, translate site, language sites, localize content, social publish, schedule post, Buffer, email campaign, Mailchimp, SendGrid, transactional email, content distribution, newsletter send, Google Search Console, GSC, keyword tracking, keyword rankings, search analytics, indexing status, URL inspection, sitemap submit, search performance, SERP data, optimize content, headline scoring, readability analysis, SEO score, content scoring, meta optimization, content freshness, content triage, bulk optimize, Flesch-Kincaid, keyword density, Google Analytics, GA4, traffic analytics, pageviews, sessions, user analytics, Plausible, privacy analytics, Core Web Vitals, CWV, LCP, INP, CLS, PageSpeed, page speed, site speed, performance score, Slack alert, email alert, notification channel, alert threshold, severity routing, escalation, incident notification, uptime alert, error alert, performance alert, scheduled report, health digest, alert cooldown, alert dedup, workflow trigger, automation, scheduled event, content lifecycle, cron trigger, hook trigger, workflow rule, automate, trigger management, LinkedIn, LinkedIn post, LinkedIn article, B2B social, pubblica LinkedIn, Twitter, X, tweet, thread, pubblica tweet, Twitter analytics, genera contenuto, scrivi post, AI content, content brief, crea articolo, draft post, genera bozza, structured data, Schema.org, JSON-LD, rich snippet, schema markup, dati strutturati
 
 Keywords that indicate **development**:
 create block, block.json, theme.json, register_rest_route, plugin development, hooks, PHPStan, build, test, scaffold, i18n, translation, accessibility, a11y, headless, decoupled, WPGraphQL, CI, CD, pipeline, GitHub Actions, GitLab CI, deploy automatico, workflow, quality gate
@@ -116,6 +116,14 @@ Priority: `gutenberg` > `wp-core` > `wp-site` > `wp-block-theme` > `wp-block-plu
   → `wp-alerting` skill + `wp-monitoring-agent` agent
 - **Workflow trigger / automation / scheduled event / content lifecycle / cron trigger / hook trigger / workflow rule / automate / trigger management**
   → `wp-content-workflows` skill + `wp-site-manager` agent
+- **LinkedIn / LinkedIn post / LinkedIn article / B2B social / pubblica LinkedIn**
+  → `wp-linkedin` skill + `wp-distribution-manager` agent
+- **Twitter / X / tweet / thread / pubblica tweet / Twitter analytics**
+  → `wp-twitter` skill + `wp-distribution-manager` agent
+- **genera contenuto / scrivi post / AI content / content brief / crea articolo / draft post / genera bozza**
+  → `wp-content-generation` skill + `wp-content-strategist` agent
+- **structured data / Schema.org / JSON-LD / rich snippet / schema markup / dati strutturati**
+  → `wp-structured-data` skill + `wp-content-strategist` agent
 
 ## Step 2c: route by local environment intent (keywords)
 

package/skills/wp-content-generation/SKILL.md

@@ -0,0 +1,128 @@
+---
+name: wp-content-generation
+description: This skill should be used when the user asks to "generate content",
+  "write a blog post", "create an article", "AI content", "content brief", "draft
+  a post", "genera contenuto", "scrivi post", "crea articolo", "genera bozza",
+  "content pipeline", "create content from brief", or mentions AI-assisted content
+  creation for WordPress.
+version: 1.0.0
+---
+
+# WordPress Content Generation Skill
+
+## Overview
+
+AI-driven content generation pipeline for WordPress. This skill guides Claude through a structured 7-step process: from content brief to published, SEO-optimized post with structured data. It uses existing MCP tools — no new tools are introduced.
+
+## When to Use
+
+- User wants to create new blog posts or articles with AI assistance
+- User has a content brief or topic and wants a full draft
+- User asks for SEO-optimized content creation
+- User wants to generate content with structured data included
+- User mentions content pipeline, content brief, or AI writing
+
+## Content Generation vs Content Repurposing
+
+| Need | Skill |
+|------|-------|
+| Create new original content from scratch | `wp-content-generation` (this skill) |
+| Transform existing content for new channels | `wp-content-repurposing` |
+| Edit/update existing posts | `wp-content` |
+| Bulk page generation from templates | `wp-programmatic-seo` |
+
+## Decision Tree
+
+1. **What does the user need?**
+   - "write a post" / "create article" / "generate content" → Full Pipeline (Section 1)
+   - "content brief" / "what to write about" → Brief Creation (Section 2)
+   - "outline" / "structure" / "plan the article" → Outline Patterns (Section 3)
+   - "optimize" / "SEO" / "improve draft" → Integrate with `wp-content-optimization`
+
+2. **Run detection first:**
+   ```bash
+   node skills/wp-content-generation/scripts/content_gen_inspect.mjs [--cwd=/path/to/project]
+   ```
+   This checks for REST API access, GSC availability, and existing content volume.
+
+## The 7-Step Pipeline
+
+### Step 1: Brief
+Define the content brief with target audience, goal, and constraints.
+See `references/brief-templates.md`
+
+**Input from user:**
+- Topic or keyword
+- Target audience
+- Content goal (inform, convert, engage)
+- Word count target (optional)
+
+### Step 2: Keyword Research
+Use GSC data (if available) to identify keyword opportunities.
+
+**Tools used:**
+- `gsc_query_analytics` — find related queries with impressions and CTR
+- `gsc_list_pages` — check existing content for the keyword to avoid cannibalization
+
+**Fallback:** If GSC not configured, use the topic as primary keyword and suggest 3-5 related terms based on semantic analysis.
+
+### Step 3: Outline
+Create a structured outline with H2/H3 hierarchy.
+See `references/outline-patterns.md`
+
+**Output:** Markdown outline with headings, key points per section, target word count per section.
+
+### Step 4: Draft
+Generate the full draft following the outline.
+
+**Writing guidelines:**
+- Match the site's existing voice and tone (analyze recent posts)
+- Include data, examples, and actionable takeaways
+- Write naturally — avoid AI-typical phrases ("delve into", "it's important to note")
+- Target the specified word count (default: 1,200-1,500 words)
+
+### Step 5: SEO Optimize
+Apply on-page SEO using `wp-content-optimization` patterns.
+
+**Checks:**
+- Primary keyword in title, first paragraph, and 1-2 H2s
+- Meta description (150-160 chars) with keyword
+- Internal linking to 2-3 related posts (find via `wp_list_posts`)
+- Image alt text with keyword
+- Readability: short paragraphs, sub-headings every 300 words
+
+### Step 6: Structured Data
+Add appropriate Schema.org markup using `sd_inject`.
+
+**Auto-detection:**
+- Contains FAQ section → FAQPage schema
+- Is a how-to/tutorial → HowTo schema
+- Default → Article schema
+
+### Step 7: Publish
+Create the post via WordPress REST API.
+
+**Tools used:**
+- `create_content` — create the post (status: draft by default)
+- `sd_inject` — add structured data
+- User confirms before changing status to `publish`
+
+## Reference Files
+
+| File | Content |
+|------|---------|
+| `references/generation-workflow.md` | Detailed 7-step pipeline with prompts and checkpoints |
+| `references/brief-templates.md` | Brief templates for different content types |
+| `references/outline-patterns.md` | Outline structures for articles, tutorials, listicles |
+
+## Recommended Agent
+
+**`wp-content-strategist`** — coordinates the full pipeline, selects keywords, creates outlines, and manages the publish workflow.
+
+## Related Skills
+
+- **`wp-content`** — content lifecycle management and editing
+- **`wp-content-optimization`** — SEO scoring, readability analysis, meta optimization
+- **`wp-search-console`** — keyword data for Step 2 (keyword research)
+- **`wp-structured-data`** — schema injection for Step 6
+- **`wp-content-repurposing`** — distribute published content to social/email channels

package/skills/wp-content-generation/references/brief-templates.md

@@ -0,0 +1,151 @@
+# Brief Templates
+
+## Template 1: Blog Post Brief
+
+For informational articles, thought leadership, and evergreen content.
+
+```markdown
+## Content Brief: Blog Post
+
+**Topic:** [Main subject]
+**Primary Keyword:** [Target search term]
+**Secondary Keywords:** [3-5 related terms]
+
+**Audience:**
+- Who: [Target reader persona]
+- Knowledge level: [Beginner / Intermediate / Advanced]
+- Pain point: [What problem does this solve?]
+
+**Content Goal:**
+- [ ] Inform (educational content)
+- [ ] Convert (drive to product/CTA)
+- [ ] Engage (build community/discussion)
+
+**Format:** Blog post
+**Word Count:** 1,200-1,500 words
+**Tone:** [Informative / Casual / Professional / Technical]
+
+**Key Points to Cover:**
+1. [Main point 1]
+2. [Main point 2]
+3. [Main point 3]
+
+**Internal Links:** Link to [related post 1], [related post 2]
+**CTA:** [What should the reader do next?]
+**Schema Type:** Article
+```
+
+## Template 2: Tutorial Brief
+
+For step-by-step guides and how-to content.
+
+```markdown
+## Content Brief: Tutorial
+
+**Topic:** How to [achieve specific outcome]
+**Primary Keyword:** "how to [action]"
+**Secondary Keywords:** [related terms]
+
+**Audience:**
+- Who: [Target reader]
+- Prerequisite knowledge: [What should they already know?]
+- Expected outcome: [What will they be able to do after reading?]
+
+**Content Goal:** Educate and enable
+**Format:** Step-by-step tutorial
+**Word Count:** 1,500-2,000 words
+**Tone:** Instructive, encouraging
+
+**Steps to Cover:**
+1. [Step 1: Setup/Prerequisites]
+2. [Step 2: First action]
+3. [Step 3: Next action]
+4. [Step 4: Verification/Testing]
+5. [Step 5: Troubleshooting common issues]
+
+**Visuals Needed:**
+- [ ] Screenshots for each step
+- [ ] Final result image
+- [ ] Before/after comparison
+
+**Internal Links:** Link to [prerequisite guide], [advanced guide]
+**CTA:** [Try the product / Read the next tutorial]
+**Schema Type:** HowTo
+```
+
+## Template 3: Listicle Brief
+
+For "N best/top/ways" format content.
+
+```markdown
+## Content Brief: Listicle
+
+**Topic:** [N] [superlative] [subject] for [audience/purpose]
+**Primary Keyword:** "[best/top] [subject]"
+**Secondary Keywords:** [specific items in the list]
+
+**Audience:**
+- Who: [Target reader]
+- Intent: [Research / Comparison / Discovery]
+
+**Content Goal:** Inform + drive clicks to specific items
+**Format:** Numbered list (N items)
+**Word Count:** 1,000-1,800 words (depends on N)
+**Tone:** Authoritative, concise
+
+**List Items:**
+1. [Item] — [1-2 sentence reason for inclusion]
+2. [Item] — [reason]
+3. [Item] — [reason]
+...
+
+**Per-Item Structure:**
+- H2 heading with item name
+- 100-200 word description
+- Key benefit or differentiator
+- Link (if external) or CTA (if internal)
+
+**Schema Type:** Article (or ItemList if appropriate)
+```
+
+## Template 4: FAQ Content Brief
+
+For frequently asked questions and knowledge base articles.
+
+```markdown
+## Content Brief: FAQ
+
+**Topic:** [Subject area for questions]
+**Primary Keyword:** "[subject] FAQ" or "[subject] questions"
+**Secondary Keywords:** [specific questions as long-tail]
+
+**Audience:**
+- Who: [Customers / Prospects / Users]
+- Stage: [Awareness / Consideration / Decision]
+
+**Content Goal:** Answer common questions, reduce support load
+**Format:** Q&A pairs
+**Word Count:** 800-1,200 words
+**Tone:** Helpful, authoritative, concise
+
+**Questions to Answer:**
+1. What is [subject]?
+2. How does [subject] work?
+3. How much does [subject] cost?
+4. Is [subject] right for [audience]?
+5. How do I get started with [subject]?
+
+**Per-Question Structure:**
+- H3 heading with the question
+- 50-150 word answer
+- Link to detailed resource if available
+
+**Schema Type:** FAQPage
+```
+
+## Using Briefs
+
+1. Select the appropriate template based on content format
+2. Fill in all fields with the user (or ask clarifying questions)
+3. Use the completed brief as input to Step 3 (Outline) of the generation pipeline
+4. Keep the brief alongside the published post for future optimization reference

package/skills/wp-content-generation/references/generation-workflow.md

@@ -0,0 +1,132 @@
+# Generation Workflow
+
+## Full Pipeline: Brief → Publish
+
+### Step 1: Brief Creation
+
+**Goal:** Define what to write and for whom.
+
+**Prompt to user:**
+> What topic would you like to write about? Who is your target audience?
+
+**Brief structure:**
+| Field | Description | Example |
+|-------|-------------|---------|
+| Topic | Main subject | "Benefits of cactus water for athletes" |
+| Primary keyword | Target search term | "cactus water benefits" |
+| Audience | Who reads this | Health-conscious millennials |
+| Goal | Content purpose | Drive product page visits |
+| Format | Content type | Blog post / Tutorial / Listicle |
+| Word count | Target length | 1,200-1,500 words |
+| Tone | Writing style | Informative, friendly, evidence-based |
+
+### Step 2: Keyword Research
+
+**If GSC is available:**
+1. Run `gsc_query_analytics` for the primary keyword (last 90 days)
+2. Identify: current rankings, impressions, CTR
+3. Find related queries with high impressions but low CTR (optimization opportunities)
+4. Check for keyword cannibalization: `gsc_list_pages` filtered by keyword
+
+**If GSC is not available:**
+1. Use the primary keyword as anchor
+2. Generate 5-7 semantically related terms
+3. Suggest long-tail variations (question-based: "how", "why", "what is")
+
+**Output:** Primary keyword + 5-7 secondary keywords + 2-3 long-tail variations
+
+### Step 3: Outline Creation
+
+**See `outline-patterns.md` for templates per content type.**
+
+**Process:**
+1. Select outline pattern based on content format
+2. Create H2/H3 hierarchy with 5-8 main sections
+3. Assign word count targets per section
+4. Place keywords: primary in H1, secondary in H2s, long-tail in body
+5. Plan internal links: identify 2-3 existing posts to link to
+
+**Quality check:**
+- Does each section deliver standalone value?
+- Is there a logical flow from introduction to conclusion?
+- Are keywords placed naturally (not forced)?
+
+### Step 4: Draft Writing
+
+**Writing process:**
+1. Write introduction: hook → context → promise (what reader will learn)
+2. Write each section following the outline
+3. Add data points, examples, or quotes where possible
+4. Write conclusion: summary → takeaway → CTA
+5. Self-review: cut filler, tighten sentences, check flow
+
+**Voice calibration:**
+- Analyze 2-3 recent posts from the site (use `wp_list_posts`)
+- Match sentence length, vocabulary level, and tone
+- Avoid: "delve into", "it's crucial to note", "in today's fast-paced world"
+- Prefer: direct statements, active voice, specific numbers
+
+### Step 5: SEO Optimization
+
+**Checklist:**
+- [ ] Primary keyword in title (first 60 chars)
+- [ ] Primary keyword in first paragraph
+- [ ] Primary keyword in 1-2 H2 headings
+- [ ] Meta description: 150-160 chars with keyword
+- [ ] Internal links: 2-3 links to related posts
+- [ ] Image alt text includes keyword variant
+- [ ] Short paragraphs (2-4 sentences)
+- [ ] Sub-headings every 250-350 words
+- [ ] Total word count meets target
+
+**Internal linking strategy:**
+1. Fetch recent posts: `wp_list_posts(per_page: 20, orderby: "relevance", search: PRIMARY_KEYWORD)`
+2. Select 2-3 most relevant posts
+3. Link naturally within content (not forced anchor text)
+
+### Step 6: Structured Data
+
+**Auto-detect schema type from content:**
+
+| Content Pattern | Schema | Tool Call |
+|----------------|--------|-----------|
+| Contains numbered steps / "how to" | HowTo | `sd_inject(post_id, "HowTo", {...})` |
+| Contains Q&A pairs | FAQPage | `sd_inject(post_id, "FAQPage", {...})` |
+| Default blog post | Article | `sd_inject(post_id, "Article", {...})` |
+
+**Article schema (default):**
+```
+sd_inject(post_id, "Article", {
+  headline: POST_TITLE,
+  image: FEATURED_IMAGE_URL,
+  datePublished: POST_DATE,
+  author: { "@type": "Person", "name": AUTHOR_NAME },
+  description: META_DESCRIPTION
+})
+```
+
+### Step 7: Publish
+
+**Pre-publish checklist:**
+1. Show draft to user for review
+2. Confirm title, excerpt, categories, tags
+3. Confirm featured image
+4. Confirm publish date (immediate or scheduled)
+
+**Publish as draft first:**
+```
+create_content(type: "post", title: TITLE, content: HTML_CONTENT, status: "draft",
+  excerpt: EXCERPT, categories: [CAT_IDS], tags: [TAG_IDS])
+```
+
+**After user approval:**
+```
+update_content(id: POST_ID, status: "publish")
+```
+
+## Post-Publish
+
+After publishing, suggest:
+1. **Distribution:** Use `wp-content-repurposing` to create social/email variants
+2. **Monitoring:** Check GSC in 7-14 days for indexing and initial rankings
+3. **Optimization:** Re-optimize in 30 days based on search performance data