Agent skill · DevOps & Cloud

seo-traffic-diagnosis

Diagnose organic traffic changes (drops, stalls, or unexpected wins) using Ahrefs MCP plus Search Console data. Use this skill when traffic suddenly dropped, has been flat despite investment, after an algorithm update, after a migration or deploy, or when a competitor seems to be taking share. Triggers on traffic dropped, traffic decline, traffic stalled, organic decline, lost rankings, why is traffic down, algorithm update, post-migration traffic loss, traffic diagnosis. Also triggers when stakeholders are panicking about analytics.

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill seo-traffic-diagnosis --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 8 KB
Bundled scripts: none
Path: skills/seo-traffic-diagnosis/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# SEO Traffic Diagnosis Diagnose why organic traffic moved (down, flat, or unexpectedly up) using Ahrefs MCP combined with Search Console and analytics data. Stack-agnostic. Produces a root-cause diagnosis and an action plan. --- ## When to use - Organic traffic dropped sharply - Organic traffic has been flat for months despite content investment - After a known Google algorithm update - After a migration, replatform, or domain change - After a deploy that touched routing, redirects, or rendering - When a competitor is visibly taking organic share - When a single page dropped from a ranked position - When stakeholders need an explanation, fast ## When NOT to use - Routine performance reporting (use `analytics-strategy`) - Pre-emptive content planning (use `seo-content-gap-audit`) - Backlink-only investigations (use `seo-backlink-audit`) - Technical issue triage outside of traffic concerns (use `seo-site-health-audit`) --- ## Required inputs - Description of the symptom (what changed, when, magnitude) - Date the change started (best estimate) - Recent SEO history: deploys, migrations, content changes, link campaigns - Access to Ahrefs MCP, Search Console, and analytics - Confirmatio

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Required inputs
  4. The framework: 5 layers of diagnosis
  5. Layer 1: Confirm the change is real
  6. Layer 2: Localize the change
  7. Layer 3: Page-level analysis
  8. Layer 4: Technical analysis
  9. Layer 5: External analysis
  10. Workflow
  11. Failure patterns
  12. Output format
  13. Reference files
Ships with 1 file
  • references/diagnosis-checklist.md
More from claude-skills
All skills →
About this skill
What does the seo-traffic-diagnosis skill do?

Diagnose organic traffic changes (drops, stalls, or unexpected wins) using Ahrefs MCP plus Search Console data. Use this skill when traffic suddenly dropped, has been flat despite investment, after an algorithm update, after a migration or deploy, or when a competitor seems to be taking share. Triggers on traffic dropped, traffic decline, traffic stalled, organic decline, lost rankings, why is traffic down, algorithm update, post-migration traffic loss, traffic diagnosis. Also triggers when stakeholders are panicking about analytics.

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill seo-traffic-diagnosis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going