google-search-console
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…
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
$ npx -y skills add kostja94/marketing-skills --skill seo-monitoring --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/seo-monitoringContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
name: seo-monitoring description: When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console. metadata: version: 1.0.1
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.
| 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.
| 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 |
| Metric | Purpose | Data Source | |--------|---------|-------------| | **Rank changes** | Target keyword movement | GSC, SEO tools | | **Keyword count** | New gains / losses per page | SEO tools, GSC |
| 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) |
**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**).
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 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**:
Choose by privacy, cost, and team workflow.
| 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 |
| 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 |
| 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 |
| Metric | Source | Notes | |--------|--------|------| | Pages per session | GA4 | Use GA for own site; third-party for competitors | | Avg session duration | GA4 | | | Bounce rate | GA4 | |
| 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 + com
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
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…
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…
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic,"…
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4,"…
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,"…
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…