Borrowing it
Nothing to install: this file belongs to FlorianBruniaux/google-search-console-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/FlorianBruniaux/google-search-console-mcp/main/.claude/skills/sitemap-audit/SKILL.mdgit clone --depth 1 https://github.com/FlorianBruniaux/google-search-console-mcpWrote 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.
[](https://agentmods.dev/skills/florianbruniaux/google-search-console-mcp/sitemap-audit)<a href="https://agentmods.dev/skills/florianbruniaux/google-search-console-mcp/sitemap-audit"><img src="https://agentmods.dev/badge/skills/florianbruniaux/google-search-console-mcp/sitemap-audit/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.
<a href="https://agentmods.dev/skills/florianbruniaux/google-search-console-mcp/sitemap-audit"><img src="https://agentmods.dev/badge/skills/florianbruniaux/google-search-console-mcp/sitemap-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00087 | $0.00355 |
| Opus 5 | $0.00044 | $0.00178 |
| Sonnet 5 | $0.00017 | $0.00071 |
| Haiku 4.5 | $0.00009 | $0.00036 |
Grade A, and why
sitemap-audit 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.
What it actually says
Sitemap Audit
Audit all submitted sitemaps for a property and identify coverage gaps and errors.
Steps
- Call
list_propertiesto confirm the exactsite_url. - Call
list_sitemapsto get all submitted sitemaps with their last download date, submitted URL count, and indexed URL count. - Call
sitemap_auditfor a detailed health report on each sitemap. - Call
check_indexing_issuesto compare sitemap submissions against actual indexed page counts across the property. - Flag any sitemap where the gap between submitted and indexed exceeds 20% as a priority issue.
Output format
Sitemap inventory table: Sitemap URL | Type | Submitted | Indexed | Gap % | Last downloaded | Status
Issues list sorted by severity:
- Critical: sitemaps returning 404, parse errors, or not loading
- High: submitted/indexed ratio below 80%
- Medium: last downloaded more than 7 days ago (Google not re-fetching)
- Low: sitemaps with low coverage but low traffic impact
Recommendations: for each issue, one concrete action (re-submit, fix the URL, split the sitemap into smaller files, remove orphan URLs).
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 · 33 lines · 87 tokens per session scan A 740b1f064c9f
sitemap-audit is a skill published in the GitHub repository FlorianBruniaux/google-search-console-mcp (10 stars, last pushed 10d ago), licensed MIT. It adds 87 tokens to every session and 355 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
using-mac
Use when invoking mac-device MCP tools to drive a Mac test machine (agent-fleet project) -- screenshot-and-click UI testing, long-running shell or zsh commands, file or process operations, AppleScript automation, or coordinating exclusive device use across multiple agents.
using-win
Use when invoking win-device MCP tools to drive a Windows test machine (agent-fleet project) -- screenshot-and-click UI testing, long-running shell commands, file or process operations, or coordinating exclusive device use across multiple agents.
gsccli
Use when the user wants to query Google Search Console search analytics (clicks/impressions/CTR/position by query/page/country/device), inspect URL indexing status, manage sitemaps, or send Indexing API notifications via the gsccli shell command. Triggers on GSC, Search Console, sitemap, indexing API, mobile…
zotero-keeper-harness
Cline harness for Zotero Keeper and the bundled VS Code extension. Triggers: zotero keeper, zotero mcp, full check, release checklist, workflow, vsix, Cline.
web-analytics
Analyze web traffic, SEO performance, and search engine trends using Google Search Console, Google Analytics 4, and Bing Webmaster Tools. Use when the user asks to analyze traffic, check SEO, or find keyword opportunities.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.