seo-monitor

Skill: SEO Monitor — Periodic Delta Tracking

All responses and reports are produced in English by default. Switch to the user's language if they explicitly request it.

---

Overview

This skill is Step 4 in the SEO-GEO pipeline. It re-crawls a previously audited site, compares the current state against the original baseline, and produces a delta report highlighting what improved, what regressed, and what needs attention.

Position in the pipeline

[seo-collector] → site-data.json ──────────────────────┐
                       ↓                                │
[seo-geo-audit] → audit-report.md + audit-actions.json  │
                       ↓                                │
[seo-implementer] → fixes/                              │
                       ↓                                │
             ┌─────────────────────────┐                │
             │   SEO MONITOR (this)    │ ←──────────────┘
             └─────────────────────────┘    (re-uses collector)
                       ↓
              monitoring/
              ├── baseline.json
              ├── delta-[date].md
              └── alerts.md
                       ↓
              ↻ loops back to collector for next cycle

What it produces

seo-project-[domain]/
└── monitoring/
    ├── baseline.json           ← Snapshot from the first audit (created once)
    ├── scan-[date].json        ← Each new crawl result
    ├── delta-[date].md         ← Comparison report (human-readable)
    ├── delta-[date].json       ← Comparison data (machine-readable)
    ├── alerts.md               ← Active alerts (updated each scan)
    └── history.md              ← Score evolution over time

---

Step 0: Determine monitoring mode

First run (no baseline exists)

If no monitoring/baseline.json exists in the project folder:

1. Check if site-data.json and audit-actions.json exist from a previous audit
2. If yes → convert them into the baseline:
   • Copy site-data.json → monitoring/baseline.json (add baseline_date field)
   • Extract scores from audit-actions.json → store in baseline
3. If no → ask the user:

   No previous audit found for this domain.
   Would you like me to:
     1. Run a full audit first (collector + audit) to establish the baseline
     2. Run a quick scan now and use it as the baseline