Systems Lab

Agent skill

gsc-performance-analyzer

This skill should be used when the user asks to \"analyze GSC performance\", \"optimize organic CTR\", \"check keyword rankings\", or mentions \"position tracking\", \"seasonal SEO trends\", or \"Google Discover performance\".

activeSelf-containedInstructions only1,469 words

Filed under Content and SEO.

From Ad-Superpowers/ad-superpowers-plugin · 120 skills · 5 · pushed 2026-09-10

What it does when it runs

This skill should be used when the user asks to \"analyze GSC performance\", \"optimize organic CTR\", \"check keyword rankings\", or mentions \"position tracking\", \"seasonal SEO trends\", or \"Google Discover performance\". Do NOT use for: indexing problems or technical SEO issues (use technical-seo-monitor).

Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about gsc-performance-analyzer

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/Ad-Superpowers/ad-superpowers-plugin.git /tmp/ad-superpowers-plugin
git -C /tmp/ad-superpowers-plugin sparse-checkout set "plugin/skills/gsc-performance-analyzer"
mkdir -p ~/.claude/skills/gsc-performance-analyzer
cp -R "/tmp/ad-superpowers-plugin/plugin/skills/gsc-performance-analyzer/." ~/.claude/skills/gsc-performance-analyzer/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

Or take the whole library

This repo ships a .claude-plugin manifest, so Claude Code can install all 120 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.

/plugin marketplace add Ad-Superpowers/ad-superpowers-plugin
/plugin

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from Ad-Superpowers/ad-superpowers-plugin/blob/9b6385d2d2d228e4dac096a1d6bc5715c04fa736/plugin/skills/gsc-performance-analyzer/SKILL.md, which is licensed MIT (repository). 1,469 words, 21 headings.

GSC Performance Analyzer

Purpose

Provide expert-level interpretation of Google Search Console data. Transform raw metrics (clicks, impressions, CTR, position) into actionable SEO insights with proper context for benchmarks, seasonality, and data quality.

When to Use This Skill

Invoke when user mentions:

  • Performance analysis: "How is my organic search doing?"
  • CTR optimization: "My CTR is low, what should I do?"
  • Position tracking: "Am I ranking well for this keyword?"
  • Trends: "Why did my traffic drop last week?"
  • Search appearances: "What are rich results?"
  • Discover/News: "How is my content doing in Google Discover?"
  • Data quality: "Is my GSC data accurate?"

Required Tools

ToolPurpose
gsc_search_analyticsAll organic search data queries
gsc_list_sitesProperty discovery
gsc_manage_url(action="inspect")Page-level indexing diagnostics
gsc_search_analytics(dimensions=["page"])Page-level performance overview

Part 1: CTR Benchmarks by Position

Expected CTR by Average Position (Web Search, 2024-2026 data)

AI Overviews impact: Google AI Overviews (formerly SGE) are shown for a large portion of informational queries. For queries where an AI Overview appears, CTR for positions 1-3 can drop 20-60% compared to the benchmarks below. The effect is strongest on "what is", "how to", and definition queries. Navigational, commercial, and brand queries are less affected.

PositionExpected CTRRangeInterpretation
127-32%22-39%#1 should capture ~30% of clicks — lower if AI Overview shown
215-18%12-22%Strong second position
310-13%8-16%Still above the fold
47-9%5-11%Often below ads on mobile
55-7%3-9%Bottom of first visible results
6-73-5%2-6%Requires scrolling on mobile
8-102-3%1-4%Bottom of page 1
11-200.5-1.5%0.2-2%Page 2 — very few clicks

CTR Modifiers

FactorCTR ImpactNotes
AI Overview present-20-60%Informational queries most affected; answer shown inline
Rich snippets (FAQ, How-to)+20-50%Higher visibility, more SERP real estate
Sitelinks+15-30%Authority signal, more click targets
Featured snippet (position 0)+40-80%Dominates SERP, but may reduce position 1 CTR
Brand query+50-100%Users specifically looking for you
Long-tail (4+ words)+10-20%Higher intent, less competition
SERP features (maps, shopping)-10-30%Competing visual elements push organic down
Ads above organic-15-25%Especially on mobile, ads push organic below fold

CTR Diagnosis Framework

IF actual_ctr > expected_ctr × 1.3:
    → Excellent! Strong titles/meta descriptions
    → Consider: Are you getting enough impressions?

IF actual_ctr is within ±30% of expected:
    → Normal performance for this position
    → Focus on improving position rather than CTR

IF actual_ctr < expected_ctr × 0.7:
    → Below expected — investigate:
    1. Title tag: Is it compelling? Under 60 chars?
    2. Meta description: Does it include a CTA? Under 155 chars?
    3. SERP features: Are rich results/ads pushing you down?
    4. Search intent mismatch: Does your page match what searchers want?
    5. Competing sitelinks: Does a competitor have expanded sitelinks?

Part 2: Performance Patterns

Seasonal Analysis

To detect seasonality, query with dimensions=["date"] over 90+ days:

PatternDetectionAction
Weekly cycleCompare Mon-Sun averagesB2B: weekday peaks; B2C: weekend peaks
Monthly cycleCompare week-over-weekE-commerce: paycheck cycles, month-end
SeasonalCompare month-over-monthHoliday, weather, industry events
Trend3-month moving averageGradual decline = content aging; rise = growing authority

