本文へ移動
cccskills
無料GitHub で公開

seo-gsc-indexing

Identify indexing problems and coverage issues using Google Search Console URL inspection data. Checks up to 20 pages for indexing status, coverage state, robots.txt state, and last crawl date. Use when user says "index issues", "indexing problems", "not indexed", "indexing coverage", or "why is my page not indexed".

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

GSC Index Issues — Indexing Coverage Report

@skills/seo/references/mcp-degradation.md @skills/seo/references/gsc-api-reference.md

Checks indexing status for up to 20 pages using the GSC URL Inspection API. IMPORTANT: inspect_url is rate-limited — this skill caps all calls at 20 to avoid rate-limit hangs. Prioritizes pages most likely to have indexing issues.

MCP Check

Before calling any GSC tool, verify the MCP is connected:

  1. Use ToolSearch with query +google-search-console
  2. If tools returned — note the actual tool name prefix, proceed to Inputs
  3. If no tools returned — display the GSC MCP error template from references/mcp-degradation.md and stop:
## Google Search Console MCP Not Available

The `/seo gsc index-issues` command requires the GSC MCP, which is not currently connected.

**What you can do:**
- Use `/seo technical <url>` for crawlability and indexability analysis (no live data)
- Use `/seo audit <url>` for a full static SEO audit

**To connect GSC MCP:**
- Install and configure a Google Search Console MCP server (see README for setup)
- Add it to ~/.claude/mcp.json at user scope (NOT project scope)
- Verify GSC property access before running commands (domain vs URL prefix format)
- See references/gsc-api-reference.md for property format details

Inputs

  • site: The GSC property URL. Accept both formats:
    • Domain property: sc-domain:example.com
    • URL prefix: https://example.com or https://www.example.com
    • If user provides a bare domain (no prefix), call list_sites to identify the correct property format registered in GSC.
  • urls (optional): Specific URLs the user wants to inspect. If provided, inspect these directly (still capped at 20 total calls).

Date Calculation

Use Bash to calculate dates for the initial search analytics query:

endDate=$(date -v-3d +%Y-%m-%d)
startDate=$(date -v-31d +%Y-%m-%d)
echo "endDate: $endDate | startDate: $startDate"

Execution

RATE LIMIT RULE: Never call inspect_url more than 20 times in a single run.

Path A — User provided specific URLs

If the user provides specific URLs to inspect:

  1. Accept up to 20 URLs (if user provides more, inspect first 20, note the cap)
  2. For each URL, call inspect_url:
    • siteUrl: the site property
    • inspectionUrl: the specific URL
  3. Collect all results, proceed to Output

Path B — No specific URLs (general scan)

  1. Get pages GSC knows about: Call query_search_analytics with:

    • siteUrl: the site property
    • startDate: calculated startDate
    • endDate: calculated endDate
    • dimensions: ["page"]
    • rowLimit: 100
  2. Select pages to inspect (cap at 20): Strategy — prioritize pages most likely to have indexing issues:

    • Sort pages by impressions ascending (low impressions = potential indexing issues)
    • Take the bottom 20 pages by impressions
    • These are the pages GSC sees but that get little visibility
  3. Inspect each selected page: For each of the up to 20 selected pages, call inspect_url:

    • siteUrl: the site property
    • inspectionUrl: the page URL

    Stop after 20 calls regardless of remaining pages.

Post-processing: Group results by coverage state:

  • Indexed (coverageState contains "Indexed" or indexingState = "INDEXED")
  • Excluded (coverageState contains "Excluded", "Blocked", "Noindex", "Redirect")
  • Error (coverageState contains "Error", "Not found")

Output Format

## GSC Index Issues: [site property]
**Pages inspected:** [count] of [total pages in GSC]
**Rate limit cap:** 20 inspect_url calls maximum per run

### Indexing Status Summary
| Coverage State | Count |
|----------------|-------|
| Indexed | [n] |
| Excluded | [n] |
| Error | [n] |

### Indexed Pages
| URL | Indexing State | Last Crawl Date |
|-----|----------------|-----------------|
| [url] | [state] | [date] |

### Excluded Pages
| URL | Coverage State | Robots.txt State | Last Crawl Date |
|-----|----------------|------------------|-----------------|
| [url] | [state] | [state] | [date] |

