claude-plugin-wordpress-manager 2.3.1 → 2.6.0

package/skills/wp-content-optimization/references/readability-analysis.md

@@ -0,0 +1,201 @@
+# Readability Analysis
+
+## Overview
+
+Readability analysis measures how easy content is to read and understand. Claude performs Flesch-Kincaid scoring, sentence length analysis, passive voice detection, paragraph assessment, and jargon identification directly on WordPress content — no external readability tools required. The goal is web-optimized content that matches the target audience's reading level.
+
+## Flesch-Kincaid Scoring
+
+### Formula
+```
+Flesch Reading Ease = 206.835 - (1.015 × ASL) - (84.6 × ASW)
+
+Where:
+  ASL = Average Sentence Length (words per sentence)
+  ASW = Average Syllables per Word
+```
+
+### Score Interpretation
+
+| Score | Grade Level | Audience | Action |
+|-------|-------------|----------|--------|
+| 90-100 | 5th grade | Very easy, children | Too simple for most web content |
+| 80-89 | 6th grade | Easy, conversational | Good for broad consumer content |
+| 70-79 | 7th grade | Fairly easy | Good for general web content |
+| 60-69 | 8th-9th grade | Standard | **Target for most WordPress content** |
+| 50-59 | 10th-12th grade | Fairly difficult | Acceptable for professional audience |
+| 30-49 | College | Difficult | Only for specialized/technical content |
+| 0-29 | Graduate | Very difficult | Rewrite for web consumption |
+
+### Target Scores by Content Type
+
+| Content Type | Target Score | Rationale |
+|--------------|-------------|-----------|
+| Blog posts | 60-70 | General audience, scannable |
+| Product descriptions | 65-75 | Clear, benefit-focused |
+| Technical documentation | 45-60 | Professional audience |
+| Landing pages | 70-80 | Must be instantly clear |
+| Email newsletters | 65-75 | Quick reading format |
+
+## Sentence Length Analysis
+
+### Guidelines
+
+| Metric | Target | Flag Threshold |
+|--------|--------|----------------|
+| Average sentence length | 15-20 words | >20 words average |
+| Maximum sentence length | 35 words | >40 words |
+| Short sentence ratio | 20-30% under 10 words | <10% short sentences |
+| Variety | Mix of short, medium, long | All same length |
+
+### Sentence Length Distribution
+Ideal content alternates between sentence lengths for rhythm:
+```
+Short sentence (5-10 words).     ← Punchy, creates emphasis
+Medium sentence (11-20 words).   ← Core information delivery
+Long sentence (21-30 words).     ← Complex ideas, supporting detail
+Short sentence (5-10 words).     ← Reset reader attention
+```
+
+### Fixing Long Sentences
+Strategies for breaking up long sentences:
+1. **Split at conjunctions** — break at "and", "but", "while", "although"
+2. **Remove relative clauses** — move "which" and "that" clauses to new sentences
+3. **Use bullet lists** — convert compound sentences into scannable lists
+4. **Front-load the point** — put the main idea first, details after
+
+### Example
+```
+Before (38 words):
+"WordPress is a content management system that allows users to create websites
+and blogs with themes and plugins, which can be customized to match any brand
+identity and extended with additional functionality."
+
+After (two sentences, 15 + 16 words):
+"WordPress is a content management system for creating websites and blogs.
+Themes and plugins let you customize the design and extend functionality."
+```
+
+## Passive Voice Detection
+
+### What to Flag
+Passive voice constructions where the subject receives the action:
+```
+Passive: "The plugin was installed by the user."
+Active:  "The user installed the plugin."
+```
+
+### Target
+- Maximum 10% of sentences in passive voice
+- 5% or less is ideal for web content
+
+### Common Passive Patterns
+| Passive Pattern | Active Rewrite |
+|----------------|----------------|
+| "was created by" | "[subject] created" |
+| "is recommended" | "we recommend" |
+| "can be configured" | "you can configure" |
+| "has been updated" | "we updated" / "[subject] updated" |
+| "should be installed" | "install" (imperative) |
+
+### When Passive Is Acceptable
+- Scientific or technical writing where the actor is irrelevant
+- When the object is more important than the subject
+- Policy or legal statements
+
+## Paragraph Length Guidelines
+
+| Metric | Target | Flag |
+|--------|--------|------|
+| Sentences per paragraph | 2-4 | >5 sentences |
+| Words per paragraph | 40-80 | >100 words |
+| One-sentence paragraphs | Occasional for emphasis | >3 consecutive |
+| Wall of text | Never | Any paragraph >150 words |
+
+### Web-Specific Rules
+- Break up paragraphs more aggressively than print
+- Use subheadings every 200-300 words
+- Include visual breaks (images, lists, blockquotes) every 300-400 words
+- One idea per paragraph
+
+## Jargon and Complexity Detection
+
+### Flag These Patterns
+1. **Industry jargon** — terms unknown to general audience (e.g., "canonical URL", "transclusion")
+2. **Acronyms without definition** — first use must define the acronym
+3. **Multi-syllable alternatives** — when simpler words exist
+4. **Nominalization** — turning verbs into nouns ("optimization" instead of "optimize")
+5. **Double negatives** — "not uncommon" instead of "common"
+
+### Simplification Table
+
+| Complex | Simple |
+|---------|--------|
+| utilize | use |
+| implement | add / set up |
+| functionality | feature |
+| methodology | method |
+| in order to | to |
+| at this point in time | now |
+| a large number of | many |
+| in the event that | if |
+| prior to | before |
+| subsequent to | after |
+
+## Step-by-Step Workflow
+
+### Step 1: Fetch Content
+```
+Use get_content with the post ID to retrieve full body content.
+Strip HTML tags for text-only analysis.
+```
+
+### Step 2: Compute Metrics
+Claude analyzes the plain text and computes:
+- Total word count
+- Total sentence count
+- Average sentence length (words/sentences)
+- Estimated Flesch-Kincaid score
+- Passive voice percentage
+- Average paragraph length
+- Jargon terms identified
+
+### Step 3: Generate Report
+```
+Readability Report for: "Post Title"
+═══════════════════════════════════
+Flesch-Kincaid Score: 58 (target: 60-70) ⚠ Below target
+Average Sentence Length: 22 words (target: <20) ⚠ Too long
+Passive Voice: 15% (target: <10%) ⚠ Too high
+Avg Paragraph Length: 95 words (target: <80) ⚠ Long paragraphs
+Jargon Terms Found: 3 (canonical, transclusion, REST endpoint)
+
+Top Issues:
+1. 5 sentences over 35 words — break into shorter sentences
+2. 3 paragraphs over 100 words — split with subheadings
+3. "canonical URL" used without definition — add brief explanation
+```
+
+### Step 4: Suggest Improvements
+Claude generates specific rewrite suggestions:
+- Rewrites for the 3 longest sentences
+- Paragraph split points with suggested subheadings
+- Passive-to-active voice conversions
+- Jargon simplifications or definitions to add
+
+### Step 5: Apply Changes (Optional)
+```
+Use update_content to apply approved changes.
+Preserve all HTML structure, links, and media.
+Only modify text content for readability improvements.
+```
+
+## Best Practices
+
+- Always analyze the full post body, not just excerpts
+- Consider the target audience when evaluating scores (technical docs have lower target)
+- Preserve the author's voice — readability improvements should not flatten style
+- Do not oversimplify to the point of losing nuance or accuracy
+- Run readability analysis after SEO optimization to ensure keyword insertion did not harm readability
+- Check readability on both desktop and mobile (shorter paragraphs matter more on mobile)
+- Use transition words (however, therefore, for example) to maintain flow after sentence splitting

