claude-plugin-wordpress-manager 2.4.0 → 2.9.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "wordpress-manager",
-  "version": "2.4.0",
-  "description": "Unified WordPress management plugin for Claude Code. Orchestrates Hostinger MCP (infrastructure), WP REST API bridge (103 tools incl. WooCommerce + Multisite + Webhooks + Mailchimp + Buffer + SendGrid), and WordPress.com MCP (hosted sites) with 12 specialized agents, 34 skills, and security hooks. Includes 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.",
+  "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"
@@ -30,7 +30,14 @@
     "buffer",
     "sendgrid",
     "social-media",
-    "email-marketing"
+    "email-marketing",
+    "google-search-console",
+    "gsc",
+    "keyword-tracking",
+    "seo-feedback",
+    "content-optimization",
+    "readability",
+    "headline-scoring"
   ],
   "mcpServers": "./.mcp.json"
 }

package/CHANGELOG.md

@@ -2,6 +2,109 @@
 
 All notable changes to the WordPress Manager plugin for Claude Code.
 
+## [2.9.0] - 2026-03-01
+
+### Added — Automated Workflows (WCOP Tier 4+5 Complete)
+- **wp-content-workflows skill** — workflow triggers for scheduled events, content lifecycle hooks, and WP action/filter hooks
+- **4 new MCP tools**: `wf_list_triggers`, `wf_create_trigger`, `wf_update_trigger`, `wf_delete_trigger`
+- **5 reference files**: schedule-triggers, content-lifecycle-hooks, wp-action-hooks, multi-channel-actions, trigger-management
+- **Detection script**: `workflow_inspect.mjs` — detects action channels, automation plugins, custom REST endpoints, WP-Cron config
+- **Safety hook**: PreToolUse confirmation for `wf_delete_trigger` (prevents accidental deletion of active workflows)
+
+### Changed
+- **wp-site-manager agent**: added Workflow Automation Management section (6-step procedure), 4 Workflow MCP tools, wp-content-workflows in Related Skills
+- **Router v16**: added 9 workflow keywords and `wp-content-workflows` route
+- **Cross-references**: wp-webhooks → wp-content-workflows, wp-social-email → wp-content-workflows
+
+### Metrics
+- Skills: 39 (+1) | MCP tools: 132 (+4) | Reference files: 192 (+5) | Detection scripts: 27 (+1) | Safety hooks: 5 (+1)
+
+### WCOP Score (Final)
+| Layer | v2.6.0 | v2.9.0 |
+|-------|--------|--------|
+| Content Factory | 9/10 | 9/10 |
+| Quality Assurance | 9/10 | 9/10 |
+| Distribution | 8/10 | 8/10 |
+| Observability | 7/10 | **9/10** |
+| Automation | 7/10 | **9/10** |
+| **Total** | **8/10** | **8.8/10** |
+
+## [2.8.0] - 2026-03-01
+
+### Added — Smart Alerting (WCOP Tier 4b)
+- **wp-alerting skill** — severity-based alert routing via Slack and SendGrid
+- **3 new MCP tools**: `slack_send_alert` (webhook), `slack_send_message` (Bot Token + Block Kit), `slack_list_channels`
+- **4 reference files**: slack-integration, alert-thresholds, escalation-paths, report-scheduling
+- **Detection script**: `alerting_inspect.mjs` — detects Slack, SendGrid, monitoring setup
+- **SiteConfig extension**: `slack_webhook_url`, `slack_bot_token`, `slack_channel`
+
+### Changed
+- **wp-monitoring-agent**: added Procedure 10 (Alert Dispatch — severity-based routing: info→Slack webhook, warning→Slack Bot + thread, critical→Slack + email), added Alerting MCP Tools section (3 Slack + 2 SendGrid)
+- **Router v15**: added 13 alerting keywords and `wp-alerting` route
+- **Cross-references**: wp-monitoring → wp-alerting + wp-analytics
+
+### Metrics
+- Skills: 38 (+1) | MCP tools: 128 (+3) | Reference files: 187 (+4) | Detection scripts: 26 (+1)
+
+## [2.7.0] - 2026-03-01
+
+### Added — Analytics (WCOP Tier 4a)
+- **wp-analytics skill** — unified analytics: GA4, Plausible, Core Web Vitals
+- **14 new MCP tools**: 6 GA4 (`ga4_run_report`, `ga4_get_realtime`, `ga4_top_pages`, `ga4_traffic_sources`, `ga4_user_demographics`, `ga4_conversion_events`), 4 Plausible (`pl_get_stats`, `pl_get_timeseries`, `pl_get_breakdown`, `pl_get_realtime`), 4 CWV (`cwv_analyze_url`, `cwv_batch_analyze`, `cwv_get_field_data`, `cwv_compare_pages`)
+- **5 reference files**: ga4-integration, plausible-setup, cwv-monitoring, analytics-dashboards, traffic-attribution
+- **Detection script**: `analytics_inspect.mjs` — detects GA4, Plausible, Google API key config
+- **SiteConfig extension**: `ga4_property_id`, `ga4_service_account_key`, `plausible_api_key`, `plausible_base_url`, `google_api_key`
+
+### Changed
+- **wp-monitoring-agent**: added Procedure 8 (Analytics Monitoring) and Procedure 9 (CWV Trend Check) with 14 analytics MCP tools
+- **Router v14**: added GA4, Plausible, CWV keywords and route
+- **Cross-references**: wp-search-console, wp-content-attribution, wp-content-optimization → wp-analytics
+
+### Metrics
+- Skills: 37 (+1) | MCP tools: 125 (+14) | Reference files: 183 (+5) | Detection scripts: 25 (+1)
+
+## [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

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-monitoring-agent.md

