content-decaylisted
Install: claude install-skill sitetiller/ai-visibility-skills
# Content decay: diagnose before refreshing
Goal: separate pages that really decayed from pages hit by seasonality, tracking gaps, technical faults or a ranking update, then refresh the first group with real changes. Google warns against refreshing for its own sake: changing dates to seem fresh, or adding and removing content mainly to seem fresh, appear in its list of warning signs.
## Inputs
- Two Search Console Pages exports with equal-length windows, for example the last 90 days and the 90 days before. Compare the same weekdays and avoid mixing a holiday period with a normal one. Use the API: `gsc --dims page --out before.csv` (see `gsc-bing`).
- Pages the user owns.
## Steps
1. Export both periods:
```bash
npx sitetiller gsc example.com --start 2026-05-14 --end 2026-08-11 --dims page --out before.csv
npx sitetiller gsc example.com --start 2026-08-12 --end 2026-11-09 --dims page --out after.csv
```
2. Find decaying pages:
```bash
npx sitetiller decay before.csv after.csv --min-clicks 20 --drop 30 --json
```
Output per page: `url`, `clicksBefore`, `clicksAfter`, `impressionsBefore`, `impressionsAfter`, `positionBefore`, `positionAfter`, `change` (fraction, -0.6 is a 60% fall), `reason`, sorted by clicks lost. Defaults: pages with at least 20 clicks before and a fall of at least 30%. These are tool defaults, not Google thresholds; change them to the site's size.
3. Read `reason` as a pointer, not a verdict:
| `reason` | Meaning | First check |