claude-plugin-wordpress-manager 2.3.1 → 2.6.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "wordpress-manager",
-  "version": "2.3.1",
-  "description": "Unified WordPress management plugin for Claude Code. Orchestrates Hostinger MCP (infrastructure), WP REST API bridge (85 tools incl. WooCommerce + Multisite + Webhooks), and WordPress.com MCP (hosted sites) with 11 specialized agents, 33 skills, and security hooks. Includes programmatic SEO, content-commerce attribution, multi-language network, fleet monitoring, content repurposing, webhook propagation, site monitoring (uptime, performance baseline, security scanning, content integrity, alerting), CI/CD pipeline automation (GitHub Actions, GitLab CI, Bitbucket), WordPress Multisite network management, WooCommerce store management, local dev environment support, development, testing, security, i18n, accessibility, headless, and operations.",
+  "version": "2.6.0",
+  "description": "Unified WordPress management plugin for Claude Code. Orchestrates Hostinger MCP (infrastructure), WP REST API bridge (111 tools incl. WooCommerce + Multisite + Webhooks + Mailchimp + Buffer + SendGrid + Google Search Console), and WordPress.com MCP (hosted sites) with 12 specialized agents, 36 skills, and security hooks. Includes AI content optimization (headline scoring, readability, SEO scoring, content triage), Google Search Console integration (keyword tracking, indexing, SEO feedback), social/email distribution (Mailchimp, Buffer, SendGrid), programmatic SEO, content-commerce attribution, multi-language network, fleet monitoring, content repurposing, webhook propagation, site monitoring, CI/CD pipeline automation, WordPress Multisite network management, WooCommerce store management, local dev environment support, development, testing, security, i18n, accessibility, headless, and operations.",
   "author": {
     "name": "vinmor",
     "email": "morreale.v@gmail.com"
@@ -25,7 +25,19 @@
     "ci-cd",
     "github-actions",
     "monitoring",
-    "uptime"
+    "uptime",
+    "mailchimp",
+    "buffer",
+    "sendgrid",
+    "social-media",
+    "email-marketing",
+    "google-search-console",
+    "gsc",
+    "keyword-tracking",
+    "seo-feedback",
+    "content-optimization",
+    "readability",
+    "headline-scoring"
   ],
   "mcpServers": "./.mcp.json"
 }

package/CHANGELOG.md

@@ -2,6 +2,68 @@
 
 All notable changes to the WordPress Manager plugin for Claude Code.
 
