blog-decay

# Blog Decay Use `/blog decay` to find pages whose Google Search Console performance has declined quarter-over-quarter. The command compares a current-period export against a previous-period export, flags pages with a 20% or larger decline by default, and recommends the next content action. ## Default Offline Workflow Run the local analyzer against two GSC page exports: ```bash python3 scripts/content_decay.py current.json previous.json ``` Useful options: ```bash python3 scripts/content_decay.py current.json previous.json --threshold 0.30 python3 scripts/content_decay.py current.json previous.json --metric impressions python3 scripts/content_decay.py current.json previous.json --format markdown --output decay-report.md ``` The script accepts JSON lists of page rows with `page` or `url`, `clicks`, and `impressions`. It also accepts the object shape returned by `blog-google` when the rows are under a top-level `rows` key. ## Optional Live GSC Export For live data, use `/blog google gsc` or the underlying `blog-google` command to create each period export, then run the offline analyzer: ```bash python3 skills/blog-google/scripts/run.py gsc_query --property sc-domain:example.com --dimensions page --start-date YYYY-MM-DD --end-date YYYY-MM-DD --json > gsc-current.json python3 skills/blog-google/scripts/run.py gsc_query --property sc-domain:example.com --dimensions page --start-date YYYY-MM-DD --end-date YYYY-MM-DD --json > gsc-previous.json python3 scripts/content_decay...