What problem does it solve?
Yoast SEO and Readability tasks on WordPress often become slow and error-prone because scoring, score storage (DB + mu-plugin), content repairs, and health monitoring require careful, version-specific handling to avoid score flicker and misleading results.
Core Features & Use Cases
- Score Architecture Control: Understands and safely works with Yoast’s two-layer scoring model (post meta and
wp_yoast_indexable) and the current yoast-rest-meta.php mu-plugin behavior to prevent interfering with Yoast-owned indexables.
- Readability Repair Workflow: Diagnoses 🔴/🟡 readability violations, rewrites only the violated rules, preserves LazyBlocks exactly, validates strict content constraints, publishes via REST, and re-scores.
- Site Health Monitor (Cron): Runs a standalone Linux cron monitor that queries
wp_yoast_indexable via SSH, applies clear OR-based alert logic across SEO and Readability, snapshots results, and posts conditional Discord alerts.
Quick Start
Load the skill and ask your agent to fix a Yoast Readability red post by preserving LazyBlocks, validating the rewritten content, publishing via REST, and re-running scoring.
