RecipeSearch Console
Track what entered and left the sitemaps
Sitemap deltas since last read: appeared, vanished, the early warning for generation bugs.
IntentThe site's own publication log, as Google sees it.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Weekly.
- After deploys touching routing.
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.
Track deltas since the last run.
Verify vanished URLs were meant to vanish.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
URLs vanished that nobody deleted
Conclude
Generation regression: the sitemap is lying about the site, fix before Google believes it.
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.
- Legitimate churn (products in and out of stock) needs a baseline: deltas without one cry wolf.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.