### Error Pages
| URL | Coverage State | Page Fetch State | Last Crawl Date |
|-----|----------------|------------------|-----------------|
| [url] | [state] | [state] | [date] |

### Recommendations
- [For each excluded/error page: specific action based on coverage state]

Recommendation logic by coverage state:

  • "Blocked by robots.txt": Check robots.txt is not accidentally blocking this URL
  • "Excluded by 'noindex' tag": Remove noindex meta tag if page should be indexed
  • "Redirect": Verify the redirect target is indexed
  • "Crawl anomaly" or fetch error: Check server response codes, page may be returning 5xx
  • "Duplicate without user-selected canonical": Add canonical tag pointing to preferred URL
  • "Not found (404)": Fix broken URL or add redirect from old URL

Note if cap reached: "Showing [20] of [total] pages. Run again with specific URLs to inspect additional pages."

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

seo

無料

Comprehensive SEO analysis for any website or business type. Orchestrates 52 sub-skills (52 active): full site audits, technical SEO (CWV/INP), schema, E-E-A-T content quality, images, sitemaps, GEO for AI Overviews, llms.txt generation, AI crawler audit, plus live GSC and Ahrefs MCP data. GSC: overview, drops, opportunities, brand-vs-nonbrand, cannibalization, compare, content-decay, index-issues, new-keywords. Ahrefs: overview, backlinks, keywords, competitors, content-gap, broken-links, new-links, anchor-analysis, dr-history, top-pages. Cross-MCP: serp, content-brief, brand-radar, site-audit-pro, report. Local: log-analysis, ai-content-check, internal-links, local, migration-check, obsidian-kb. AI Readability: llms-txt, robots-ai. Performance: lighthouse-audit, core-web-vitals, page-experience. Quality & AI Search: rich-results, ai-optimization, eeat-audit, helpful-content. Triggers on: "SEO", "audit", "schema", "Core Web Vitals", "sitemap", "E-E-A-T", "AI Overviews", "GEO", "technical SEO", "content quality", "structured data", "GSC", "Ahrefs", "backlinks", "keywords", "search console", "domain rating", "local SEO", "migration", "lighthouse", "pagespeed", "LCP", "INP", "CLS", "page experience", "interstitials", "mobile friendly", "rich results", "rich snippets", "schema eligibility", "AI optimization", "AI search readiness", "EEAT", "trust signals", "helpful content", "people-first", "content quality gate".

日本語の概要は準備中です。原文の説明を表示しています。

lionkiii/claude-seo-skills212026年6月11日 更新

Analyze a domain's anchor text distribution from Ahrefs: see the breakdown of anchor text used across all backlinks and assess link profile health. Use when user says "anchor text", "anchor analysis", "anchor distribution", "link anchors", or "anchor text profile".

日本語の概要は準備中です。原文の説明を表示しています。

lionkiii/claude-seo-skills212026年6月11日 更新

Analyze a domain's backlink profile using Ahrefs: see who links to the domain, source Domain Rating, anchor text, link type, and when each link was first seen. Use when user says "Ahrefs backlinks", "backlink profile", "who links to", "link analysis", or "referring pages".

日本語の概要は準備中です。原文の説明を表示しています。

lionkiii/claude-seo-skills212026年6月11日 更新

Find broken backlinks pointing to a domain using Ahrefs: links targeting 404 pages that can be reclaimed. Prioritizes highest-DR lost links for maximum recovery impact. Use when user says "broken backlinks", "broken links", "link reclamation", "dead backlinks", or "404 backlinks".

日本語の概要は準備中です。原文の説明を表示しています。

lionkiii/claude-seo-skills212026年6月11日 更新

Discover a domain's top organic competitors from Ahrefs: competing domains, keyword overlap count, shared keywords, and unique competitor keywords. Use when user says "Ahrefs competitors", "organic competitors", "competing domains", "keyword overlap", or "who competes with".

日本語の概要は準備中です。原文の説明を表示しています。

lionkiii/claude-seo-skills212026年6月11日 更新

Find keywords that competitors rank for but the target domain does not, using Ahrefs data. Reveals content opportunities and topic gaps. Use when user says "content gap", "keywords competitors rank for", "missing keywords", "competitor keywords", or "content gap analysis".

日本語の概要は準備中です。原文の説明を表示しています。

lionkiii/claude-seo-skills212026年6月11日 更新

lionkiii のスキルをすべて見る

このスキルの問題を報告する