compare

# /claude-seo-ai:compare Four comparisons, one script. **Read-only**: everything is written under `${CLAUDE_PLUGIN_DATA}/runs` (comparisons land in `<root>/compare/<a>__<b>/compare.json`), never in the user's project. `$ARGUMENTS` decides the shape: | The user gave you | Run | | --- | --- | | two URLs / run refs | `compare.mjs <refA> <refB>` — same host is a **baseline**, a staging-looking host is **staging**, two sites are **competitor** | | three to five refs | `compare.mjs <refA> <refB> <refC> …` — competitor matrix (max 5) | | "since my last audit" | `compare.mjs --baseline latest --against <url\|run>` | | staging vs production | `compare.mjs --prod <ref> --staging <ref>` (add `--map staging.example.com=example.com` when the hosts do not look related) | | "what do the pages ranking for X have that I don't" | the content-gap flow below | A `<ref>` is a run directory, a `report.json`, `latest[:<host>]`, `baseline[:<host>]`, or a URL. ## Flow A — baseline, staging, competitor 1. **Get a run for every side.** A ref that is already a run (`latest`, `latest:example.com`, a path) needs nothing. For a URL with no run, audit it first so the user sees the acquisition and can ask for more pages: `node "${CLAUDE_PLUGIN_ROOT}/scripts/audit.mjs" <url> --pages 3 --checks deterministic --render static --out "${CLAUDE_PLUGIN_DATA}/runs"` (If you skip this, `compare.mjs` audits the URL itself with exactly those settings.) 2. **Compare:** `node "${CLAUDE_PLUGIN_ROOT}/scripts/...