# Check sitemap health in one pass

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

The per-file health read, the fast sibling of the full indexation skill.

**Intent.** Errors, warnings and coverage per sitemap file.

## When to use

- Weekly hygiene.

## 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. Run sitemap health. — tools: `gsc_get_sitemap_health`
2. Rank issues by affected URL count.

## Decision rules

- **When** Errors concentrate in one file → **conclude** That file's generator is the bug: fix it, not the URLs.

## 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

- Sitemap URL counts and index counts never match exactly: gaps are normal, trends are the signal.

## 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)
