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:
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?
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)?
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
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:
Algorithm / Core Update Impact
- Drop coincides with known Google core update dates
- Impact skewed toward certain types of queries or content
- No major technical changes around the same time
Technical / Infrastructure Failure
- Indexing/crawlability suddenly impaired
- Widespread 5xx/4xx errors
- Robots.txt or meta noindex changes
- Broken redirects or canonicalization errors
Manual Action / Policy Violation
- Manual action message in GSC
- Sudden, severe drop in branded and non-branded queries
- History of aggressive link building or spammy tactics
Content / Quality Reassessment
- Specific sections or topics hit harder
- Content thin, outdated, or heavily AI-generated
- Competitors significantly improved content around the same topics
Demand / Seasonality / External Factors
- Search demand drop in the niche (check industry trends)
- Macro events, regulation changes, or market shifts
Data-Driven Investigation Steps
When you have GSC and analytics access, structure the analysis like a forensic investigation:
1. Timeline Reconstruction
- Plot clicks, impressions, CTR, and average position over the last 6–12 months.
- Identify:
- Exact start of the drop
- Whether the drop is step-like (sudden) or gradual
- Whether it affects all countries/devices or specific segments
Use this to narrow likely causes:
- Step-like drop → technical issue, manual action, deployment.
- Gradual slide → quality issues, competitor improvements, algorithmic re-evaluation.
2. Segment Analysis
Segment the impact by:
- Device: desktop vs. mobile
- Country / region
- Query type: branded vs. non-branded
- Page type: home, category, product, blog, docs, etc.
Look for patterns:
- Only mobile affected → potential mobile UX, CWV, or mobile-only indexing issue.
- Specific country affected → geo-targeting, hreflang, local factors.
- Non-branded hit harder than branded → often algorithm/quality-related.
3. Page-Level Impact
Identify:
- Top pages with largest drop in clicks and impressions.
- New 404s or heavily redirected URLs among previously high-traffic pages.
- Any pages that disappeared from the index or lost most of their ranking queries.
Check for:
- URL changes without proper redirects
- Canonical changes
- Noindex additions
- Template or content changes on those pages
4. Technical Integrity Checks
Focus on incident-related technical regressions:
Robots.txt
- Any recent changes?
- Are key sections blocked unintentionally?
Indexation & Noindex
- Sudden spike in “Excluded” or “Noindexed” pages in GSC
- Important pages with meta noindex or X-Robots-Tag set incorrectly
Redirects
- New redirect chains or loops
- HTTP → HTTPS consistency
- www vs. non-www consistency
- Migrations without full redirect mapp
1---2name: seo-forensic-incident-response3description: Investigate sudden drops in organic traffic or rankings and run a structured forensic SEO incident response with triage, root-cause analysis and recovery plan.4---5
6
7# SEO Forensic Incident Response
8
9You 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.
10
11This skill is not a generic SEO audit. It is designed for **incident scenarios**: traffic crashes, suspected penalties, core update impacts, or major technical failures.
12
13## When to Use
14
15Use this skill when:
16- You need to understand and resolve a sudden, significant drop in organic traffic or rankings.
17- There are signs of a possible penalty, core update impact, major technical regression or other SEO incident.
18
19Do **not** use this skill when:
20- You need a routine SEO health check or prioritization of opportunities (use `seo-audit`).
21- You are focused on long-term local visibility for legal/professional services (use `local-legal-seo-audit`).
22
23## Initial Incident Triage
24
25Before deep analysis, clarify the incident context:
26
271. **Incident Description**
28 - When did you first notice the drop?
29 - Was it sudden (1–3 days) or gradual (weeks)?
30 - Which metrics are affected? (sessions, clicks, impressions, conversions)
31 - Is the impact site-wide, specific sections, or specific pages?
32
332. **Data Access**
34 - Do you have access to:
35 - Google Search Console (GSC)?
36 - Web analytics (GA4, Matomo, etc.)?
37 - Server logs or CDN logs?
38 - Deployment/change logs (Git, CI/CD, CMS release notes)?
39
403. **Recent Changes Checklist**
41 Ask explicitly about the 30–60 days before the drop:
42 - Site redesign or theme change
43 - URL structure changes or migrations
44 - CMS/plugin updates
45 - Changes to hosting, CDN, or security tools (WAF, firewalls)
46 - Changes to robots.txt, sitemap, canonical tags, or redirects
47 - Bulk content edits or content pruning
48
494. **Business Context**
50 - Is this a seasonal niche?
51 - Any external events affecting demand?
52 - Any previous manual actions or penalties?
53
54---
55
56## Incident Classification Framework
57
58Classify the incident into one or more buckets to guide the investigation:
59
601. **Algorithm / Core Update Impact**
61 - Drop coincides with known Google core update dates
62 - Impact skewed toward certain types of queries or content
63 - No major technical changes around the same time
64
652. **Technical / Infrastructure Failure**
66 - Indexing/crawlability suddenly impaired
67 - Widespread 5xx/4xx errors
68 - Robots.txt or meta noindex changes
69 - Broken redirects or canonicalization errors
70
713. **Manual Action / Policy Violation**
72 - Manual action message in GSC
73 - Sudden, severe drop in branded and non-branded queries
74 - History of aggressive link building or spammy tactics
75
764. **Content / Quality Reassessment**
77 - Specific sections or topics hit harder
78 - Content thin, outdated, or heavily AI-generated
79 - Competitors significantly improved content around the same topics
80
815. **Demand / Seasonality / External Factors**
82 - Search demand drop in the niche (check industry trends)
83 - Macro events, regulation changes, or market shifts
84
85---
86
87## Data-Driven Investigation Steps
88
89When you have GSC and analytics access, structure the analysis like a forensic investigation:
90
91### 1. Timeline Reconstruction
92
93- Plot clicks, impressions, CTR, and average position over the last 6–12 months.
94- Identify:
95 - Exact start of the drop
96 - Whether the drop is step-like (sudden) or gradual
97 - Whether it affects all countries/devices or specific segments
98
99Use this to narrow likely causes:
100- **Step-like drop** → technical issue, manual action, deployment.
101- **Gradual slide** → quality issues, competitor improvements, algorithmic re-evaluation.
102
103### 2. Segment Analysis
104
105Segment the impact by:
106
107- **Device**: desktop vs. mobile
108- **Country / region**
109- **Query type**: branded vs. non-branded
110- **Page type**: home, category, product, blog, docs, etc.
111
112Look for patterns:
113- Only mobile affected → potential mobile UX, CWV, or mobile-only indexing issue.
114- Specific country affected → geo-targeting, hreflang, local factors.
115- Non-branded hit harder than branded → often algorithm/quality-related.
116
117### 3. Page-Level Impact
118
119Identify:
120
121- Top pages with largest drop in clicks and impressions.
122- New 404s or heavily redirected URLs among previously high-traffic pages.
123- Any pages that disappeared from the index or lost most of their ranking queries.
124
125Check for:
126
127- URL changes without proper redirects
128- Canonical changes
129- Noindex additions
130- Template or content changes on those pages
131
132### 4. Technical Integrity Checks
133
134Focus on incident-related technical regressions:
135
136- **Robots.txt**
137 - Any recent changes?
138 - Are key sections blocked unintentionally?
139
140- **Indexation & Noindex**
141 - Sudden spike in “Excluded” or “Noindexed” pages in GSC
142 - Important pages with meta noindex or X-Robots-Tag set incorrectly
143
144- **Redirects**
145 - New redirect chains or loops
146 - HTTP → HTTPS consistency
147 - www vs. non-www consistency
148 - Migrations without full redirect mapp