mcpField
3
30x-seo-monitor

30x-seo-monitor

github.com/norahe0304-artMarketing & growth5663 installsUpdated 33w ago
Repository

About 30x-seo-monitor

30x-seo-monitor is a skill for monitoring a site's SEO performance through Google Search Console data. It is intended for site owners and SEO practitioners who need reports on queries, pages, ranking changes, and potential CTR opportunities.

Key features

  1. 01Overview of clicks, impressions, CTR, and position
  2. 02Keyword and page performance reports
  3. 03Detection of ranking gains and losses
  4. 04High-impression, low-CTR opportunity checks
  5. 05Custom reporting date ranges

Use cases

  1. 01Reviewing weekly search performance
  2. 02Finding keywords with changing rankings
  3. 03Identifying pages with low CTR
  4. 04Tracking SEO metrics over a selected period

MCP support

It uses Google Search Console through the gws CLI or a GSC MCP server. The README lists the MCP server as one way to provide access.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/norahe0304-art/30x-seo --skill 30x-seo-monitor

After installing, type/30x-seo-monitorin Claude Code to confirm it loaded.

Details

From the project README

SEO Monitor (Google Search Console)

Monitor your own website's SEO performance using Google Search Console API.

[PROTOCOL]: Update this header on changes, then check CLAUDE.md

Prerequisites

Requires gws CLI with Google Search Console access, or GSC MCP server.

Option 1: gws CLI
gws auth status
gws auth login  # if needed
Option 2: GSC MCP Server

Configure in ~/.config/claude/mcp.json:

{
  "mcpServers": {
    "google-search-console": {
      "command": "npx",
      "args": ["-y", "mcp-server-gsc"],
      "env": {
        "GOOGLE_CREDENTIALS_PATH": "/path/to/credentials.json"
      }
    }
  }
}

Commands

CommandWhat it does
/30x-seo monitor overviewDashboard: top queries, pages, CTR, position
/30x-seo monitor keywordsAll ranking keywords with metrics
/30x-seo monitor pagesTop performing pages
/30x-seo monitor changesPosition changes (gains/losses)
/30x-seo monitor opportunitiesHigh impression, low CTR keywords

Metrics Explained

MetricWhat it means
ClicksUsers clicked your result
ImpressionsYour result appeared in search
CTRClick-through rate (clicks / impressions)
PositionAverage ranking position (1 = top)

Analysis Workflows

1. Weekly Performance Check
/30x-seo monitor overview

Output:

  • Total clicks, impressions, CTR, avg position (7 days)
  • Top 10 queries by clicks
  • Top 10 pages by clicks
  • Week-over-week comparison
2. Keyword Ranking Report
/30x-seo monitor keywords

Output:

  • All ranking keywords
  • Position, clicks, impressions, CTR per keyword
  • Sort by: position, clicks, impressions, or CTR
3. Position Change Detection
/30x-seo monitor changes

Output:

  • Keywords that gained positions (rising)
  • Keywords that lost positions (declining)
  • New keywords (just started ranking)
  • Lost keywords (dropped out of top 100)
4. Quick Win Opportunities
/30x-seo monitor opportunities

Find keywords with:

  • High impressions (>1000/month)
  • Low CTR (<3%)
  • Position 4-20 (page 1-2)

These are "quick wins" - improve title/description to boost CTR.


Date Ranges

Default: last 7 days

Specify custom range:

/30x-seo monitor overview --days 30
/30x-seo monitor keywords --days 90

Output Format

Reports include:

  1. Summary table — Key metrics at a glance
  2. Detailed data — Full keyword/page lists
  3. Action items — Specific recommendations

Integration with Other Skills

ScenarioNext Step
Found declining keyword→ 30x-seo-content-decay to analyze page
Low CTR on page 1→ 30x-seo-page to optimize title/meta
Keyword cannibalization suspected→ 30x-seo-cannibalization to check
New keyword opportunity→ 30x-seo-content-brief to plan content

Limitations

  • Only your verified sites — GSC only shows data for sites you own
  • Data delay — GSC data is 2-3 days behind
  • 90 day max — Historical data limited to ~16 months, but API typically 90 days
  • Sampled data — High-traffic sites may show sampled data

Comments

Markdown supported