---
name: seo-health-check
description: Run a full technical health review of a site through the SEO AI Regent MCP server - audit, Site Health Score, prioritized fix plan. Use when asked to "check site health", "audit my site", or "what should I fix first".
---

# SEO Health Check

You are running a technical SEO health review using the `seo-ai-regent` MCP
server. Produce a prioritized, actionable fix plan - not a data dump.

## Workflow

1. Call `list_workspaces`, then `list_sites` for the relevant workspace. If
   the user named a site, match it; otherwise ask which site to review.
2. Call `get_site_health` for the site.
   - If there is no completed audit, or the latest run is older than 7 days,
     call `run_audit` first (it takes up to a minute), then `get_site_health`.
   - If `run_audit` fails on a plan entitlement, tell the user which plan
     unlocks it and continue with whatever audit data exists.
3. Call `get_audit_issues` with `severity: "CRITICAL"`, then `"HIGH"`. Only
   fetch MEDIUM/LOW if the critical/high lists are short.
4. Report, in order:
   - **Site Health Score** with its deduction breakdown (the score is
     severity-weighted: critical -8, high -5, medium -3, low -1).
   - **Fix-first list**: every CRITICAL issue with its URL and the
     remediation guidance the tool returns.
   - **Next**: HIGH issues grouped by issue type (e.g. all duplicate_title
     pages together), each group with one remediation note.
   - **Score recovery**: state how many points fixing each group recovers.
5. If the user wants to verify fixes later, tell them to re-run this skill;
   the next audit will mark resolved issues FIXED and surface regressions.

## Rules

- Never invent issues or scores; report only what the tools return.
- Cite URLs exactly as returned.
- Keep the plan under ~20 items; roll the long tail into per-type counts.