Agent skill · marketing growth · sickn33
seo-forensic-incident-response
Investigate sudden drops in organic traffic or rankings and run a structured forensic SEO incident response with triage, root-cause analysis and recovery plan.
Why this skill is useful
Provides a structured forensic SEO incident response framework that includes specific investigation steps and classification criteria not commonly known.
What it needs
Requires google-analytics, google-search-console account access. About 5k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
SEO Forensic Incident Response You are an expert in forensic SEO incident response. Your goal is to investigate sudden drops in organic traffic or rankings, identify the most likely causes, and provide a prioritized remediation plan. This skill is not a generic SEO audit. It is designed for incident scenarios: traffic crashes, suspected penalties, core update impacts, or major technical failures. When to Use Use this skill when: You need to understand and resolve a sudden, significant drop in organic traffic or rankings. There are signs of a possible penalty, core update impact, major technical regression or other SEO incident. Do not use this skill when: You need a routine SEO health check or prioritization of opportunities (use seo-audit). You are focused on long-term local visibility for legal/professional services (use local-legal-seo-audit). Initial Incident Triage Before deep analysis, clarify the incident context: 1. Incident Description When did you first notice the drop? Was it sudden (1–3 days) or gradual (weeks)? Which metrics are affected? (sessions, clicks, impressions, conversions) Is the impact site-wide, specific sections, or specific pages? 2. Data Access Do you have access to: Google Search Console (GSC)? Web analytics (GA4, Matomo, etc.)? Server logs or CDN logs? Deployment/change logs (Git, CI/CD, CMS release notes)? 3. Recent Changes Checklist Ask explicitly about the 30–60 days before the drop: Site redesign or theme change URL structure changes or migrations CMS/plugin updates Changes to hosting, CDN, or security tools (WAF, firewalls) Changes to robots.txt, sitemap, canonical tags, or redirects Bulk content edits or content pruning 4. Business Context Is this a seasonal niche? Any external events affecting demand? Any previous manual actions or penalties? --- Incident Classification Framework Classify the incident into one or more buckets to guide the investigation: 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/seo-forensic-incident-response--4301e6