@@ -54,6 +54,15 @@ You are a WordPress monitoring specialist. You perform comprehensive site health
 - **Hosting**: `hosting_listWebsites` — check hosting status and resources
 - **DNS**: `DNS_getDNSRecordsV1` — verify DNS records and email auth (SPF, DKIM, DMARC)
 
+### Analytics MCP Tools (`mcp__wp-rest-bridge__ga4_*`, `mcp__wp-rest-bridge__pl_*`, `mcp__wp-rest-bridge__cwv_*`)
+- **GA4**: `ga4_run_report`, `ga4_get_realtime`, `ga4_top_pages`, `ga4_traffic_sources`, `ga4_user_demographics`, `ga4_conversion_events`
+- **Plausible**: `pl_get_stats`, `pl_get_timeseries`, `pl_get_breakdown`, `pl_get_realtime`
+- **CWV**: `cwv_analyze_url`, `cwv_batch_analyze`, `cwv_get_field_data`, `cwv_compare_pages`
+
+### Alerting MCP Tools (`mcp__wp-rest-bridge__slack_*`, `mcp__wp-rest-bridge__sg_*`)
+- **Slack**: `slack_send_alert`, `slack_send_message`, `slack_list_channels`
+- **SendGrid**: `sg_send_email`, `sg_send_template_email` (for critical severity email alerts)
+
 ### External Tools
 - **Bash**: Run health-check scripts, SSL checks, Lighthouse CLI, file integrity scans
 - **WebFetch**: Fetch PageSpeed Insights, check external URLs, verify sitemap
@@ -133,6 +142,39 @@ Run health assessments across all configured sites and generate a fleet-wide com
    - Common configuration drift from baselines
 5. **Generate fleet report** (see Fleet Report template below)
 
+### Procedure 8: Analytics Monitoring (Performance Dashboard)
+
+1. Fetch traffic data from GA4 (`ga4_top_pages`, `ga4_traffic_sources`) or Plausible (`pl_get_stats`, `pl_get_breakdown`)
+2. Fetch CWV for top pages (`cwv_batch_analyze`)
+3. Fetch keyword data from GSC (`gsc_top_queries`) if available
+4. Correlate: pages with high traffic + Poor CWV = optimization priority
+5. Generate Performance Dashboard Report
+6. If CWV Poor on top pages → recommend delegation to `wp-performance-optimizer`
+
+### Procedure 9: CWV Trend Check
+
+1. Run `cwv_analyze_url` on homepage and top landing pages
+2. Compare with CWV thresholds (Good: LCP<2.5s, INP<200ms, CLS<0.1)
+3. If available, fetch field data via `cwv_get_field_data` for real-user metrics
+4. Report status (Good/Needs Improvement/Poor) per metric
+5. If any metric is Poor → alert with specific pages and metrics
+
+### Procedure 10: Alert Dispatch (Severity-Based Routing)
+
+Route monitoring findings to notification channels based on severity. See `wp-alerting` skill for full threshold and escalation configuration.
+
+1. **Classify severity** for each finding:
+   - **Info**: Plugin updates available, backup completed, minor metric changes
+   - **Warning**: LCP > 2.5s, error rate > 2%, disk > 80%, SSL < 30 days
+   - **Critical**: Site down, LCP > 4s, error rate > 5%, disk > 95%, security vulnerability
+2. **Dispatch by severity**:
+   - **Info** → `slack_send_alert` to general channel (simple text)
+   - **Warning** → `slack_send_message` with Block Kit formatting + threaded details
+   - **Critical** → `slack_send_message` with `<!channel>` mention + `sg_send_email` to alert recipients
+3. **Deduplication**: Check `{site}:{metric}:{severity}` key against cooldown window (info: 60m, warning: 30m, critical: 10m). Severity escalation bypasses cooldown.
+4. **Recovery**: When a metric returns to normal after an alert, send recovery notification to the same channel/thread.
+5. **Scheduled reports**: Use Procedure 8 output to generate daily/weekly health digests via Slack Block Kit.
+
 ## Report Generation
 
 After completing relevant procedures, generate a report following the templates in `references/reporting-templates.md`:
