RecipeSearch Console
Check sitemap health in one pass
The per-file health read, the fast sibling of the full indexation skill.
IntentErrors, warnings and coverage per sitemap file.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Weekly hygiene.
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.
Run sitemap health.
Rank issues by affected URL count.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Errors concentrate in one file
Conclude
That file's generator is the bug: fix it, not the URLs.
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.
- Sitemap URL counts and index counts never match exactly: gaps are normal, trends are the signal.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.