# Inventory submitted sitemaps and their status

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

The sitemap list read with processing dates and per-file verdicts.

**Intent.** What sitemaps exist, when processed, with what result.

## When to use

- Onboarding.
- After sitemap generation changes.

## 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. List sitemaps with statuses. — tools: `gsc_list_sitemaps`
2. Flag stale processing dates against the site's publish cadence.

## Decision rules

- **When** A sitemap has not been processed since well before the last publish wave → **conclude** The pipeline broke upstream of Google: check generation and submission.

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

- Submitted is not fetched, fetched is not indexed: three different verbs, keep them apart.

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