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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionseo-monitoringExecute the skills CLI command in your project's root directory to begin installation:
Fetches seo-monitoring from kostja94/marketing-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate seo-monitoring. Access via /seo-monitoring in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
309
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
309
stars
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
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 + competitors) | SEO tools | Outreach |
| Indexed pages | SEO tools | High-authority pages; internal linking |
| Outbound domains | SEO tools | Partnership opportunities |
| Metric | Source | Notes |
|---|---|---|
| Keyword count | SEO tools | How many keywords rank |
| Metric | Source | Notes |
|---|---|---|
| Articles published | Manual | Weekly count |
| Published vs indexed | GSC | New content indexing |
| New page traffic | GA4 | Fresh content performance |
| 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.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
We added seo-monitoring from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: seo-monitoring is focused, and the summary matches what you get after install.
We added seo-monitoring from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
seo-monitoring fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
seo-monitoring fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for seo-monitoring matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for seo-monitoring matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for seo-monitoring matched our evaluation — installs cleanly and behaves as described in the markdown.
seo-monitoring fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
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