Common Traffic Drop Causes

SymptomLikely CauseDiagnosis
All queries drop equallyAlgorithm updateCheck Google Search Status dashboard
Specific page dropsLost ranking for key termsCheck position changes for that page
Impressions stable, clicks drop, position stableAI Overviews absorbing clicksCheck if query type is informational; AI Overview is answering the question in SERP
Impressions up, clicks downPosition dropped below fold OR AI OverviewCTR decline with impression growth; check query types
Impressions down, CTR stableLost rankings broadlyCompare positions period-over-period
Single-day cliffTechnical issueCheck gsc_manage_url(action="inspect") for crawl errors
Gradual decline over weeksContent freshness decay or AI Overview rolloutContent needs updating; check if informational queries are affected
Mobile-only dropMobile usability issueCheck mobile-specific metrics

Part 3: Search Type Analysis

Web (Default)

Standard organic search results. Primary metric for most sites.

Google Discover

gsc_search_analytics(site_url="...", search_type="discover", days=28)
MetricGoodAveragePoor
CTR> 8%4-8%< 4%
Impressions/article> 5,0001,000-5,000< 1,000

Discover optimization:

  • Large, high-quality images (min 1200px wide)
  • Compelling, non-clickbait titles
  • E-E-A-T signals (author bios, expertise)
  • Fresh, timely content
  • Topics the user has shown interest in (personalized)

Google News

gsc_search_analytics(site_url="...", search_type="news", days=28)

News-specific considerations:

  • Timeliness is critical (24-72 hour window)
  • Headline quality directly impacts CTR
  • Structured data (NewsArticle schema) improves visibility

Image Search

gsc_search_analytics(site_url="...", search_type="image", days=28)

Image optimization:

  • Descriptive alt text
  • Relevant file names
  • Proper image sitemaps
  • WebP format for speed

Part 4: Data Quality Guide

Data Freshness

Data StateAvailabilityAccuracy
final (default)3-4 days delayHigh — confirmed data
all1-2 days delayMedium — may be revised

Known Limitations

LimitationImpactWorkaround
Max 16 months historyCan't compare YoY beyond 16 monthsExport monthly for long-term tracking
25,000 row limit per queryLarge sites may miss long-tail dataUse filters to segment queries
Position is averagePosition 5.3 could be 1 sometimes, 10 othersAdd date dimension for daily positions
Anonymized queriesVery low-volume queries hidden~10-20% of impressions may be anonymized
Click/impression countingDeduplicated per query per day per userLower than raw pageview counts
Fresh data revisions"all" data may change after finalizationUse "final" for reporting

Sampling

GSC does NOT sample data (unlike GA4). All reported metrics are based on actual data. However:

  • Very rare queries may be anonymized (privacy threshold)
  • Position is an average — a query at position 1 and position 20 shows as 10.5

Part 5: Output Format

================================================================================
                     ORGANIC SEARCH PERFORMANCE ANALYSIS
                     Property: [site_url]
                     Period: [start_date] to [end_date]
================================================================================

EXECUTIVE SUMMARY
─────────────────
Total clicks: [X] ([+/-Y%] vs previous period)
Total impressions: [X] ([+/-Y%])
Average CTR: [X%] (benchmark: [Y%] for avg position [Z])
Average position: [X] ([improved/declined] by [Y])

HEALTH ASSESSMENT: [STRONG / STABLE / DECLINING / NEEDS ATTENTION]

TOP PERFORMING QUERIES (by clicks)
───────────────────────────────────
| Query | Clicks | Impressions | CTR | Position | CTR vs Benchmark |
|-------|--------|-------------|-----|----------|-----------------|
| [kw]  | 450    | 12,000      | 3.8%| 4.2      | Normal ✓        |
| [kw]  | 320    | 8,500       | 3.8%| 2.1      | LOW ⚠️ (expect 15-18%) |

CTR OPTIMIZATION OPPORTUNITIES
──────────────────────────────
Keywords where CTR is significantly below benchmark for their position:

| Query | Position | Actual CTR | Expected CTR | Gap | Fix |
|-------|----------|-----------|-------------|-----|-----|
| [kw]  | 1.5      | 12%       | 28-32%      | -16% | Improve title tag — OR check if AI Overview present |
| [kw]  | 3.2      | 4%        | 10-13%      | -6%  | Add rich snippets |

Note: If an AI Overview is shown for an informational query, low CTR at positions 1-3 is expected and may not be fixable via on-page optimization. The strategic response is to target commercial/navigational queries where AI Overviews are less prevalent, or to optimize content to be cited within the AI Overview itself (structured data, E-E-A-T).

TREND ANALYSIS
──────────────
[Week-over-week or day-over-day trend observations]

SEARCH TYPE BREAKDOWN
─────────────────────
| Type | Clicks | Impressions | CTR | Trend |
|------|--------|-------------|-----|-------|
| Web | [X] | [Y] | [Z%] | [↑↓→] |
| Discover | [X] | [Y] | [Z%] | [↑↓→] |
| Image | [X] | [Y] | [Z%] | [↑↓→] |

RECOMMENDATIONS
───────────────
1. [Highest-impact recommendation]
2. [Second recommendation]
3. [Third recommendation]

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what gsc-performance-analyzer does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.