@@ -232,3 +274,5 @@ For issues found during monitoring:
 - **`wp-audit` skill** — one-time comprehensive audit (security + performance + SEO)
 - **`wp-security` skill** — security hardening procedures
 - **`wp-performance` skill** — backend profiling and optimization
+- **`wp-analytics` skill** — analytics setup, traffic reports, CWV monitoring
+- **`wp-alerting` skill** — alert thresholds, severity routing, Slack/email escalation, scheduled reports

package/agents/wp-site-manager.md

@@ -52,6 +52,7 @@ Content and data management via WordPress REST API:
 - **Comments**: `list_comments`, `get_comment`, `create_comment`, `update_comment`, `delete_comment`
 - **Plugins**: `list_plugins`, `get_plugin`, `activate_plugin`, `deactivate_plugin`, `create_plugin`
 - **WP.org**: `search_plugin_repository`, `get_plugin_details`
+- **Workflows**: `wf_list_triggers`, `wf_create_trigger`, `wf_update_trigger`, `wf_delete_trigger`
 
 ### 2. Hostinger MCP (`mcp__hostinger-mcp__*`)
 Infrastructure and hosting management:
@@ -148,11 +149,28 @@ When setting up or managing a multi-language WordPress Multisite network:
 
 See the `wp-multilang-network` skill for detailed reference files on network architecture, hreflang, content sync, language routing, and international SEO.
 
+### Workflow Automation Management
+
+Manage automated workflow triggers that connect WordPress events to notification channels.
+
+1. **Detect existing workflows**: Run `node skills/wp-content-workflows/scripts/workflow_inspect.mjs` to assess current configuration
+2. **List triggers**: Use `wf_list_triggers` to see all configured workflows, filter by `status` or `type`
+3. **Create trigger**: Use `wf_create_trigger` with:
+   - `type`: `schedule` (cron-based), `hook` (WP action/filter), or `content` (post lifecycle)
+   - `conditions`: Trigger-specific conditions (cron interval, hook name, post status transition)
+   - `actions`: Array of notification actions (Slack, email, webhook) with templates and recipients
+4. **Update trigger**: Use `wf_update_trigger` to modify conditions, actions, or status (activate/deactivate)
+5. **Delete trigger**: Use `wf_delete_trigger` — requires user confirmation via safety hook
+6. **Test trigger**: Create with `status: "inactive"`, review configuration, then update to `status: "active"`
+
+See the `wp-content-workflows` skill for reference files on schedule patterns, content lifecycle hooks, WP action hooks, multi-channel actions, and trigger management.
+
 ### Safety Rules
 - NEVER delete content without explicit user confirmation
 - NEVER deactivate plugins without listing dependencies first
 - NEVER modify published content status without confirmation
 - Always show a summary of changes before executing bulk operations
+- NEVER delete workflow triggers without explicit user confirmation (safety hook enforced)
 
 ## Specialized Agents
 
@@ -176,3 +194,4 @@ For domain-specific tasks, delegate to specialized agents:
 
 - **`wp-multisite` skill** — multisite network management with 10 MCP tools
 - **`wp-multilang-network` skill** — multi-language network orchestration (hreflang, content sync, international SEO)
+- **`wp-content-workflows` skill** — workflow triggers, scheduled events, content lifecycle automation