indexing-audit

indexing-audit is a skill for Claude Code from amirjahfar1/Google-Search-Console-GSC-MCP. It costs 29 tokens per session (382 once invoked), scanned A, a copy of indexing-audit, MIT.

A check of whether a website’s important pages are included in Google’s search index, based on Google Search Console data. It also identifies pages blocked, excluded, or assigned a different main URL by Google.

In plain words
What is it for?
Use it to investigate crawling and indexing issues, check whether pages appear in Google, and create a prioritized list of fixes.
Why use it?
It shows which visible pages may be missing from search and why, instead of leaving indexing problems as unexplained traffic loss.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the google-search-console-gsc-mcp plugin — 12 skills, 1 MCP server shipped together

Good fit Use it to investigate crawling and indexing issues, check whether pages appear in Google, and create a prioritized list of fixes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/amirjahfar1/google-search-console-gsc-mcp/indexing-audit
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 indexing-audit
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.

agentmods badge for indexing-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/amirjahfar1/google-search-console-gsc-mcp/indexing-audit/github.svg)](https://agentmods.dev/skills/amirjahfar1/google-search-console-gsc-mcp/indexing-audit)
Your own site
<a href="https://agentmods.dev/skills/amirjahfar1/google-search-console-gsc-mcp/indexing-audit"><img src="https://agentmods.dev/badge/skills/amirjahfar1/google-search-console-gsc-mcp/indexing-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.

agentmods 80×15 button for indexing-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/amirjahfar1/google-search-console-gsc-mcp/indexing-audit"><img src="https://agentmods.dev/badge/skills/amirjahfar1/google-search-console-gsc-mcp/indexing-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 382 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 86% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.00382
Opus 5 $0.00015 $0.00191
Sonnet 5 $0.00006 $0.00076
Haiku 4.5 $0.00003 $0.00038

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

Security

Grade A, and why

indexing-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.

Origin

This is a copy

86% identical to indexing-audit — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/indexing-audit/SKILL.md · 38 lines

What it actually says

Indexing Audit

Audit the indexing status of the top pages on a site and produce a prioritized action list.

Steps

  1. Call list_properties to confirm the exact site_url.
  2. Call get_search_analytics with dimensions=page, sort_by=impressions, row_limit=20 to identify the 20 most-visible pages.
  3. Extract the list of page URLs from the results.
  4. Call batch_url_inspection with up to 10 URLs at a time (API limit). Run twice if needed to cover all 20 pages.
  5. Categorize each URL by verdict:
    • Indexed (PASS)
    • ⚠️ Soft 404 / Excluded
    • Not indexed / Blocked
    • 🔍 Canonical mismatch (Google chose a different canonical)
  6. For each issue, provide the specific coverageState, pageFetchState, or robotsTxtState from the inspection.

Output format

Present as a prioritized action list:

  1. Critical — Not indexed pages that have impressions (visibility being lost)
  2. High — Canonical mismatches on high-traffic pages
  3. Medium — Robots.txt or fetch blocks
  4. Low — Soft exclusions on low-traffic pages

Include a summary table: page URL | verdict | issue | recommended action.

Run sitemap-health-check alongside this — a submitted-vs-indexed gap at the sitemap level often explains the same indexing issues found here at the page level. For a full cross-referenced report, use 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.

  1. 11d ago First seen · 38 lines · 29 tokens per session scan A 419407712350

Subscribe to this mod's changes

indexing-audit is a skill published in the GitHub repository amirjahfar1/Google-Search-Console-GSC-MCP (0 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 382 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to indexing-audit, differing in 4 lines, and is treated as a copy.

Related

Other skills, from other repositories

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