agentleFS
dragosrouadragosroua/claude-content-skills/skills/gsc-assistant/SKILL.md

gsc-assistant

Skill15 starsChanged 12 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    indexed.md: - All indexed pages in two tables:

    line 12
  2. Distinctive:

    When checking to-index pages via URL Inspection:

    line 36
  3. Distinctive:

    If indexed: Mark as "false positive - indexed" in Submitted column

    line 37
  4. Distinctive:

    Import GSC export CSV to create indexed.md (Indexed Public table)

    line 100
  5. Distinctive:

    Update counts and statistics

    line 113
  6. Distinctive:

    Check status: Use URL Inspection, mark result

    line 118
  7. Distinctive:

    Create working files in project directory:

    line 123
  8. Distinctive:

    Add them to indexed.md Indexed With Lag table

    line 188
  9. Distinctive:

    Remove them from to-index.md

    line 189
  10. Distinctive:

    Update row numbers and counts

    line 190

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GSC Assistant Skill

Purpose

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

  1. 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)
  2. 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

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

Regular Updates

  1. Pre-processing: Scan to-index.md for "false positive - indexed" entries
  2. Move false positives to indexed.md (Indexed With Lag table)
  3. Set "Detected" date from when entry was in to-index
  4. Set "Confirmed" date to current date
  5. Remove from to-index.md
  6. 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:

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.