package/skills/wp-content-optimization/references/seo-content-scoring.md

@@ -0,0 +1,245 @@
+# SEO Content Scoring
+
+## Overview
+
+SEO content scoring evaluates how well a piece of WordPress content is optimized for search engines. Claude performs keyword density analysis, heading hierarchy assessment, internal and external linking checks, image alt text coverage, and content structure evaluation. When GSC data is available, Claude cross-references actual search queries to validate keyword targeting.
+
+## Keyword Density Analysis
+
+### Target Ranges
+
+| Keyword Type | Target Density | Minimum | Maximum |
+|-------------|---------------|---------|---------|
+| Primary keyword | 1-2% | 0.5% | 3% |
+| Secondary keywords | 0.5-1% each | 0.3% | 1.5% |
+| LSI/related terms | Natural occurrence | — | — |
+
+### Density Calculation
+```
+Keyword Density = (Number of keyword occurrences / Total word count) × 100
+```
+
+### Placement Rules
+1. **Title (H1)** — primary keyword must appear (preferably front-loaded)
+2. **First paragraph** — primary keyword within first 100 words
+3. **Subheadings** — primary or secondary keyword in at least 1 H2
+4. **Body distribution** — keyword spread throughout, not clustered
+5. **Last paragraph** — primary keyword in conclusion
+6. **URL slug** — primary keyword in the URL
+
+### Keyword Stuffing Detection
+Flag when:
+- Primary keyword density exceeds 3%
+- Same keyword appears in consecutive sentences
+- Keyword is forced into unnatural phrasing
+- Multiple exact-match keyword repetitions in one paragraph
+
+### Example Analysis
+```
+Post: "WordPress Speed Optimization Guide" (1500 words)
+Primary keyword: "wordpress speed optimization"
+
+Occurrences: 18 times
+Density: 18/1500 × 100 = 1.2% ✓ Within target
+
+Distribution:
+- Title: ✓ Present
+- First paragraph: ✓ Present (word 12)
+- H2 headings: ✓ 1 of 4 H2s contains keyword
+- Last paragraph: ✓ Present
+- URL: ✓ /wordpress-speed-optimization-guide
+```
+
+## H2/H3 Hierarchy Coverage
+
+### Structure Requirements
+
+| Element | Requirement | Check |
+|---------|------------|-------|
+| H1 | Exactly 1 per page, contains primary keyword | Required |
+| H2 | 2-6 per post, secondary keywords in 50%+ | Required |
+| H3 | As needed under H2, long-tail keywords | Recommended |
+| H4+ | Rare, deep detail only | Optional |
+| Skip levels | Never (H1 → H3 without H2) | Flag as error |
+
+### Heading Optimization Checklist
+- [ ] One H1 only, matching the post title
+- [ ] H2s outline the main sections (scannable table of contents)
+- [ ] At least one H2 contains the primary keyword
+- [ ] H3s provide detail under their parent H2
+- [ ] No heading level is skipped
+- [ ] Headings are descriptive (not generic like "More Info")
+- [ ] Secondary keywords distributed across H2/H3 headings
+
+### Example Heading Audit
+```
+H1: WordPress Speed Optimization: Complete Guide          ✓ Primary keyword
+  H2: Why WordPress Speed Matters                         ✓ Descriptive
+    H3: Impact on SEO Rankings                            ✓ Secondary keyword
+    H3: Impact on User Experience                         ✓ Related term
+  H2: How to Measure WordPress Speed                      ✓ Secondary keyword
+  H2: 10 WordPress Speed Optimization Techniques          ✓ Primary keyword
+    H3: Enable Caching                                    ✓ Specific
+    H3: Optimize Images                                   ✓ Specific
+    H3: Minimize CSS and JavaScript                       ✓ Specific
+  H2: Conclusion                                          ⚠ Generic, add keyword
+```
+
+## Internal Linking Analysis
+
+### Minimum Standards
+
+| Content Length | Internal Links | Rationale |
+|---------------|---------------|-----------|
+| < 500 words | 1-2 links | Short content, few linking opportunities |
+| 500-1000 words | 2-3 links | Standard blog post |
+| 1000-2000 words | 3-5 links | In-depth article |
+| 2000+ words | 5-8 links | Pillar content, extensive topic |
+
+### What to Check
+1. **Link count** — meets minimum for content length
+2. **Anchor text** — descriptive, keyword-rich (not "click here")
+3. **Link relevance** — linked pages are topically related
+4. **Link distribution** — links spread throughout content, not clustered
+5. **Orphan detection** — identify posts with zero inbound internal links
+6. **Reciprocal links** — pillar pages link to cluster posts and vice versa
+
+### Link Opportunity Detection
+Claude identifies linking opportunities by:
+- Finding mentions of topics that have dedicated pages on the site
+- Detecting keyword phrases that match other post titles
+- Identifying related content that could provide context
+- Suggesting links to pillar pages from cluster content
+
+## External Linking
+
+### Guidelines
+
+| Metric | Target |
+|--------|--------|
+| External links per post | 1-2 minimum |
+| Link targets | Authoritative, relevant sources (.gov, .edu, industry leaders) |
+| Link freshness | Source content should be current (not outdated) |
+| Nofollow | Use for sponsored or untrusted links |
+| Open in new tab | Yes for external links (target="_blank") |
+
+### What to Avoid
+- Linking to direct competitors' commercial pages
+- Linking to low-authority or spammy sites
+- Excessive external links (>5 per 1000 words)
+- Broken external links (check periodically)
+
+## Image Alt Text Coverage
+
+### Requirements
+| Check | Standard |
+|-------|----------|
+| All images have alt text | 100% coverage required |
+| Alt text includes keyword | At least 1 image per post |
+| Alt text is descriptive | Describes the image content |
+| Alt text length | 5-15 words |
+| Decorative images | Empty alt="" (not missing alt) |
+
+### Example
+```
+Good: alt="WordPress performance optimization dashboard showing page load times"
+Bad:  alt="image1" or alt="" (on informational image) or alt missing
+```
+
+## Combining with GSC Data
+
+When Google Search Console is available, enrich the SEO scoring with real search data:
+
+### Step 1: Fetch Search Queries for the Page
+```
+Use gsc_search_analytics with the page URL to get actual queries driving traffic.
+```
+
+### Step 2: Compare Target vs Actual Keywords
+```
+Target keyword: "wordpress speed optimization"
+Actual top queries from GSC:
+  1. "wordpress speed" (pos 8, 500 impressions)
+  2. "wordpress performance" (pos 12, 300 impressions)
+  3. "how to speed up wordpress" (pos 15, 200 impressions)
+
+Analysis: Content ranks for related terms but not the exact target.
+Action: Strengthen primary keyword presence, add "how to speed up wordpress" as H2.
+```
+
+### Step 3: Identify Keyword Gaps
+- Queries with high impressions but low CTR → meta description issue
+- Queries with high position (>10) → content depth issue
+- Queries the page ranks for that are not in the content → add sections
+
+## SEO Content Score Card
+
+### Scoring Template
+```
+SEO Content Score for: "Post Title"
+═════════════════════════════════════
+Keyword Density:      1.2%    ✓ (target: 1-2%)
+Keyword in H1:        Yes     ✓
+Keyword in First 100: Yes     ✓
+Keyword in URL:       Yes     ✓
+
+H2 Count:             4       ✓ (target: 2-6)
+H2 with Keywords:     2/4     ✓ (target: 50%+)
+H3 Count:             6       ✓
+Heading Hierarchy:    Valid   ✓ (no skipped levels)
+
+Internal Links:       2       ⚠ (target: 3-5 for 1200 words)
+External Links:       1       ✓ (target: 1-2)
+Anchor Text Quality:  Good    ✓
+
+Image Alt Coverage:   3/4     ⚠ (1 image missing alt text)
+Keyword in Alt:       1/4     ✓
+
+Overall Score:        7.5/10
+Priority Fixes:
+1. Add 1-2 more internal links to related content
+2. Add alt text to image in section 3
+```
+
+## Step-by-Step Workflow
+
+### Step 1: Fetch Content
+```
+Use get_content to retrieve the full post HTML.
+Parse headings, links, images, and body text.
+```
+
+### Step 2: Identify Target Keyword
+Either provided by user or extracted from:
+- Post title analysis
+- GSC top query for the URL
+- Content theme analysis
+
+### Step 3: Run All Checks
+Claude analyzes in sequence:
+1. Keyword density and placement
+2. Heading hierarchy and keyword coverage
+3. Internal and external link audit
+4. Image alt text coverage
+5. GSC data cross-reference (if available)
+
+### Step 4: Generate Score Card
+Produce the formatted score card with pass/fail for each criterion.
+
+### Step 5: Prioritize Fixes
+Rank issues by impact:
+1. Missing keyword in title/H1 (highest impact)
+2. Keyword density out of range
+3. No internal links
+4. Missing alt text
+5. Heading hierarchy issues
+6. External link additions
+
+## Best Practices
+
+- Run SEO scoring before publishing (pre-publish checklist)
+- Re-score after content updates to ensure changes did not break optimization
+- Use GSC data to validate keyword targeting against real search behavior
+- Do not sacrifice readability for SEO score — readability comes first
+- Update scoring analysis quarterly as search patterns evolve
+- Track score changes over time to measure optimization impact

