# Watch crawl freshness on pages that change

> Tier: recipe. Operating recipe: real tool sequence, core rules, known traps.

Crawl freshness monitored against each page's change cadence.

**Intent.** Whether Google re-reads the pages whose content moves.

## When to use

- News, pricing, inventory pages: anything whose staleness costs money.

## When not to use

- No specific contraindication beyond the preconditions below.

## Sources

Required: Search Console

## Preconditions

- The account is ticked in the dashboard, confirmed via list_accounts.

## Inputs

- `window`: Analysis window. Default: last 30 days.

## Procedure

1. Monitor indexation freshness on the watchlist. — tools: `gsc_monitor_indexation_freshness`
2. Flag pages whose last crawl trails their change cadence.

## Decision rules

- **When** A page's crawl age exceeds twice its change cadence → **conclude** Google serves an old version: staleness finding, with both dates.

## Evidence requirements

- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.

## Human approval boundary

- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.

## Failure modes

- Crawl date is not render date for JS-heavy pages: the gap can hide a second staleness.

## Output

- **Readout**: The figures, with windows and accounts named.
- **Flags**: What deserves a deeper skill or a human decision.

## Related

- Skill: [indexation-health](https://www.getmcpads.com/skills/indexation-health.md)