seo-index-validation

Diagnose crawl and index health issues for deployed websites via HTTP probes and GSC reports.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/BryceEWatson/claude-global-skills --skill seo-index-validation
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: seo-index-validation
Source: https://github.com/BryceEWatson/claude-global-skills/tree/main/seo-index-validation
Command: npx skills add https://github.com/BryceEWatson/claude-global-skills --skill seo-index-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill requires curl, and includes scripts (resource) components.

What problem does it solve?

Diagnoses crawl and index health for deployed websites and identifies why pages are not indexed.

Core Features & Use Cases

  • Detects issues pushing pages out of Google index via live HTTP probes (status codes, redirects, canonical tags, sitemap checks) and Google Search Console (GSC) reports.
  • Guides confirmation-gated fixes at the correct layer (CDN/host, redirects, 404 pages) and schedules lagged re-checks to verify results.
  • Supports end-to-end workflows from issue detection to validation, including per-URL checks and recrawl nudges.

Quick Start

Run the headless probe against your domain by executing scripts/crawl-check.sh <domain> and review the PASS/WARN/FAIL output.

Frequently Asked Questions about seo-index-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose why my pages are not indexed in Google Search Console?โ–ผ

Identify indexing issues by running live HTTP probes with curl to check status codes, redirects, and canonical tags, then analyzing Google Search Console reports. This produces a structured PASS/WARN/FAIL summary and a confirmation-gated remediation plan.

How do I check crawl health for my website after a deployment or migration?โ–ผ

Validate post-deployment index health by executing a curl-based crawl check against your live domain to detect redirect and canonical tag issues. This outputs a PASS/WARN/FAIL summary and guides confirmation-gated fixes at the correct host layer.

Do I need a Google Search Console access token to run a crawl check?โ–ผ

A Google Search Console access token is optional; live crawl checks only require curl to probe HTTP status codes and redirects. Provide a GSC_ACCESS_TOKEN only when you need to query sitemap data directly during the index validation process.

What is the best way to fix site indexing problems detected via curl probes?โ–ผ

Fix indexing problems by following the structured remediation plan to apply confirmation-gated fixes at the correct CDN, host, or redirect layer. The workflow schedules lagged re-checks to validate that your unindexed pages successfully re-enter the crawl queue.

Can I use curl to read Google Search Console reports for site audits?โ–ผ

Use curl for live HTTP probes during site audits to detect status code and redirect anomalies, optionally pairing it with a GSC_ACCESS_TOKEN to read Google Search Console reports. This pinpoints exactly why specific URLs are not indexed.

Why does my site indexing validation fail after checking sitemaps?โ–ผ

Indexing validation fails when curl probes detect live HTTP errors, improper redirects, or canonical tag conflicts that block crawl access. The script outputs a FAIL status and a targeted remediation plan to resolve these specific sitemap and host issues.