indexing

kostja94/marketing-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/kostja94/marketing-skills --skill indexing
0 commentsdiscussion
summary

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

skill.md

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

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site URL and indexing goals.

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

Crawled - Currently Not Indexed

Cause Action
Low quality, duplicate, off-topic Improve content, fix duplicates, set correct canonical
Static assets (CSS/JS) See below
Feed, share URLs with params Usually OK to ignore; or noindex, canonical to main URL
Important content pages Use URL Inspection, verify canonical/internal links/sitemap, Request indexing

Static Assets (Next.js / Vercel)

Vercel adds unique dpl= params to static assets per deploy, creating many "Crawled - currently not indexed" URLs.

Do Don't
Keep robots.txt allowing /_next/ Do not block /_next/ (breaks CSS/JS loading). See robots-txt
Accept static assets in GSC as expected Do not block /_next/static/css/ or ?dpl=
Use X-Robots-Tag for static assets CSS/JS should not be indexed; no SEO impact

Static assets in "Crawled - currently not indexed" is normal and expected.

Other Issue Types (from GSC Coverage)

Issue Fix
Excluded by «noindex» tag Remove noindex if accidental; keep if intentional
Blocked by robots.txt See robots-txt; remove Disallow for important paths
Redirect / 404 Fix URL or add redirect
Duplicate / Canonical Set correct canonical; usually OK
Soft-404 Page returns 200 but content says "not found" or empty—Google may treat as 404. Fix: return 404 status for truly missing pages; or add real content for 200 pages

Soft-404

A soft-404 occurs when a page returns HTTP 200 but the content indicates the page doesn't exist (e.g. "Page not found" message, empty state). Google may treat it as 404 and exclude from index.

Fix When
Return 404 Page truly doesn't exist; use proper 404 status
Add content Page is intentional (e.g. empty search results); ensure substantive content or use noindex
Redirect If URL moved, use 301 to correct destination

Noindex Usage

  • How: metadata.robots = { index: false } or <meta name="robots" content="noindex"> or X-Robots-Tag
  • Rationale: Not all site content should be indexed; noindex is a valid choice for many pages
  • Caution: Avoid noindex on important content pages
  • With robots.txt: robots.txt = path-level crawl control; noindex = page-level index control. Do not block noindex pages in robots.txt—crawlers must access the page to read the directive. Use both: robots for /admin/, /api/; noindex for /login/, /thank-you/, etc. See robots-txt for when to use which.
  • nofollow ≠ noindex: nofollow controls link equity only; it does not prevent indexing. To exclude from search, use noindex. See page-metadata for meta robots implementation.

Page Types That Typically Need Noindex

Category Page Types Typical Meta Reason
Auth & Account Login, Signup, Password reset, Account dashboard Login: noindex,nofollow; Signup: noindex,follow No search value; login indexed = security risk; signup follow allows crawl of Privacy/Terms links
Admin & Private Admin, Staging, Test pages, Internal tools noindex,nofollow Not for public; avoid discovery
Conversion Endpoints Thank-you, Confirmation, Checkout success, Download gate noindex,follow Post-conversion; no SERP value; allow link equity
System & Utility 404, Internal search results, Faceted/filter URLs noindex,follow or noindex,nofollow Thin/duplicate; 404 = error state
Legal Privacy, Terms, Cookie Policy (optional) Often noindex,follow Low-value indexed; reduces clutter
Duplicate & Thin Printer-friendly, Parameter URLs, Near-duplicate noindex,follow or canonical Duplicate content; canonical preferred when possible
Low-Value Media kit, Feedback board (external), Thin press noindex or index for brand queries Case-by-case

noindex,follow vs noindex,nofollow: Use noindex,follow for most cases—excludes from SERP but allows link equity. Use noindex,nofollow only for login (security), staging, or temporary test pages.

Google Indexing API

Type Typical use
JobPosting Job boards
BroadcastEvent Live platforms

Requirements: Enable Indexing API, create service account, add owner in Search Console, request quota (default 200 URLs/day).

Output Format

Related Skills

  • google-search-console: Find and diagnose indexing issues in GSC
  • robots-txt: Path-level crawl control; when to use robots.txt vs noindex; do not block /_next/ or noindex pages
  • page-metadata: Meta robots implementation; noindex vs nofollow
  • xml-sitemap: Submit and maintain sitemap
  • indexnow: Faster indexing for Bing
  • canonical-tag: Resolve duplicate content
how to use indexing

How to use indexing on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add indexing
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/kostja94/marketing-skills --skill indexing

The skills CLI fetches indexing from GitHub repository kostja94/marketing-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/indexing

Reload or restart Cursor to activate indexing. Access the skill through slash commands (e.g., /indexing) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.641 reviews
  • Ganesh Mohane· Dec 28, 2024

    Keeps context tight: indexing is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • William Srinivasan· Dec 20, 2024

    We added indexing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Camila Shah· Dec 16, 2024

    indexing reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ren Torres· Dec 4, 2024

    Registry listing for indexing matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Tariq Zhang· Nov 23, 2024

    indexing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Sakshi Patil· Nov 19, 2024

    indexing has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Yash Thakker· Nov 19, 2024

    I recommend indexing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Maya Srinivasan· Nov 11, 2024

    indexing reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Zara Diallo· Oct 14, 2024

    We added indexing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Chaitanya Patil· Oct 10, 2024

    Solid pick for teams standardizing on skills: indexing is focused, and the summary matches what you get after install.

showing 1-10 of 41

1 / 5