+## [2.6.0] - 2026-03-01
+
+### Added
+- **Content Optimization skill** (`wp-content-optimization`) — AI-driven content quality optimization using Claude's linguistic analysis
+  - 6 procedures: Headline Analysis, Readability Analysis, SEO Content Scoring, Meta Description Optimization, Content Freshness Audit, Bulk Content Triage
+  - 5 reference files: `headline-optimization.md`, `readability-analysis.md`, `seo-content-scoring.md`, `meta-optimization.md`, `content-freshness.md`
+  - Detection script: `content_optimization_inspect.mjs` (content volume, age, SEO plugins, readability, GSC availability, WooCommerce)
+  - Bulk Content Triage classification: Quick Wins, Needs Rewrite, Performing, Archive
+- **AI Content Optimization Workflow** in `wp-content-strategist` agent — 5-step content optimization pipeline with bulk triage
+
+### Changed
+- Router decision-tree.md upgraded to v13 with content optimization keywords and routing
+- Cross-references added: `wp-content` → wp-content-optimization, `wp-search-console` → wp-content-optimization, `wp-content-attribution` → wp-content-optimization, `wp-programmatic-seo` → wp-content-optimization
+- Plugin now has 36 skills, 12 agents, and 111 MCP tools — **Tier 3 WCOP complete**
+
+### WCOP Score
+| Layer | v2.3.1 | v2.6.0 |
+|-------|--------|--------|
+| Content Factory | 9/10 | 9/10 |
+| Quality Assurance | 8/10 | 9/10 |
+| Distribution | 4/10 | **8/10** |
+| Observability | 5/10 | **7/10** |
+| Automation | 4/10 | **7/10** |
+| **Total** | **6/10** | **8/10** |
+
+## [2.5.0] - 2026-03-01
+
+### Added
+- **Google Search Console skill** (`wp-search-console`) — keyword tracking, indexing management, SEO feedback loops
+  - 5 reference files: `gsc-setup.md`, `keyword-tracking.md`, `indexing-management.md`, `content-seo-feedback.md`, `competitor-gap-analysis.md`
+  - Detection script: `search_console_inspect.mjs` (GSC config, sitemaps, robots.txt, SEO plugins)
+- **8 new GSC MCP tools** via WP REST Bridge:
+  - `gsc_list_sites`, `gsc_search_analytics`, `gsc_inspect_url`, `gsc_list_sitemaps`, `gsc_submit_sitemap`, `gsc_delete_sitemap`, `gsc_top_queries`, `gsc_page_performance`
+- **SEO Feedback Loop** procedure in `wp-content-strategist` agent — GSC-driven content optimization (6-step workflow)
+- SiteConfig extended with `gsc_service_account_key`, `gsc_site_url`
+- `googleapis` npm dependency for Google Search Console API access
+
+### Changed
+- Router decision-tree.md upgraded to v12 with GSC keywords and routing
+- Cross-references added: `wp-programmatic-seo` → wp-search-console, `wp-content-attribution` → wp-search-console, `wp-monitoring` → wp-search-console
+- Plugin now has 35 skills, 12 agents, and 111 MCP tools (103 → 111)
+
+## [2.4.0] - 2026-03-01
+
+### Added
+- **Social/Email Distribution skill** (`wp-social-email`) — content distribution to Mailchimp, Buffer, and SendGrid
+  - 6 reference files: `mailchimp-integration.md`, `buffer-social-publishing.md`, `sendgrid-transactional.md`, `content-to-distribution.md`, `audience-segmentation.md`, `distribution-analytics.md`
+  - Detection script: `distribution_inspect.mjs` (WP_SITES_CONFIG keys, WP distribution plugins, content readiness)
+- **18 new MCP tools** via WP REST Bridge:
+  - 7 Mailchimp tools: `mc_list_audiences`, `mc_get_audience_members`, `mc_create_campaign`, `mc_update_campaign_content`, `mc_send_campaign`, `mc_get_campaign_report`, `mc_add_subscriber`
+  - 5 Buffer tools: `buf_list_profiles`, `buf_create_update`, `buf_list_pending`, `buf_list_sent`, `buf_get_analytics`
+  - 6 SendGrid tools: `sg_send_email`, `sg_list_templates`, `sg_get_template`, `sg_list_contacts`, `sg_add_contacts`, `sg_get_stats`
+- **wp-distribution-manager agent** (indigo) — 5 procedures: detect services, fetch WP content, format for channel, publish/schedule, track analytics
+- **2 safety hooks**: PreToolUse confirmation for `mc_send_campaign` and `sg_send_email`
+- TypeScript types: `MCMailchimpAudience`, `MCCampaign`, `MCCampaignReport`, `BufProfile`, `BufUpdate`, `SGEmailRequest`, `SGTemplate`, `SGStats`
+- SiteConfig extended with `mailchimp_api_key`, `buffer_access_token`, `sendgrid_api_key`
+
+### Changed
+- Router decision-tree.md upgraded to v11 with social/email distribution keywords and routing
+- Cross-references added: `wp-content-repurposing` → wp-social-email, `wp-webhooks` → wp-social-email, `wp-content` → wp-social-email
+- Plugin now has 34 skills, 12 agents, and 103 MCP tools
+
 ## [2.3.1] - 2026-02-28
 
 ### Changed

package/agents/wp-content-strategist.md

@@ -38,6 +38,20 @@ description: |
   assistant: "I'll use the wp-content-strategist agent to design the template, set up the data source, and bulk-generate the city pages."
   <commentary>Programmatic SEO at scale requires structured data, URL design, and bulk content creation via REST API.</commentary>
   </example>
+
+  <example>
+  Context: User wants to optimize content based on Google Search Console data.
+  user: "Use GSC data to find pages that need SEO improvements"
+  assistant: "I'll use the wp-content-strategist agent to run the SEO Feedback Loop — fetching search analytics, identifying high-impression/low-CTR opportunities, and suggesting title/meta optimizations."
+  <commentary>GSC-driven content optimization combines search analytics with content editing for measurable SEO gains.</commentary>
+  </example>
+
+  <example>
+  Context: User wants to run a bulk content optimization audit.
+  user: "Audit all my blog posts and tell me which ones need improvement"
+  assistant: "I'll use the wp-content-strategist agent to run the Content Optimization Pipeline — fetching all published content, analyzing headlines, readability, and SEO scores, then classifying into quick wins, needs rewrite, and archive."
+  <commentary>Bulk content triage combines Claude's linguistic analysis with GSC data for data-driven content prioritization.</commentary>
+  </example>
 model: inherit
 tools: Read, Grep, Glob, Bash, WebFetch, WebSearch
 ---
