mcpbeat Sign in

Gsc Assistant Skill for Claude

Google Search Console indexing assistant. Use when the user wants to track page indexing status, compare sitemap against GSC indexed pages, manage submission tracking, or move false positives (pages indexed per URL Inspection but not yet in GSC export) to the indexed list. Maintains two tracking files (indexed.md, to-index.md) with prioritization support.

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
275
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/nicepkg/ai-workflow --skill gsc-assistant

The instruction itself

23 sections, as written by the author

GSC Assistant Skill

Purpose

This skill helps manage Google Search Console indexing status by maintaining two markdown tracking files:

  • indexed.md - All indexed pages in two tables:
  • "Indexed Public" - URLs confirmed in GSC export data
  • "Indexed With Lag" - URLs confirmed via URL Inspection (not yet in export)
  • to-index.md - Pages awaiting indexing:
  • Difference between sitemap and total indexed URLs
  • Prioritized by categories (configurable)
  • Tracks submission dates

When to Use This Skill

  • User asks about "indexing status" or "GSC indexing"
  • User wants to "compare sitemap with indexed pages"
  • User mentions "URL inspection" or "false positives"
  • User needs to "track submissions" or "indexing progress"
  • User asks to "move indexed pages" or "update indexing status"
  • User wants to "generate indexing report"

Key Concepts

GSC Data Lag

Google Search Console export data has approximately 2 weeks lag. Pages that show as indexed in URL Inspection may not appear in the export yet. These are tracked separately as "Indexed With Lag".

False Positives

When checking to-index pages via URL Inspection:

  • If indexed: Mark as "false positive - indexed" in Submitted column
  • Pre-processing moves these to indexed.md (Indexed With Lag table)
  • The "Detected" date is inferred from when the entry was added to to-index

Priority Categories

to-index.md organizes pages by priority:

  • Priority 1: High-value content series
  • Priority 2: Recent content (current/previous year)
  • Priority 3: Specific content collections
  • Lower priorities: Archive pages, pagination, etc.

File Schemas

indexed.md

# Indexed Pages

## Indexed Public (GSC Export)

*Last updated: YYYY-MM-DD*
*Source: gsc-export.csv*

| # | URL | Last Crawled |
|---|-----|--------------|
| 1 | https://example.com/page-1/ | 2025-12-01 |
| 2 | https://example.com/page-2/ | 2025-12-02 |

## Indexed With Lag (URL Inspection Confirmed)

*Pages confirmed indexed via URL Inspection but not yet in GSC export*

| # | URL | Detected | Confirmed |
|---|-----|----------|-----------|
| 1 | https://example.com/new-page/ | 12 Dec 2025 | 12 Dec 2025 |

to-index.md

# Pages To Index

*Generated: YYYY-MM-DD*
*Total: X pages*

## Priority 1: [Category Name]

| # | URL | Submitted |
|---|-----|-----------|
| 1 | https://example.com/important-page/ | 12 Dec |
| 2 | https://example.com/another-page/ | - |

## Priority 2: [Category Name]

| # | URL | Submitted |
|---|-----|-----------|
| 1 | https://example.com/recent-post/ | - |

Workflow

Initial Setup

  • Import GSC export CSV to create indexed.md (Indexed Public table)
  • Extract sitemap URLs
  • Calculate difference (sitemap - indexed = to-index)
  • Categorize to-index pages by priority
  • Generate to-index.md

Regular Updates

  • Pre-processing: Scan to-index.md for "false positive - indexed" entries
  • Move false positives to indexed.md (Indexed With Lag table)
  • Set "Detected" date from when entry was in to-index
  • Set "Confirmed" date to current date
  • Remove from to-index.md
  • Update counts and statistics

Manual Operations

  • Mark submissions: Update "Submitted" column with date
  • Check status: Use URL Inspection, mark result
  • Refresh data: Import new GSC export, recalculate

Configuration

Create working files in project directory:

project/
├── gsc-export.csv          # GSC indexed pages export
├── sitemap.xml             # Site sitemap (or use dist/sitemap.xml)
├── indexed.md              # Tracking file (generated)
└── to-index.md             # Tracking file (generated)

Commands

Generate Initial Files

"Generate indexing tracking files from GSC export and sitemap"

Pre-process False Positives

"Process false positives and update indexed list"

Update Submission Status

"Mark [URL] as submitted on [date]"

Refresh From New Export

"Update indexed list from new GSC export"

Generate Statistics

"Show indexing progress statistics"

Statistics Output

INDEXING STATUS SUMMARY
=======================

Indexed Public (GSC):     789 pages
Indexed With Lag:          12 pages
Total Indexed:            801 pages

Sitemap Total:          2,054 pages
To Index:               1,253 pages

Progress:                 39.0%

By Priority:
- Priority 1: 55 remaining (4 false positives moved)
- Priority 2: 7 remaining
- Priority 3: 290 remaining

Example Usage

User: "I just checked some URLs in GSC URL Inspection and marked them as false positive - indexed. Process those and update the tracking files."

Claude will:

  • Scan to-index.md for entries with "false positive - indexed"
  • Extract those URLs and their original detection dates
  • Add them to indexed.md Indexed With Lag table
  • Remove them from to-index.md
  • Update row numbers and counts
  • Report changes made

Other skills for the same job

different authors, same section of the catalogue
Protocolsio Integration
by christophacham
×4

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.

16k tokens
Tailored Resume Generator
by frostant
×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens
Excalidraw Diagram Generator
by github
vendor ×3

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

36k tokens scripts
Expo Dev Client
by openai
vendor ×3

Build and distribute Expo development clients locally or via TestFlight

961 tokens
Executing Plans
by ZhanlinCui
×3

Use when you have a written implementation plan to execute in a separate session with review checkpoints

542 tokens
Anndata
by christophacham
×3

Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.

16k tokens
Benchling Integration
by christophacham
×3

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

14k tokens
Biopython
by christophacham
×3

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

24k tokens

How to use it

Copy the folder

Take nicepkg/gsc-assistant from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.