package/skills/wp-content-optimization/scripts/content_optimization_inspect.mjs

@@ -0,0 +1,237 @@
+/**
+ * content_optimization_inspect.mjs — Detect content optimization readiness.
+ *
+ * Checks WordPress content volume, content age distribution, SEO plugins,
+ * readability plugins, GSC availability, and WooCommerce presence.
+ *
+ * Usage:
+ *   node content_optimization_inspect.mjs [--cwd=/path/to/project]
+ *
+ * Exit codes:
+ *   0 — content optimization readiness found
+ *   1 — no content optimization readiness found
+ */
+
+import { readFileSync, existsSync, readdirSync } from 'node:fs';
+import { join, resolve } from 'node:path';
+import { argv, stdout, exit } from 'node:process';
+
+// ---------------------------------------------------------------------------
+// Helpers
+// ---------------------------------------------------------------------------
+
+function readFileSafe(filePath) {
+  try { return readFileSync(filePath, 'utf-8'); } catch { return null; }
+}
+
+function existsSafe(filePath) {
+  try { return existsSync(filePath); } catch { return false; }
+}
+
+function globDir(dirPath) {
+  try { return readdirSync(dirPath); } catch { return []; }
+}
+
+// ---------------------------------------------------------------------------
+// Detectors
+// ---------------------------------------------------------------------------
+
+function detectContent(cwd) {
+  const indicators = [];
+
+  // Check wp-content directory exists
+  if (!existsSafe(join(cwd, 'wp-content'))) {
+    return { has_content: false, indicators };
+  }
+
+  indicators.push('wp-content directory exists');
+
+  // Check for uploads (indicator of content)
+  const uploads = globDir(join(cwd, 'wp-content', 'uploads'));
+  if (uploads.length > 0) {
+    indicators.push(`wp-content/uploads contains ${uploads.length} entries`);
+  }
+
+  // Check for themes presence
+  const themes = globDir(join(cwd, 'wp-content', 'themes'));
+  if (themes.length > 0) {
+    indicators.push(`${themes.length} theme(s) installed`);
+  }
+
+  const hasContent = uploads.length > 0 || themes.length > 0;
+  return { has_content: hasContent, indicators };
+}
+
+function detectContentAge(cwd) {
+  const indicators = [];
+  const yearsFound = [];
+
+  const uploadsPath = join(cwd, 'wp-content', 'uploads');
+  if (!existsSafe(uploadsPath)) {
+    return { years_found: yearsFound, indicators };
+  }
+
+  const entries = globDir(uploadsPath);
+  const yearPattern = /^(20\d{2})$/;
+
+  for (const entry of entries) {
+    const match = entry.match(yearPattern);
+    if (match) {
+      yearsFound.push(parseInt(match[1], 10));
+      indicators.push(`upload directory found for year ${match[1]}`);
+    }
+  }
+
+  yearsFound.sort();
+
+  if (yearsFound.length > 1) {
+    indicators.push(`content spans ${yearsFound.length} years (${yearsFound[0]}–${yearsFound[yearsFound.length - 1]})`);
+  }
+
+  return { years_found: yearsFound, indicators };
+}
+
+function detectSeoPlugins(cwd) {
+  const indicators = [];
+  const plugins = globDir(join(cwd, 'wp-content', 'plugins'));
+
+  const seoPlugins = [
+    { dir: 'wordpress-seo', name: 'Yoast SEO' },
+    { dir: 'seo-by-rank-math', name: 'RankMath' },
+    { dir: 'all-in-one-seo-pack', name: 'AIOSEO' },
+  ];
+
+  for (const plugin of plugins) {
+    const lower = plugin.toLowerCase();
+    for (const seo of seoPlugins) {
+      if (lower === seo.dir) {
+        indicators.push(`seo_plugin: ${seo.name} (${plugin})`);
+      }
+    }
+  }
+
+  return { found: indicators.length > 0, indicators };
+}
+
+function detectReadability(cwd) {
+  const indicators = [];
+  const plugins = globDir(join(cwd, 'wp-content', 'plugins'));
+
+  // Yoast and RankMath both include readability analysis
+  const readabilityPlugins = [
+    { dir: 'wordpress-seo', name: 'Yoast SEO (readability analysis)' },
+    { dir: 'seo-by-rank-math', name: 'RankMath (readability analysis)' },
+  ];
+
+  for (const plugin of plugins) {
+    const lower = plugin.toLowerCase();
+    for (const rp of readabilityPlugins) {
+      if (lower === rp.dir) {
+        indicators.push(`readability_plugin: ${rp.name}`);
+      }
+    }
+  }
+
+  return { found: indicators.length > 0, indicators };
+}
+
+function detectGsc() {
+  const indicators = [];
+  let configured = false;
+
+  const raw = process.env.WP_SITES_CONFIG;
+  if (!raw) return { configured, indicators };
+
+  let sites;
+  try { sites = JSON.parse(raw); } catch { return { configured, indicators }; }
+  if (!Array.isArray(sites)) return { configured, indicators };
+
+  for (const site of sites) {
+    const label = site.name || site.url || 'unknown';
+    if (site.gsc_service_account_key) {
+      configured = true;
+      indicators.push(`gsc_service_account_key configured for ${label}`);
+    }
+  }
+
+  return { configured, indicators };
+}
+
+function detectWoocommerce(cwd) {
+  const indicators = [];
+  const plugins = globDir(join(cwd, 'wp-content', 'plugins'));
+
+  for (const plugin of plugins) {
+    if (plugin.toLowerCase() === 'woocommerce') {
+      indicators.push(`woocommerce plugin detected (${plugin})`);
+    }
+  }
+
+  return { found: indicators.length > 0, indicators };
+}
+
+// ---------------------------------------------------------------------------
+// Main
+// ---------------------------------------------------------------------------
+
+function main() {
+  const cwdArg = argv.find(a => a.startsWith('--cwd='));
+  const cwd = cwdArg ? resolve(cwdArg.split('=')[1]) : process.cwd();
+
+  const content = detectContent(cwd);
+  const contentAge = detectContentAge(cwd);
+  const seoPlugins = detectSeoPlugins(cwd);
+  const readability = detectReadability(cwd);
+  const gscAvailable = detectGsc();
+  const woocommerce = detectWoocommerce(cwd);
+
+  const found = content.has_content &&
+                (seoPlugins.found || readability.found || gscAvailable.configured);
+
+  const recommendations = [];
+
+  if (content.has_content) {
+    recommendations.push('Content detected — ready for AI-driven optimization analysis');
+  }
+  if (seoPlugins.found) {
+    recommendations.push('SEO plugin detected — headline and meta description optimization can use plugin data');
+  }
+  if (readability.found) {
+    recommendations.push('Readability analysis available — use wp-content-optimization for Flesch-Kincaid scoring');
+  }
+  if (gscAvailable.configured) {
+    recommendations.push('GSC configured — combine search data with content optimization for data-driven improvements');
+  }
+  if (woocommerce.found) {
+    recommendations.push('WooCommerce detected — prioritize optimization of high-revenue content');
+  }
+  if (contentAge.years_found.length > 1) {
+    recommendations.push('Content spans multiple years — run Content Freshness Audit to identify stale content');
+  }
+  if (!content.has_content && !seoPlugins.found && !readability.found && !gscAvailable.configured) {
+    recommendations.push('No content or optimization tools detected — create content first, then use wp-content-optimization');
+  }
+  if (content.has_content && seoPlugins.found && gscAvailable.configured) {
+    recommendations.push('Full optimization stack ready — use wp-content-optimization for comprehensive content triage');
+  }
+
+  const report = {
+    tool: 'content_optimization_inspect',
+    version: '1.0.0',
+    timestamp: new Date().toISOString(),
+    cwd,
+    found,
+    content,
+    content_age: contentAge,
+    seo_plugins: seoPlugins,
+    readability,
+    gsc_available: gscAvailable,
+    woocommerce,
+    recommendations,
+  };
+
+  stdout.write(JSON.stringify(report, null, 2) + '\n');
+  exit(found ? 0 : 1);
+}
+
+main();

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

