Site Architecture
AvdLee/RocketSimApp
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.
High-level technical SEO and site architecture auditor. An agent skill from sickn33/agentic-awesome-skills.
Install Indexing Issue Auditor
$ npx skills add sickn33/agentic-awesome-skills --skill indexing-issue-auditor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills indexing-issue-auditor --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/indexing-issue-auditor .claude/skills/indexing-issue-auditor && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "indexing-issue-auditor" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/indexing-issue-auditor into .claude/skills/indexing-issue-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indexing-issue-auditor", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/indexing-issue-auditorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sickn33/agentic-awesome-skills --skill indexing-issue-auditor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills indexing-issue-auditor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/indexing-issue-auditor .agents/skills/indexing-issue-auditor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "indexing-issue-auditor" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/indexing-issue-auditor into .agents/skills/indexing-issue-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indexing-issue-auditor", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill indexing-issue-auditor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills indexing-issue-auditor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/indexing-issue-auditor .cursor/skills/indexing-issue-auditor && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "indexing-issue-auditor" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/indexing-issue-auditor into .cursor/skills/indexing-issue-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indexing-issue-auditor", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/indexing-issue-auditor--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sickn33/agentic-awesome-skills --skill indexing-issue-auditor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills indexing-issue-auditor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/indexing-issue-auditor .gemini/skills/indexing-issue-auditor && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "indexing-issue-auditor" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/indexing-issue-auditor into .gemini/skills/indexing-issue-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indexing-issue-auditor", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sickn33/agentic-awesome-skills indexing-issue-auditorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sickn33/agentic-awesome-skills --skill indexing-issue-auditor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/indexing-issue-auditor .github/skills/indexing-issue-auditor && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "indexing-issue-auditor" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/indexing-issue-auditor into .github/skills/indexing-issue-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indexing-issue-auditor", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill indexing-issue-auditor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills indexing-issue-auditor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/indexing-issue-auditor .opencode/skills/indexing-issue-auditor && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "indexing-issue-auditor" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/indexing-issue-auditor into .opencode/skills/indexing-issue-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indexing-issue-auditor", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
indexing-issue-auditor- GitHub stars
- 47k
- Used in
- 1 other repo
- Token cost
- ~1.5k tokens
- SKILL.md length
- 735 words
- Files
- 1
- Skills in repo
- 1,497
- Repo updated
- First seen
- Licence
- MIT
At a glance
High-level technical SEO and site architecture auditor. An agent skill from sickn33/agentic-awesome-skills.
- Works in 10 steps: Indexing System Health → Crawl Architecture → Sitemap Architecture Audit → …
- Tasks that involve Technical SEO
- SKILL.md covers Overview, When to Use This Skill, Input Types and How It Works (Mandatory Phases), plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Indexing Issue Auditor is an agent skill from sickn33/agentic-awesome-skills. High-level technical SEO and site architecture auditor. Invoke to scan local or live environments for indexing, crawl budget, and structural errors.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Technical SEO. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
When your agent uses it
- Tasks that involve Technical SEO
Example prompts
- “/indexing-issue-auditor”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Indexing Issue Auditor loads about 1.5k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 735 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 735 words, ~1,503 tokens.
Download SKILL.mdSave it as
.claude/skills/indexing-issue-auditor/SKILL.md (or your agent's skills folder).- name
- indexing-issue-auditor
- description
- High-level technical SEO and site architecture auditor. Invoke to scan local or live environments for indexing, crawl budget, and structural errors.
- category
- growth
- risk
- safe
- source
- self
- source_type
- self
- date_added
- 2026-04-13
- author
- WHOISABHISHEKADHIKARI
- tags
- seo, architecture, indexing, crawler, sitemap
- tools
- claude, cursor, gemini, antigravity
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.
- Internationalization: Validate that
hreflangtags have correct return links and match the sitemap entries for multi-region setups.
Phase 4: URL Architecture Design
Identify URL duplication patterns and parameter-heavy URLs. Propose a "Clean URL Architecture Model."
Phase 5: Redirect & Link Flow
Identify redirect chains and loops. Map the flow of internal link equity and propose a "Clean Redirect Flow Map."
Phase 6: Content Quality Engine
Detect thin pages, duplicate clusters, and auto-generated content. Propose a consolidation plan.
Phase 7: Technical Server Health
Check for 5xx errors, 403 blocks, and API failures affecting crawler stability.
- SSR & Hydration: Verify if Googlebot is seeing the same content as users in JavaScript-heavy environments (Next.js/Nuxt). Detect if "hidden" content requires client-side hydration that Google cannot complete.
Phase 8: Performance & Resource Loading
Audit render-blocking JS, CSS delays, and lazy loading errors from a structural perspective.
Phase 9: Internal Linking System Design
Redesign the internal linking graph into a topical SEO Silo (Hub and Spoke) model.
Show full SKILL.md (286 more words)Show less
Phase 10: Final Rebuild Plan
Produce a step-by-step cleanup order and an SEO stabilization roadmap (Day 1 → Day 30).
Master Issue Control Table
For every audit, you MUST generate a table in this exact format:
| # | Issue | Layer (SEO/Crawl/Server/Content) | Affected URLs/Patterns | Root Cause | Fix (Technical) | Fix (Structural) | Priority | Status |
|---|---|---|---|---|---|---|---|---|
| 1 | Redirect Loop | Server | /blog/old-post | Nested .htaccess rule | Flatten to 1-hop | Redesign routing | High | Open |
Examples
Example 1: Local Directory Audit
Input: Root directory of a static site project.
Scan Result: Detected a robots.txt blocking /public/static but missing an entry for the /api route.
Fix: Added Disallow: /api/* and verified sitemap.xml includes only the /app/ routes.
Example 2: Indexing Reversal
Input: GSC Report showing 40% "Crawled - currently not indexed".
Diagnosis: Architectural duplication (Parameter-based vs. Static URLs).
Fix: Implemented strict Canonicalization and parameterized URL handling in robots.txt.
Best Practices
- ✅ Provide FIX + STRUCTURAL DESIGN: Do not just report; provide the technical fix and the architectural redesign.
- ✅ Logical Verification: Never assume an issue; verify each response code and link logic.
- ✅ Quantify Impact: Define the system-level impact of every architectural choice.
- ❌ No Fluff: Focus on actionable, engineering-level structured output.
Common Pitfalls
- Problem: Treating indexing issues as "content only" when they are often architectural.
- Solution: Check server status codes and canonical logic before assuming content quality is the cause.
- Problem: Ignoring "Crawl Depth" (pages buried too deep for Google to find).
- Solution: Design a flatter hierarchy (max 3 clicks from home).
Limitations
- Live Interaction: Cannot initiate a Google Search Console "Request Indexing" action — instructions only.
- Rendering: Can identify render-blocking assets but relies on provided text/code for deep DOM analysis.
Related Skills
@seo-structure-architect- For detailed header hierarchy and schema markup.@security-auditor- For server-side security and vulnerability checks.@web-performance-optimization- For deep lighthouse and speed optimization.
© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/indexing-issue-auditor of sickn33/agentic-awesome-skills.
Open the folder on GitHubat commit b84d35a
Used in 1 other repository
We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Indexing Issue Auditor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Indexing Issue Auditor this skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Site ArchitectureAvdLee/RocketSimApp | 805 | 11 repos | ~3.3k | Automated safety check: Pass | Custom licence | |
| Hreflang and International SEOAgriciDaniel/claude-seo | 19k | 5 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Google SEO APIsAgriciDaniel/claude-seo | 19k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude | 11k | — | ~2.8k | Automated safety check: Notes | MIT | |
| SEO Ops Structural Checklisttigerless-labs/seo-ops | 700 | — | ~3.3k | Automated safety check: Notes | None |
Similar skills
Hreflang and International SEO
AgriciDaniel/claude-seo
Audits, validates and generates hreflang tags for multi-language and multi-region sites in HTML, HTTP headers or XML sitemaps, flagging common code and return-tag mistakes.
Google SEO APIs
AgriciDaniel/claude-seo
Pulls real Google data for SEO work: Search Console, PageSpeed Insights, CrUX field data, the Indexing API and GA4 organic traffic, through /seo google commands.
GEO-First SEO Audit Tool
zubair-trabzada/geo-seo-claude
Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.
SEO Ops Structural Checklist
tigerless-labs/seo-ops
Checks a site against a deterministic set of structural SEO and GEO checks, either running a crawler-eye report against a URL or reviewing code against the same checklist.
SEO
Bhanunamikaze/Agentic-SEO-Skill
Deterministic LLM-first SEO audits for websites, blog posts, and GitHub repositories.
More from sickn33/agentic-awesome-skills
All 1,497 skills in this repoLiuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
User Thoughts Memory
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
Using LWC Memory and Graphs
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
Find Complementary Founders
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
Whatsapp Cloud API
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
Cline Pilot
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Related
Categories
Questions about Indexing Issue Auditor
What does Indexing Issue Auditor do?
High-level technical SEO and site architecture auditor. An agent skill from sickn33/agentic-awesome-skills. Indexing Issue Auditor is an agent skill from sickn33/agentic-awesome-skills. High-level technical SEO and site architecture auditor.
When should I use Indexing Issue Auditor?
Indexing Issue Auditor fits situations like: tasks that involve Technical SEO.
How do I install Indexing Issue Auditor in Claude Code?
Run `npx skills add sickn33/agentic-awesome-skills --skill indexing-issue-auditor -a claude-code`. Or copy the skill folder (skills/indexing-issue-auditor in sickn33/agentic-awesome-skills) into .claude/skills/indexing-issue-auditor in your project. Claude Code loads it when a task matches its description.
How do I install Indexing Issue Auditor in Codex?
Run `npx skills add sickn33/agentic-awesome-skills --skill indexing-issue-auditor -a codex`. Or copy the skill folder (skills/indexing-issue-auditor in sickn33/agentic-awesome-skills) into .agents/skills/indexing-issue-auditor in your project. Codex loads it when a task matches its description.
Can I use Indexing Issue Auditor in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill indexing-issue-auditor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/indexing-issue-auditor, .gemini/skills/indexing-issue-auditor, .github/skills/indexing-issue-auditor and .opencode/skills/indexing-issue-auditor in your project.
What does Indexing Issue Auditor need to run?
SKILL.md names no scripts, command-line tools or credentials: Indexing Issue Auditor is instructions for the agent only.
Does Indexing Issue Auditor access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Indexing Issue Auditor safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Indexing Issue Auditor use?
Indexing Issue Auditor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Indexing Issue Auditor use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Indexing Issue Auditor?
Skills that share tags, products or a category with Indexing Issue Auditor: Site Architecture (AvdLee/RocketSimApp, 805 stars), Hreflang and International SEO (AgriciDaniel/claude-seo, 19k stars), Google SEO APIs (AgriciDaniel/claude-seo, 19k stars) and GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Indexing Issue Auditor?
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.