seo-index-validationlisted

Validate whether a DEPLOYED site is being crawled and indexed correctly, and diagnose plus fix why pages are not indexed. Use when a Google Search Console alert email arrives ("New reason preventing your pages from being indexed", "Not found (404)", "Page with redirect", "Discovered / currently not indexed", "Crawled / currently not indexed", "Soft 404"), when checking index health after a deploy, migration, or domain change, when a page will not appear in Google, or to confirm a prior indexing fix actually cleared in Search Console. It probes live HTTP (status codes, redirects, soft-404, canonical tags, sitemap) with curl, reads the GSC report via the browser, fixes at the correct layer (CDN or host setting, _redirects, a 404 page) under confirmation-gating, then schedules a lagged re-check. NOT for keyword research, content optimization, or backlinks. Triggers include "Search Console", "GSC", "not indexed", "404 in Search Console", "page with redirect", "soft 404", "validate indexing", "validate SEO", "why
BryceEWatson/claude-global-skills · ★ 0 · AI & Automation · score 72

Install: claude install-skill BryceEWatson/claude-global-skills

# seo-index-validation Diagnose and fix **crawl and index health** for a *deployed* site, then verify the fix in Google Search Console (GSC). The scope is deliberately narrow: the reasons Google gives for *not indexing* a page (404, redirect, soft-404, duplicate or wrong canonical, discovered-not-indexed) and the live-infrastructure causes behind them. This is **not** a keyword, content, or backlink skill. If asked for those, say so and stop. ## Operating principle - **Reproduce before you believe.** Every diagnosis is grounded in a live HTTP probe or the GSC report, never in memory. Tag each finding *measured*, *derived*, or *assumed*. - **Exact URLs, not buckets.** A GSC alert names a *reason* ("Not found (404)"). The load-bearing output is the *exact affected URL(s)*. Get them. - **Separate benign from real.** Most redirects Google reports are correct canonicalization. Do not "fix" them (see the table below). - **Automate the readable half; browse only where there is no API.** Default to curl and the Search Console API. The browser is only for the three GSC actions that have no API. - **Confirmation-gate live changes.** Toggling a CDN or host setting, or shipping a redirect, is outward-facing. Propose, get an explicit yes, then act. Never unattended. ## What is automatable vs browser-only (verified against official docs) | Step | curl / API? | How | |------|-------------|-----| | Live status, redirects, soft-404, homepage canonical presence, sitemap resolution | yes,