SEO Incident Response & Recovery
SEO incident response prepares you to respond quickly and effectively when something goes wrong — a traffic drop, indexation failure, manual action, technical outage, or failed migration.
Learning Focus
After this lesson you can respond to traffic loss, indexing failure, manual actions, technical outages, and track recovery performance.
This lesson covers the seven incident response areas (leaves 11.9.1–11.9.7): traffic loss response plan, indexing failure response plan, manual action response plan, migration recovery plan, technical outage response plan, stakeholder communication plan, and recovery performance tracking.
Traffic Loss Response Plan
Respond to significant organic traffic drops.
Traffic loss response workflow (from Lesson 2.5.1):
- Confirm the drop: Check GSC (impressions and clicks) and GA4 (organic sessions). Is the drop in one or both?
- Isolate timing: When did the drop start? Exact date matters.
- Segment: Brand vs non-brand, device, country, page type.
- Check for technical issues: GSC crawl errors, robots.txt, noindex, server errors, redirect issues.
- Check for algorithm updates: Google Search Status Dashboard.
- Check for competitive changes: Competitor analysis.
- Check for site changes: Deployment log correlation.
- Develop response: Fix technical issues, improve content quality, or adjust strategy.
Escalation criteria:
| Severity | Criteria | Response Time | Notify |
|---|---|---|---|
| Critical | > 50% traffic drop | Within 1 hour | SEO lead, marketing leadership, engineering |
| High | 25-50% drop | Within 4 hours | SEO team |
| Medium | 15-25% drop | Within 24 hours | SEO team |
| Low | 5-15% drop | Weekly review | SEO team |
Indexing Failure Response Plan
Respond to significant drops in indexed pages.
Indexing failure response workflow (from Lesson 2.5.5):
- Confirm the drop: GSC Indexing report — check total indexed pages.
- Isolate cause:
- Check GSC for new errors.
- Check robots.txt changes.
- Check for accidental noindex additions.
- Check server errors.
- Check sitemap status.
- Fix root cause: Revert robots.txt, remove unintended noindex, fix server errors, resubmit sitemaps.
- Request recrawl: Use GSC URL Inspection to request indexing for critical pages.
- Monitor recovery: Index coverage should return to baseline within 1-4 weeks.
Manual Action Response Plan
Respond to a manual action from Google.
Manual action response workflow:
- Confirm: Check GSC Manual Actions report. Note the specific violation.
- Understand: Read Google's documentation for the specific manual action type.
- Audit: Audit your site for the violating practice.
- Fix: Remove or correct all violations.
- Document: Document what was fixed and how.
- Request reconsideration: Submit a reconsideration request explaining what was found and how it was fixed.
- Monitor: GSC will notify you of the reconsideration result.
- If denied: Review the denial reason, audit again, submit a more detailed request.
Common manual action types and fixes:
| Action Type | Fix |
|---|---|
| Unnatural links to your site | Remove or disavow violating links |
| Unnatural links from your site | Remove paid links from your site |
| Thin content | Improve or remove thin pages |
| Cloaking | Remove cloaking, ensure transparency |
| Spammy structured data | Correct or remove violating schema |
Migration Recovery Plan
Respond to SEO issues after a site migration.
Migration recovery workflow:
- Verify redirects: Confirm all 301 redirects are in place and working.
- Check indexation: GSC Indexing report — are new URLs being indexed?
- Check sitemaps: Are new sitemaps submitted and processed?
- Check traffic: Compare to pre-migration baseline.
- Address issues:
- Missing redirects: Add immediately.
- Incorrect redirects: Fix mapping.
- Indexation delay: Submit sitemaps, request indexing via URL Inspection.
- Traffic loss: Implement recovery actions within the first week.
- Rollback if needed: If recovery is not progressing within 2-3 weeks, initiate rollback.
Technical Outage Response Plan
Respond to server outages and technical failures.
Technical outage response workflow:
- Detect: Server monitoring alert, GSC crawl error spike, or user report.
- Assess: What is down? All pages or specific resources? Expected duration?
- Communicate: Inform SEO team, engineering, and stakeholders.
- Restore: Engineering restores service.
- Recover SEO:
- Verify site is accessible to Googlebot.
- Check GSC for crawl errors.
- Request recrawling of critical pages if needed.
- Monitor traffic recovery.
Preventive measures:
- Server monitoring with alerting.
- Redundant hosting/CDN.
- Regular backup and restore testing.
Stakeholder Communication Plan
Core Concept
Communicate SEO incidents to stakeholders.
Communication plan:
| Incident Type | First Notification | Follow-up | Resolution |
|---|---|---|---|
| Traffic drop > 25% | Within 4 hours | Daily updates | Summary report |
| Indexation drop | Within 8 hours | Weekly updates | Indexation restored |
| Manual action | Immediately | Weekly updates | Reconsideration result |
| Migration issue | Within 4 hours | Daily during recovery | Post-mortem report |
| Technical outage | Within 1 hour | Per update frequency | Incident report |
Stakeholder communication checklist:
| Element | Include |
|---|---|
| What happened | Brief description of the incident |
| Why it happened | Root cause (if known) |
| What we are doing | Response actions |
| Expected recovery timeline | Best estimate |
| How we will prevent recurrence | Follow-up plan |
Recovery Performance Tracking
Track the recovery process and measure success.
Recovery metrics:
| Metric | Recovery Target | Tracking Period |
|---|---|---|
| Organic traffic | Return to 90%+ of pre-incident baseline | 4-8 weeks |
| Indexed pages | Return to pre-incident count | 2-4 weeks |
| Priority keyword rankings | Return to pre-incident positions | 4-8 weeks |
| Organic revenue | Return to pre-incident levels | 4-12 weeks |
| Core Web Vitals pass rate | Meet CWV targets | 2 weeks |
Post-incident review:
After the incident is resolved, conduct a post-mortem:
- What happened? (Timeline of events)
- Why did it happen? (Root cause analysis)
- What went well? (What worked in the response)
- What could have been better? (Response improvement areas)
- How will we prevent this in the future? (Preventive measures)
- What did we learn? (Documentation updates)
Workflow
- Detect incidents through monitoring: GSC traffic/alerts, index coverage changes, manual actions, crawl error spikes, and server monitoring. Set up automated alerting for critical thresholds.
- For traffic loss: confirm the drop (GSC + GA4), isolate the timing, segment (brand vs non-brand, device, country, page type), and diagnose the cause (technical issue, algorithm update, competitive change, or site change).
- For indexing failure: confirm the drop (GSC Indexing report), isolate the cause (robots.txt, noindex, server errors, sitemap issues), fix the root cause, request recrawl for critical pages.
- For manual actions: confirm the violation in GSC, audit for the violating practice, fix all violations, document the fix, submit a reconsideration request, and monitor the result.
- Communicate to stakeholders: what happened, why, what we are doing, expected recovery timeline, and prevention plan. Escalate based on severity: critical (>50% drop) within 1 hour, high (25-50%) within 4 hours.
- Track recovery metrics: organic traffic (return to 90%+ baseline within 4-8 weeks), indexed pages (return to baseline within 2-4 weeks), keyword rankings (return within 4-8 weeks), revenue (return within 4-12 weeks).
Common Mistakes
warning
- Delaying response to confirm whether a drop is "real": A 50% traffic drop confirmed in GSC should trigger immediate response, not a "wait and see" approach. The longer you wait, the harder recovery becomes.
- Fixing symptoms without root cause analysis: Adding more content to pages hit by an algorithm update without understanding why quality was assessed as low may waste effort. Diagnose before treating.
- Submitting a reconsideration request without fully fixing violations: A premature reconsideration request that is denied makes the second attempt harder. Complete remediation fully before submitting.
- No stakeholder communication during incidents: Stakeholders who discover a traffic drop on their own before being informed lose trust in the SEO team. Communicate proactively, even when the cause is not yet known.
- No post-incident review: After recovery, failing to document what happened, why, what worked, and what could be improved means the same incident may recur. Conduct a post-mortem after every significant incident.
Checklist
- Set up automated alerting for traffic drops, indexation drops, crawl errors, and manual actions
- Maintain documented response workflows for traffic loss, indexing failure, manual actions, migration issues, and technical outages
- Define severity levels and escalation criteria with response time targets
- Maintain a stakeholder communication plan with notification templates
- Track recovery metrics against pre-incident baselines
- Conduct a post-incident review after every significant incident
- Document root cause, response actions, recovery timeline, and preventive measures
- Update incident response playbooks based on post-mortem learnings