@@ -94,3 +94,4 @@ See `references/platform-specs.md`
 - **`wp-content`** — content creation and lifecycle management (source content)
 - **`wp-headless`** — headless content delivery for multi-channel architectures
 - **`wp-woocommerce`** — product content for e-commerce repurposing
+- **wp-social-email** — publish repurposed content to social and email channels

package/skills/wp-monitoring/SKILL.md

@@ -129,3 +129,4 @@ See `references/fleet-monitoring.md`
 - **`wp-security`** — hardening procedures triggered by monitoring alerts
 - **`wp-performance`** — optimization actions based on performance trends
 - **`wp-cicd`** — CI/CD quality gates that complement monitoring (pre-deploy checks)
+- **`wp-search-console`** — add GSC search performance checks to periodic SEO monitoring

package/skills/wp-programmatic-seo/SKILL.md

@@ -95,3 +95,5 @@ The script checks headless frontend presence, SEO plugins, content volume, custo
 - `wp-rest-api` — REST API endpoints for content CRUD
 - `wp-content` — content management fundamentals
 - `wp-content-repurposing` — transform existing content into new formats
+- `wp-search-console` — monitor performance of generated pages via GSC keyword tracking and indexing status
+- `wp-content-optimization` — optimize programmatic page templates for headlines, readability, and SEO scoring