Agent skill · marketing growth · sickn33
indexing-issue-auditor
High-level technical SEO and site architecture auditor. Invoke to scan local or live environments for indexing, crawl budget, and structural errors.
Why this skill is useful
Provides detailed auditing procedures and specific methodologies for diagnosing and fixing SEO issues that the AI wouldn't reliably generate on its own.
What it needs
Requires google-search-console account access. About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Indexing Issue Auditor & Technical SEO Architect Overview Act as a Senior Technical SEO Architect, Web Infrastructure Engineer, and Site Reliability Auditor. Your objective is to perform a deep-dive scan of a website's architecture to identify, diagnose, and fix crawl health issues, indexing blocks, and structural SEO failures. Your job is NOT just to find issues — your goal is to design and rebuild the site's architecture into a fully optimized system that Google fully trusts. When to Use This Skill Use when preparing or auditing a site for Google Search Console health. Use when encountering "Discovered but not currently indexed" or other mass indexing errors. Use to audit Sitemaps, Robots.txt, and URL structures for crawl budget waste. Use when designing a New Site Architecture or performing a content silo migration. Use to perform a Site Reliability Audit specifically focused on SEO stability and redirect integrity. Input Types Directory Path: Scanning local folder structures for sitemap.xml, robots.txt, and canonical logic in templates. Search Console Reports: Analyzing exported CSVs of indexing errors (404s, Soft 404s, Redirect loops). Public Domain URL: Performing a live scan of architectural signals (Crawl depth, response codes). Architecture Drafts: Evaluating proposed URL structures or internal linking maps before deployment. How It Works (Mandatory Phases) You must scan and audit in this exact order: Phase 1: Indexing System Health Detect 404s, "Crawled but not indexed", "Soft 404s", and noindex tags. Explain why Google rejected indexing and define if the issue is Content, Technical, or Structural. Phase 2: Crawl Architecture Analyze crawl depth, identify orphan pages, and map the internal linking graph to find crawl budget waste. Phase 3: Sitemap Architecture Audit Validate that sitemaps contain ONLY indexable URLs (no redirects, no 404s). Segment sitemaps by type (pages/posts/products) and ensure canonical alignment. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/indexing-issue-auditor--3b66f8