mcpField
A
analytics-interpretation

analytics-interpretation

github.com/nicepkgMarketing & growth28864 installsUpdated 40w ago
Repository

About analytics-interpretation

A guide for content and SEO teams interpreting traffic, content performance, and search data to inform optimization decisions. It combines GA4 and Google Search Console metrics with benchmarks, trend analysis, and a content health scoring method.

Key features

  1. 01GA4 and Search Console metric interpretation
  2. 02Combined-signal traffic quality analysis
  3. 03Content health scoring method
  4. 04Week-over-week trend analysis
  5. 05Anomaly thresholds and possible causes

Use cases

  1. 01Review content reports and identify optimization priorities
  2. 02Explain site metrics to stakeholders
  3. 03Investigate changes in traffic, CTR, or rankings

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nicepkg/ai-workflow --skill analytics-interpretation

After installing, type/analytics-interpretationin Claude Code to confirm it loaded.

Details

From the project README

Analytics Interpretation

When to Use

  • Analyzing content performance reports
  • Understanding traffic patterns
  • Interpreting search console data
  • Making data-driven content decisions
  • Explaining metrics to stakeholders

Metric Benchmarks

Google Analytics 4 (GA4)
MetricGoodWarningPoorAction When Poor
Avg Time on Page>3 min1-3 min<1 minImprove content depth, add multimedia
Bounce Rate<40%40-70%>70%Add internal links, improve intro hook
Engagement Rate>60%30-60%<30%Review content quality, add CTAs
Scroll Depth>75%50-75%<50%Add visual breaks, improve structure
Pages/Session>2.51.5-2.5<1.5Improve internal linking
Google Search Console (GSC)
MetricGoodWarningPoorAction When Poor
CTR>5%2-5%<2%Improve title/meta description
Avg Position1-34-10>10Strengthen content, build links
Impressions TrendGrowingStableDecliningRefresh content, target new keywords
Mobile UsabilityPASS-FAILFix mobile issues immediately
Core Web VitalsGOODNEEDS_IMPROVEMENTPOOROptimize performance

Interpreting Combined Signals

Traffic Quality Matrix
                    High Engagement
                          │
           ┌──────────────┼──────────────┐
           │  HIDDEN GEM  │   STAR       │
           │  Low traffic │   High traffic│
           │  High quality│   High quality│
           │  → Promote   │   → Maintain  │
Low ───────┼──────────────┼──────────────┼─── High
Traffic    │              │              │   Traffic
           │  UNDERPERFORM│   LEAKY      │
           │  Low traffic │   High traffic│
           │  Low quality │   Low quality │
           │  → Rework    │   → Optimize  │
           └──────────────┼──────────────┘
                          │
                    Low Engagement
Search Intent Alignment
GSC SignalGA4 SignalInterpretation
High impressionsLow clicksTitle/meta mismatch with intent
High CTRHigh bounceContent doesn't deliver on promise
Low CTRHigh engagement (when clicked)Hidden gem, improve snippet
Growing impressionsStable clicksRanking improving, CTR opportunity

Score Calculation Methodology

Content Health Score (0-100)
health_score = (
    engagement_score × 0.30 +
    seo_score × 0.30 +
    ranking_score × 0.20 +
    trend_score × 0.20
)

Component Calculations:

engagement_score = normalize(
    time_on_page_score × 0.4 +
    bounce_rate_score × 0.3 +
    scroll_depth_score × 0.3
)

seo_score = normalize(
    ctr_score × 0.4 +
    position_score × 0.4 +
    impressions_growth × 0.2
)

ranking_score = normalize(
    avg_position × 0.5 +
    visibility_score × 0.3 +
    keyword_coverage × 0.2
)

trend_score = normalize(
    traffic_trend × 0.4 +
    ranking_trend × 0.3 +
    engagement_trend × 0.3
)
Score Interpretation
ScoreRatingStatusAction
90-100ExcellentPerforming optimallyMaintain, minor tweaks
75-89GoodSolid performanceOptimize weak areas
60-74FairRoom for improvementAddress key issues
40-59PoorUnderperformingMajor revision needed
0-39CriticalFailingComplete overhaul

Trend Analysis

Week-over-Week Comparison
| Metric | This Week | Last Week | Change | Status |
|--------|-----------|-----------|--------|--------|
| Sessions | 1,245 | 1,180 | +5.5% | ↑ GROWING |
| Avg Position | 4.2 | 4.8 | +0.6 | ↑ IMPROVING |
| CTR | 2.8% | 2.6% | +0.2pp | ↑ IMPROVING |
| Bounce Rate | 42% | 38% | +4pp | ↓ DECLINING |
Interpreting Trends
Trend PatternInterpretationRecommended Action
↑↑↑ All metrics upContent gaining momentumDouble down, create related content
↑↓↑ Mixed signalsTransition periodMonitor closely, identify cause
↓↓↓ All metrics downContent decliningUrgent refresh needed
→→→ All flatPlateau reachedExperiment with new angles

Anomaly Detection

Significant Change Thresholds
MetricSignificant ChangeAlert Level
Traffic±30% WoWHIGH
CTR±1pp WoWMEDIUM
Position±5 positionsHIGH
Bounce Rate±10pp WoWMEDIUM
Common Anomaly Causes
AnomalyPossible Causes
Sudden traffic dropAlgorithm update, technical issue, competitor
CTR spikeSERP feature win, seasonal interest
Position fluctuationGoogle testing, competitor changes
Engagement dropContent staleness, UX issue

Output Templates

Metric Summary Card
## {Metric Name}

**Current Value**: {value}
**Benchmark**: {benchmark}
**Status**: {GOOD|WARNING|POOR}
**Trend**: {↑|→|↓} ({change}% vs last period)

**Interpretation**: {1-2 sentence explanation}

**Recommended Action**: {specific action if needed}
Executive Summary
## Content Performance Summary

**Overall Health**: {score}/100 ({rating})

### Key Wins
- {positive finding 1}
- {positive finding 2}

### Concerns
- {issue 1}
- {issue 2}

### Priority Actions
1. {highest priority action}
2. {second priority action}
3. {third priority action}

Comments

Markdown supported