RecipeSearch Console
Watch crawl freshness on pages that change
Crawl freshness monitored against each page's change cadence.
IntentWhether Google re-reads the pages whose content moves.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- News, pricing, inventory pages: anything whose staleness costs money.
Do not use it when
- No specific contraindication beyond the preconditions below.
What it needs first
Required
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Monitor indexation freshness on the watchlist.
Flag pages whose last crawl trails their change cadence.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
A page's crawl age exceeds twice its change cadence
Conclude
Google serves an old version: staleness finding, with both dates.
Evidence every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- Crawl date is not render date for JS-heavy pages: the gap can hide a second staleness.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.