indexing-health

Installation
SKILL.md

Indexing Health Check

Diagnose why pages are missing from Google's (and optionally Bing's) index and produce an issue summary grouped by cause, with affected URL counts and concrete fixes. The user's request may contain a property name and/or a focus hint (for example a URL path or "check my blog section"); use it to skip resolution steps or narrow the suspect set.

Workflow

  1. Resolve the property. If the user (or the request) named a property, use it; site URLs use GSC formats like sc-domain:example.com or https://www.example.com/. Otherwise call list_sites and pick the obvious match. If several plausible matches exist, ask the user which one before continuing.

  2. Tracked-URL status. Call get_indexing_tracker for the tracker config and status summary. If URLs are being tracked, also call get_indexing_tracker_report for the indexing health score, coverage, crawl freshness, and lost / newly-indexed URLs; the lost list is your primary suspect pool. Use list_tracked_urls with a status filter when you need the concrete non-indexed URLs. If the tracker is not set up, say so briefly and continue; the sitemap and inspection steps still work.

  3. Sitemap coverage. Call list_sitemaps and check for errors, warnings, and stale last-download dates. For the main sitemap (or the one matching the user's focus), call get_sitemap_performance to join sitemap URLs with GSC metrics over the default range (last 28 days compared with the previous period, unless the user specifies otherwise). URLs present in the sitemap but with zero impressions across the range are indexing suspects. Remember GSC data lags about 2 to 3 days: never treat the most recent 2 days as complete, and say so if a dip is visible at the edge of the range. ctr values are already percentages on a 0-100 scale; never multiply them by 100. Position: lower is better.

  4. Check inspection quota BEFORE inspecting anything. Call get_inspection_quota and report the remaining daily quota for this property. Plan the inspection batch so it uses well under half of what remains; never spend the whole quota in this workflow. If the quota is exhausted or nearly so, skip step 5, rely on step 6 instead, and tell the user the quota is a daily per-property limit (2,000 inspections per day) that resets each day, so they can rerun this check tomorrow.

Installs
3
First Seen
Oct 12, 2026