Indexing

Handles the messy indexing problems you see in Search Console: "Crawled - currently not indexed," soft 404s, noindex accidents, and those endless Vercel static asset warnings. Breaks down when to use noindex versus robots.txt (spoiler: don't block pages you're trying to noindex), gives you the page removal decision tree so you stop 404-ing pages that should redirect, and includes the noindex cheat sheet for login pages, thank-you pages, and all the utility cruft cluttering your Coverage report. Also covers Google Indexing API setup if you're running a job board. The static assets table alone will save you from panicking about Next.js deploy parameters.

skills.sh installs: 1.3K
GitHub stars: 1.1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add kostja94/marketing-skills --skill indexing --agent claude-code

Installs into .claude/skills of the current project.

Files

SEO Technical: Indexing

Guides indexing troubleshooting and fix actions. For how to find and diagnose issues in GSC, see google-search-console.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Scope (Technical SEO)

Fix actions: noindex, canonical, content quality, URL Inspection; verify robots.txt does not block (see robots-txt)
Noindex: Page-level index control; which pages to exclude and how. Complements robots-txt (path-level crawl control) and google-search-console (Coverage diagnosis)

Initial Assessment

Project context: Read root {project}.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.

Identify issue from GSC (see google-search-console for Coverage report, issue types, diagnosis workflow). Then apply fix below.