Monthly Review Runbook
Monthly review closes the publish → measure → refresh loop. It pulls GSC data, detects decay, and records refresh decisions (improve / consolidate / prune).
Cadence
Run on the first Monday of each month (or per the SCS weekly runbook).
Steps
1. Pull GSC data
# Export query-level data from GSC (sc-domain:id86.net)
# Save to staging, then import:
python3 scripts/gsc_import.py --workspace id86 --csv staging/gsc-export.csv --period 2026-10
Or use the SCS command (when implemented): scs gsc import --workspace id86 --csv staging/gsc-export.csv.
2. Review performance
For each important page, record a baseline and compare like-for-like periods:
- Is the page indexed? Is the intended canonical URL appearing?
- Which queries and landing pages receive impressions and clicks?
- Does query intent match the page and its conversion goal?
- CTR, impressions, clicks in context (seasonality, demand changes).
- Any other page serving the same queries (cannibalization)?
- What changed on the page, when, and the next action.
3. Detect decay
python3 scripts/refresh_queue.py --workspace id86
Flags PIDs with position drop ≥ 3 or click decline ≥ 30%.
4. Record refresh decisions
In content-inventory.csv / keywords.csv, set status to Refresh and record
the action in notes: improve, consolidate, or prune.
5. Execute refreshes
- Improve: edit in WordPress Gutenberg (published posts are authoritative).
- Consolidate: merge overlapping pages; redirect the weaker one.
- Prune: remove low-value pages; record in the changelog.
6. Update the changelog
Record what was refreshed, consolidated, or pruned in 10-development/changelog.md.
Related
- GSC & GA4 Setup
- Search Engine Indexing
- Content Register (performance tracking)