Skip to content
Skillpedia
SEO48k · #4127

seo-forensic-incident-response

Helps your agent investigate drops in traffic or rankings. It analyzes the cause and suggests a plan to fix it. Use when your website traffic suddenly drops.

What it does

This tool helps investigate sudden drops in your website's organic traffic (like from Google). It identifies the most likely causes and suggests a plan to fix the issue.

When to use it

  • ✓Your organic traffic dropped drastically overnight.
  • ✓You suspect your site has been penalized by Google.
  • ✓There was a major Google update and your site lost rankings.

Example of what to ask your AI

“My organic traffic dropped 50% last week. What could have happened and how can I fix it?”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/seo-forensic-incident-response/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/seo-forensic-incident-response/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool asks questions about when the drop started, what data you have access to (like Google Search Console), and recent website changes. Then, it classifies the problem (e.g., Google update, technical failure) and suggests investigation steps.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill seo-forensic-incident-response

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/seo-forensic-incident-response/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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. 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
  2. Technical / Infrastructure Failure

    • Indexing/crawlability suddenly impaired
    • Widespread 5xx/4xx errors
    • Robots.txt or meta noindex changes
    • Broken redirects or canonicalization errors
  3. 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
  4. Content / Quality Reassessment

    • Specific sections or topics hit harder
    • Content thin, outdated, or heavily AI-generated
    • Competitors significantly improved content around the same topics
  5. 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

…

FAQ

Is this a full SEO audit?

No, this tool focuses on resolving urgent incidents like traffic drops, not routine audits or growth opportunities.

Do I need access to technical tools?

It's very helpful to have access to Google Search Console and analytics tools so the tool can help you investigate the data.

What are the 'recent changes' the tool asks about?

These are alterations made to your site in the last 30-60 days, such as design updates, link changes, system updates (CMS), or changes to configuration files like robots.txt.

Details

Original description by the author

Investigate sudden drops in organic traffic or rankings and run a structured forensic SEO incident response with triage, root-cause analysis and recovery plan.

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#4127
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills