What is sitemap-health-check?

A check of the sitemaps submitted to Google for a website. It looks for errors, warnings, stale downloads, processing delays, and differences between submitted and indexed pages.

Use it to investigate sitemap errors, check whether Google is fetching sitemaps, and find content types with large indexing gaps.

It can reveal problems that a sitemap’s basic status may not show, including pages submitted successfully but not actually indexed by Google.

sitemap-health-check — Skill for Claude Code by amirjahfar1

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add amirjahfar1/Google-Search-Console-GSC-MCP --skill sitemap-health-check

Clone the repo

git clone --depth 1 https://github.com/amirjahfar1/Google-Search-Console-GSC-MCP

Made for: Claude Code.

Or install google-search-console-gsc-mcp, the plugin that ships this one along with the rest of its 12 skills, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/amirjahfar1/google-search-console-gsc-mcp/sitemap-health-check/github.svg)](https://agentmods.dev/skills/amirjahfar1/google-search-console-gsc-mcp/sitemap-health-check)

Your own site

<a href="https://agentmods.dev/skills/amirjahfar1/google-search-console-gsc-mcp/sitemap-health-check"><img src="https://agentmods.dev/badge/skills/amirjahfar1/google-search-console-gsc-mcp/sitemap-health-check/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/amirjahfar1/google-search-console-gsc-mcp/sitemap-health-check"><img src="https://agentmods.dev/badge/skills/amirjahfar1/google-search-console-gsc-mcp/sitemap-health-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 544 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00047	$0.00544
Opus 5	$0.00023	$0.00272
Sonnet 5	$0.00009	$0.00109
Haiku 4.5	$0.00005	$0.00054

Measured 11d ago against content hash 9818ab687ca6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

sitemap-health-check scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/sitemap-health-check/SKILL.md · 35 lines

What it actually says

Sitemap Health Check

Go beyond "list sitemaps" — flag stale, erroring, or pending sitemaps, and check whether the URLs inside them are actually getting indexed, not just submitted.

Steps

Call list_properties to confirm the exact site_url.
Call list_sitemaps_enhanced to get all sitemaps with errors, warnings, is_pending, last_downloaded, url_count.
Flag issues:
- Errors > 0 — critical, needs immediate attention
- Warnings > 0 — review needed
- is_pending = true for more than a few days — Google hasn't processed it yet
- last_downloaded more than 30 days ago, or null — Google may have stopped fetching it
If any sitemap is a sitemap index, call list_sitemaps_enhanced again with sitemap_index=<that sitemap's path> to expand and check the child sitemaps too.
For each non-erroring sitemap, call get_sitemap_details with its exact path — this returns a content_breakdown with submitted vs indexed counts per content type. If indexed is meaningfully lower than submitted (e.g. under 80%), that's a direct indexing gap even though the sitemap itself reports no errors.
For the sitemap(s) with the worst submitted-vs-indexed gap, pull a sample of pages from get_search_analytics (dimensions=page) filtered to that sitemap's URL path, and run batch_url_inspection on up to 10 of them to get the specific per-URL verdict behind the gap.

Output format

Table: Sitemap | Type | Status | Errors | Warnings | Submitted | Indexed | Indexed % | Last Downloaded
Critical issues list (errors, long-pending sitemaps, large submitted-vs-indexed gaps)
Sample per-URL inspection results for the worst-gap sitemap
Recommendation per issue (resubmit, fix XML, remove stale/dead entries, investigate specific URLs)

A large submitted-vs-indexed gap is often the same root cause surfaced by indexing-audit — run both together on a full audit via full-seo-audit.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 35 lines · 47 tokens per session scan A 9818ab687ca6

Subscribe to this mod's changes

sitemap-health-check is a skill published in the GitHub repository amirjahfar1/Google-Search-Console-GSC-MCP (0 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 544 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.

Marketing and SEO

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens