seo-monitoring▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
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
- Review organic traffic trend
- Record baseline (e.g., monthly total)
- 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 | GA4 | Fresh content performance |
Monthly Record Template
| Category | Metric | Source | Notes | Month 1 | Month 2 |
|---|---|---|---|---|---|
| Traffic | Total sessions | GA4 | |||
| Traffic | Channel share | GA4 | |||
| Engagement | Pages per session | GA4 | |||
| Backlinks | Referring domains | SEO tools | |||
| Content | Articles published | Manual |
Adjust rows as needed.
Work Document Management
- Structure: Metrics, sources, notes, monthly values
- Benefits: Regular review, month-over-month trends, clear ownership
- Format: Spreadsheet or doc; assign owners per metric
Output Format
- Core metrics summary (indexing, traffic, keywords, backlinks)
- Benchmark and trend
- Article database structure (if applicable)
- Tool recommendations
- Monitoring table (customized)
- Action items and owners
Related Skills
- traffic-analysis: Traffic sources, attribution, diversification
- analytics-tracking: GA4, events, CTA attribution, User ID
- google-search-console: GSC reports, indexing, API
- ai-traffic-tracking: AI search traffic
- backlink-analysis: Backlink audit, toxic links
- indexing: Fix indexing issues
How to use seo-monitoring on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add seo-monitoring
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches seo-monitoring from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate seo-monitoring. Access the skill through slash commands (e.g., /seo-monitoring) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★60 reviews- ★★★★★Amelia Yang· Dec 28, 2024
We added seo-monitoring from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Kiara Choi· Dec 24, 2024
Solid pick for teams standardizing on skills: seo-monitoring is focused, and the summary matches what you get after install.
- ★★★★★Dhruvi Jain· Dec 4, 2024
We added seo-monitoring from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Oshnikdeep· Nov 23, 2024
seo-monitoring fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Amelia Abebe· Nov 19, 2024
seo-monitoring fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Min Gill· Nov 15, 2024
Registry listing for seo-monitoring matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ganesh Mohane· Oct 14, 2024
Registry listing for seo-monitoring matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Daniel Srinivasan· Oct 10, 2024
Registry listing for seo-monitoring matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Min Verma· Oct 6, 2024
seo-monitoring fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Rahul Santra· Sep 25, 2024
Keeps context tight: seo-monitoring is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 60