ワンクリックで
analytics-interpretation
Interpret GA4 and GSC data with benchmarks, status indicators, and actionable insights
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Interpret GA4 and GSC data with benchmarks, status indicators, and actionable insights
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Search and discover Claude Code skills and MCP servers from marketplaces, GitHub repositories, and registries. Use when (1) user asks to find skills for a specific task, (2) looking for MCP servers to connect external tools, (3) user mentions "find skill", "search MCP", "discover tools", or "what skills exist for X", (4) before creating a custom skill to check if one already exists.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Download and install Claude Code skills from various sources. Supports GitHub repositories, compressed archives (.zip, .tar.gz, .skill), and direct URLs. Use when user wants to download, install, or add a skill from GitHub, URL, or archive file. Triggers on "download skill", "install skill", "add skill from", "get skill".
Transform legacy codebases into AI-ready projects with Claude Code configurations. Use when (1) analyzing old projects to generate AI coding configurations, (2) creating CLAUDE.md, skills, subagents, slash commands, hooks, or rules for existing projects, (3) user wants to enable vibe coding for a codebase, (4) onboarding new team members with AI-assisted development, (5) user mentions "make project AI-ready", "generate Claude config", or "create coding standards for AI".
Add new skills to an existing workflow and update all related documentation. Use when user wants to add skills from GitHub URLs to a workflow (e.g., "add this skill to the workflow", "为工作流添加技能"). Triggers on adding skills to workflows, updating workflow documentation after skill additions.
Guide for removing skills from an existing workflow and updating all related documentation. Use when user wants to remove skills from a workflow (e.g., "remove skill", "delete skill", "移除技能", "删除技能").
| name | analytics-interpretation |
| description | Interpret GA4 and GSC data with benchmarks, status indicators, and actionable insights |
| Metric | Good | Warning | Poor | Action When Poor |
|---|---|---|---|---|
| Avg Time on Page | >3 min | 1-3 min | <1 min | Improve 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.5 | 1.5-2.5 | <1.5 | Improve internal linking |
| Metric | Good | Warning | Poor | Action When Poor |
|---|---|---|---|---|
| CTR | >5% | 2-5% | <2% | Improve title/meta description |
| Avg Position | 1-3 | 4-10 | >10 | Strengthen content, build links |
| Impressions Trend | Growing | Stable | Declining | Refresh content, target new keywords |
| Mobile Usability | PASS | - | FAIL | Fix mobile issues immediately |
| Core Web Vitals | GOOD | NEEDS_IMPROVEMENT | POOR | Optimize performance |
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
| GSC Signal | GA4 Signal | Interpretation |
|---|---|---|
| High impressions | Low clicks | Title/meta mismatch with intent |
| High CTR | High bounce | Content doesn't deliver on promise |
| Low CTR | High engagement (when clicked) | Hidden gem, improve snippet |
| Growing impressions | Stable clicks | Ranking improving, CTR opportunity |
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 | Rating | Status | Action |
|---|---|---|---|
| 90-100 | Excellent | Performing optimally | Maintain, minor tweaks |
| 75-89 | Good | Solid performance | Optimize weak areas |
| 60-74 | Fair | Room for improvement | Address key issues |
| 40-59 | Poor | Underperforming | Major revision needed |
| 0-39 | Critical | Failing | Complete overhaul |
| 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 |
| Trend Pattern | Interpretation | Recommended Action |
|---|---|---|
| ↑↑↑ All metrics up | Content gaining momentum | Double down, create related content |
| ↑↓↑ Mixed signals | Transition period | Monitor closely, identify cause |
| ↓↓↓ All metrics down | Content declining | Urgent refresh needed |
| →→→ All flat | Plateau reached | Experiment with new angles |
| Metric | Significant Change | Alert Level |
|---|---|---|
| Traffic | ±30% WoW | HIGH |
| CTR | ±1pp WoW | MEDIUM |
| Position | ±5 positions | HIGH |
| Bounce Rate | ±10pp WoW | MEDIUM |
| Anomaly | Possible Causes |
|---|---|
| Sudden traffic drop | Algorithm update, technical issue, competitor |
| CTR spike | SERP feature win, seasonal interest |
| Position fluctuation | Google testing, competitor changes |
| Engagement drop | Content staleness, UX issue |
## {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}
## 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}