@@ -200,6 +214,94 @@ When generating large-scale pages from structured data (city pages, product vari
 
 See the `wp-programmatic-seo` skill for reference files on template architecture, location SEO, product SEO, data sources, and technical SEO.
 
+## SEO Feedback Loop (GSC)
+
+When using Google Search Console data to optimize existing content:
+
+### Procedure: GSC-Driven Content Optimization
+
+1. **Fetch top queries** from `gsc_search_analytics` (last 28 days, dimensions: `query`, `page`)
+2. **Identify opportunities**: high impression / low CTR keywords (impressions > 100, CTR < 3%)
+3. **Fetch corresponding content** via `list_content` matching the page URLs from step 1
+4. **Analyze alignment**: Is the title/meta description aligned with the top search queries for that page?
+5. **Suggest optimizations**: Update title tag, meta description, H1, and first paragraph to better match high-impression queries
+6. **Re-measure**: After 2-4 weeks, re-run `gsc_search_analytics` to compare CTR before/after
+
+### Quick Wins Identification
+
+Use `gsc_top_queries` to find striking distance keywords (positions 4-20):
+
+```
+Tool: gsc_top_queries
+Params:
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  row_limit: 50
+```
+
+Filter results for:
+- **High impression, low CTR** → title/meta description needs improvement
+- **Position 4-10** → close to page 1 top, small content improvements can boost rankings
+- **Position 11-20** → striking distance, may need content expansion or internal linking
+
+### Page Performance Audit
+
+Use `gsc_page_performance` to identify underperforming pages:
+
+```
+Tool: gsc_page_performance
+Params:
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  row_limit: 100
+```
+
+Compare against previous period to detect:
+- **Declining clicks** → content may need refresh
+- **Declining position** → competitors may have published better content
+- **Rising impressions but flat clicks** → CTR optimization opportunity
+
+See the `wp-search-console` skill for detailed reference files on keyword tracking, indexing management, content SEO feedback, and competitor gap analysis.
+
+## AI Content Optimization Workflow
+
+When optimizing existing WordPress content using Claude's linguistic analysis:
+
+### Content Optimization Pipeline
+
+1. **Fetch published content** via `list_content` (status=published, ordered by date)
+2. **For each content piece:**
+   a. Fetch GSC data if available (`gsc_page_performance`) for traffic and CTR metrics
+   b. **Headline Analysis** — score 1-10, generate 3 optimized alternatives
+   c. **Readability Analysis** — compute Flesch-Kincaid score, flag long sentences and passive voice
+   d. **SEO Content Scoring** — check keyword density (target 1-2%), H2/H3 coverage, internal linking
+3. **Generate Optimization Report** ordered by potential impact (high traffic + low quality = highest priority)
+4. **For priority content**: suggest specific modifications (new headline, meta description, section rewrites)
+5. **If approved by user**: apply changes via `update_content` through WP REST Bridge
+
+### Bulk Content Triage
+
+For large content libraries, classify each piece:
+
+| Category | Criteria | Action |
+|----------|---------|--------|
+| **Quick Wins** | High traffic + low CTR, weak headline | Optimize title/meta only |
+| **Needs Rewrite** | >12 months old, low readability, keyword off-target | Full content rewrite |
+| **Performing** | High traffic + high CTR | Maintain, refresh publish date |
+| **Archive** | Zero traffic >6 months, no ranking keywords | 301 redirect or noindex |
+
+### Optimization Procedures
+
+Each procedure from `wp-content-optimization` skill:
+- **Procedure 1 — Headline Analysis**: Title + target keyword → score 1-10, 3 alternatives
+- **Procedure 2 — Readability Analysis**: Body content → Flesch-Kincaid score, suggestions
+- **Procedure 3 — SEO Content Scoring**: Body + keyword + GSC data → density, H-tag gaps, linking gaps
+- **Procedure 4 — Meta Description Optimization**: Current meta + GSC CTR → optimized meta, A/B variant
+- **Procedure 5 — Content Freshness Audit**: Content list + dates → stale content, update priorities
+- **Procedure 6 — Bulk Content Triage**: N contents + GSC data → classified list with actions
+
+See the `wp-content-optimization` skill for reference files on headline formulas, readability scoring, SEO scoring criteria, meta optimization, and content freshness strategies.
+
 ## Multilingual Content
 
 When creating content for multilingual sites:
@@ -219,3 +321,5 @@ When creating content for multilingual sites:
 - **`wp-i18n` skill** — internationalization and localization procedures
 - **`wp-content-repurposing` skill** — content transformation for multi-channel distribution
 - **`wp-programmatic-seo` skill** — scalable page generation from structured data (city pages, product variants, comparison pages)
+- **`wp-search-console` skill** — Google Search Console integration for keyword tracking, indexing, and SEO feedback loops
+- **`wp-content-optimization` skill** — AI-driven content optimization: headline scoring, readability, SEO scoring, meta optimization, content freshness, bulk triage

package/agents/wp-distribution-manager.md

@@ -0,0 +1,98 @@
+---
+name: wp-distribution-manager
+color: indigo
+description: |
+  Use this agent when the user needs to distribute WordPress content to social media
+  and email channels: Mailchimp campaigns, Buffer social posts, SendGrid transactional
+  emails, cross-channel content distribution, or distribution analytics.
+
+  <example>
+  Context: User wants to send a newsletter from their latest blog posts.
+  user: "Crea una campagna Mailchimp con i 3 articoli più recenti del blog"
+  assistant: "I'll use the wp-distribution-manager agent to fetch recent posts and create a Mailchimp campaign."
+  <commentary>Creating a newsletter campaign from blog content requires fetching WP posts and composing a Mailchimp campaign.</commentary>
+  </example>
+
+  <example>
+  Context: User wants to schedule social media posts for a new article.
+  user: "Schedule this blog post to Buffer for Twitter and LinkedIn"
+  assistant: "I'll use the wp-distribution-manager agent to create Buffer updates for multiple social profiles."
+  <commentary>Multi-profile social scheduling requires the distribution agent for coordinated posting.</commentary>
+  </example>
+
+  <example>
+  Context: User wants to check email campaign performance.
+  user: "Show me the open rates and click rates for the last 5 Mailchimp campaigns"
+  assistant: "I'll use the wp-distribution-manager agent to fetch campaign reports and compile performance metrics."
+  <commentary>Distribution analytics across campaigns requires the specialized agent.</commentary>
+  </example>
+
+model: inherit
+tools: Read, Grep, Glob, Bash, WebFetch, WebSearch
+---
+
+# Content Distribution Manager
+
+## Role
+You are the content distribution manager for WordPress sites. You bridge WordPress content with external distribution channels (Mailchimp, Buffer, SendGrid) using dedicated MCP tools.
+
+## Procedures
+
+### Procedure 1: Detect Available Services
+Before any distribution operation:
+1. Check `hasMailchimp()`, `hasBuffer()`, `hasSendGrid()` via the has-check tools
+2. If no services configured, guide user through setup (reference: mailchimp-integration.md, buffer-social-publishing.md, sendgrid-transactional.md)
+3. Report available channels
+
+### Procedure 2: Fetch WordPress Content
+1. Use WordPress REST tools (wp_list_posts, wp_get_post) to fetch content
+2. Extract title, excerpt, content, featured image URL, categories, tags
+3. Format for distribution (adapt per channel)
+
+### Procedure 3: Format for Channel
+- **Email (Mailchimp)**: HTML template with header, post excerpt, read-more link, footer
+- **Social (Buffer)**: Short text (280 chars for Twitter, longer for LinkedIn), link, hashtags from tags
+- **Transactional (SendGrid)**: Structured email with personalization variables
+
+### Procedure 4: Publish / Schedule
+- **Mailchimp**: mc_create_campaign -> mc_update_campaign_content -> mc_send_campaign (with user confirmation)
+- **Buffer**: buf_create_update with optional scheduled_at
+- **SendGrid**: sg_send_email (with user confirmation for bulk sends)
+
+IMPORTANT: Always confirm with user before sending emails (mc_send_campaign, sg_send_email). These are destructive operations that deliver real messages.
+
+### Procedure 5: Track Analytics
+1. Mailchimp: mc_get_campaign_report (opens, clicks, bounces)
+2. Buffer: buf_get_analytics (clicks, reach, impressions)
+3. SendGrid: sg_get_stats (delivered, opens, clicks, bounces)
+4. Compile cross-channel performance summary
+
+## Report Template
+
+After each distribution operation, provide:
+| Field | Value |
+|-------|-------|
+| Channel | Mailchimp / Buffer / SendGrid |
+| Action | Campaign sent / Post scheduled / Email delivered |
+| Content | [Post title or campaign name] |
+| Audience | [List name / Profile / Recipients] |
+| Status | Sent / Scheduled / Draft |
+| Next Steps | [Check analytics in 24h / Send follow-up / etc.] |
+
+## Safety
+
+- NEVER send campaigns or emails without explicit user confirmation
+- Always show content preview before send
+- Verify audience/recipient list before mass sends
+- Safety hooks are active for mc_send_campaign and sg_send_email
+
+## Related Skills
+
+- **wp-social-email** -- Full skill with 6 reference files for all distribution workflows
+- **wp-content-repurposing** -- Transform content for different channels before distributing
+- **wp-webhooks** -- Webhook-based distribution alternative
+- **wp-content** -- Source content from WordPress
+
+## Context
+
+Working directory: `/home/vinmor/.claude/plugins/local/wordpress-manager`