SEO Incident Response
When organic traffic or rankings fall sharply, the first few days matter. My role is to establish what actually changed, separate cause from noise, and give your team a clear first set of actions.
Drops after a release, migration or redesign. Indexing and rendering failures. Broken redirects or internal linking. Crawl disruptions. Search engine updates. And occasionally a tracking change that looks like a traffic loss, which is worth ruling out on the first day.
| Day 0 | We agree the scope, review the reported drop and its timing, and you share access. |
|---|---|
| Days 1–2 | I work through Search Console, crawl data, logs, release history, rendering and internal linking to isolate the likely causes. |
| Days 2–3 | You receive a written brief: what is confirmed, what has been ruled out, what is still under investigation, and what your technical owner can start on immediately. |
| Weeks 1–2 | Optional. If the incident points to a deeper structural problem, the work can extend into a short recovery engagement. |
- Search Console access, or exports showing what dropped, when, and on which page types.
- Server logs where available. They make crawl and status-code problems much easier to verify.
- Release notes and deployment history for the period, including template, redirect, CDN and configuration changes.
- Analytics access, to confirm the scale and shape of the drop.
- One technical owner who can answer questions and run quick checks.
I can work quietly with a small internal group without being visible across the organization. Where an agency or consultant already leads the account, I can also support them behind the scenes, under their name.
Use the incident form, which asks for the details I need to start, or message me on LinkedIn. Incidents are prioritized.