Skip to main content
ClaudeWave
Skill608 estrellas del repoactualizado 4d ago

seo-monitoring

The seo-monitoring skill guides users in building a comprehensive SEO data analysis system that tracks four core metrics: indexing status, organic traffic, keyword rankings, and backlink quality. Use this skill when a user needs to set up benchmark tracking, create an article performance database, recover from algorithm penalties, establish a traffic diversification strategy, or manage SEO work documentation and monitoring dashboards.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/seo-monitoring && cp -r /tmp/seo-monitoring/skills/analytics/seo/seo-monitoring ~/.claude/skills/seo-monitoring
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Analytics: SEO Monitoring

Guides building a holistic SEO data analysis system. Covers four core metrics (indexing, traffic, keywords, backlinks), benchmark setup, article database, tool selection, traffic diversification, penalty recovery, and work document management.

**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Scope

- **Core metrics**: Indexing, traffic, keywords, backlinks
- **Benchmark**: Natural traffic baseline; trend comparison
- **Article database**: Per-article performance tracking
- **Tool selection**: GA4, GSC, SEO tools, analytics platforms
- **Traffic diversification**: Healthy source mix
- **Penalty recovery**: Algorithm impact, fix workflow
- **Work documents**: Monthly records, responsibility tracking

## Four Core Metrics

### 1. Indexing

| Metric | Purpose | Data Source |
|--------|---------|-------------|
| **Pages indexed / not indexed** | Coverage; early focus: all target pages indexed | GSC, site: command, SEO tools |
| **Keyword count per page** | More keywords = more potential traffic | SEO tools |
| **Index coverage** | Target pages indexed; functional pages findable | GSC, site: command |

**Early priority**: Ensure all pages that need to rank are indexed.

### 2. Traffic

| Metric | Purpose | Data Source |
|--------|---------|-------------|
| **Total traffic** | Growth; keyword relevance (irrelevant traffic has little value) | GA4, SEO tools |
| **Subdirectory traffic** | Per-section performance; concentration vs dispersion | SEO tools, GA4 |
| **Competitive comparison** | Organic, keyword traffic, total clicks vs competitors | SEO tools |
| **Organic by page / country** | Granular breakdown | GA4, GSC |

### 3. Keywords

| Metric | Purpose | Data Source |
|--------|---------|-------------|
| **Rank changes** | Target keyword movement | GSC, SEO tools |
| **Keyword count** | New gains / losses per page | SEO tools, GSC |

### 4. Backlinks

| Metric | Purpose | Data Source |
|--------|---------|-------------|
| **Referring domains vs backlinks** | Ratio; directory links can be high volume but low value | SEO tools |
| **Backlink quality** | Do links drive traffic? Low ROI = deprioritize | SEO tools, GA4 (referral) |

## Natural Traffic Benchmark

**Location**: GA4 > Reports > Acquisition > Traffic acquisition

1. Review organic traffic trend
2. Record baseline (e.g., monthly total)
3. Compare periodically to detect growth or decline

**Tip**: Add CTA events on key articles to track content ROI (see **analytics-tracking**).

## Article Database

Track per-article performance to find high/low patterns:

| Field | Use |
|-------|-----|
| **URL, publish date, target keywords** | Content metadata |
| **Index status, rank, traffic, backlinks** | Performance |
| **vs benchmark or competitors** | Context |

Use to guide topic selection, optimization, and resource allocation.

## Tool Selection

*Tool examples are illustrative; no endorsement implied.*

| Use | Tools |
|-----|-------|
| **Precise attribution** | GA4, GSC, Bing Webmaster, Yandex Webmaster |
| **Visit analytics** | Analytics platforms (e.g. Umami, Plausible) |
| **Third-party estimates** | SEO tools |
| **SEO data** | SEO tools |

**Attribution config**:
- **User ID**: Cross-device, cross-session identification; send to GA4
- **GSC API**: Index, clicks, impressions, coverage for automation, dashboards

Choose by privacy, cost, and team workflow.

## Traffic Diversification

| Principle | Guideline |
|-----------|-----------|
| **Search share** | Keep organic search below ~75% of total |
| **Health** | Higher direct + referral share = healthier |
| **Brand sites** | Diversified traffic is common for strong brands |
| **Non-brand** | Possible without brand (e.g., tool sites) |
| **Reputation** | Site/brand reputation matters; Google assessors evaluate it |
| **Engagement** | Content, email, social, free tools drive return visits |

## Penalty Recovery

| Step | Action |
|------|--------|
| **Identify** | Which algorithm update caused the impact |
| **Analyze** | Site issues; draft fix plan |
| **Assess cost** | Decide if fixes are worth it; sometimes abandoning is best |
| **Execute** | Implement changes; wait at least 3 months until next major update |
| **Parallel** | Use other channels for quality traffic; improve engagement data for Google |
| **Data window** | Google typically uses ~6 months of data for site quality |
| **Recovery** | Outcome is uncertain; do what you can, then wait |

## Monitoring Metrics Table

### Traffic

| Metric | Source | Notes |
|--------|--------|-------|
| Total sessions | GA4 | |
| Channel share | GA4 | |
| Channel absolute | GA4 | |
| Country % and absolute | GA4 | |
| Top pages | SEO tools | Compare with competitors |
| Key page traffic | GA4 | Define "key pages" first |

### Engagement

| Metric | Source | Notes |
|--------|--------|------|
| Pages per session | GA4 | Use GA for own site; third-party for competitors |
| Avg session duration | GA4 | |
| Bounce rate | GA4 | |

### Backlinks

| Metric | Source | Notes |
|--------|--------|------|
| Domain authority | SEO tools | |
| Backlinks, referring domains | SEO tools | |
| Top referring domains by authority | SEO tools | |
| Important links | Manual log | Track loss |
| Link graph | SEO tools | Health check |
| New quality links (self + competitors) | SEO tools | Outreach |
| Indexed pages | SEO tools | High-authority pages; internal linking |
| Outbound domains | SEO tools | Partnership opportunities |

### Keywords

| Metric | Source | Notes |
|--------|--------|------|
| Keyword count | SEO tools | How many keywords rank |

### Content Output

| Metric | Source | Notes |
|--------|--------|------|
| Articles published | Manual | Weekly count |
| Published vs indexed | GSC | New content indexing |
| New page traffic | G
google-search-consoleSkill

When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.

ai-traffic-trackingSkill

When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.

traffic-analysisSkill

When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.

analytics-trackingSkill

When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.

community-forumSkill

When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.

directory-submissionSkill

When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.

product-hunt-launchSkill

When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.

distribution-channelsSkill

When the user wants to plan product distribution via marketplaces, app stores, or third-party platforms. Also use when the user mentions "distribution channels," "marketplace listing," "app store listing," "Figma plugin," "Chrome extension marketplace," "AWS Marketplace," "Shopify app," "GPTs store," "app distribution," or "third-party marketplace." For channel mix, use integrated-marketing.