First-hour triage for a sudden traffic drop

By the SEO Fire Fighter Wiki editors · Published 31 October 2026 · Last updated 31 October 2026

Short answer: In the first hour, confirm the traffic drop is real, widen the date range, then check for a manual action, a security issue, a recent site change, indexing errors and an overlapping Google update, and write down the findings before changing anything. ^[1][2][3][6]

What should be checked, in order?

The ten checks below draw on Google’s guidance and take about an hour for a small site. Each is something to look at, not something to change.

1. Confirm the drop is real. Open the Search Console Performance report and check the Search Console Data Anomalies page; the drop may be a reporting or logging issue.^[1]
2. Widen the date range. Set the range to 16 months to see whether the same dip happened a year ago, which would suggest seasonality.^[1]
3. Compare before and after. Use the Compare tab to compare the drop period with the previous period or the same period last year, across queries, pages, countries and devices.^[1]
4. Check for a manual action. Open the Manual actions report. A listed action explains a sudden, site-wide drop and has its own fix path.^[2]
5. Check for a security issue. Open the Security issues report. Hacked content, malware or social engineering can cause warnings and a traffic fall.^[3]
6. Look for a site change. Ask what shipped just before the drop: a deployment, plugin update, migration or robots.txt or noindex change.^[1]
7. Inspect affected URLs. Use the URL Inspection tool on a few lost pages to see whether Google can crawl and index them.^[4]
8. Check the Page indexing report. For a site-wide drop, look for a spike in pages not indexed and the reasons given.^[5]
9. Match dates to Google updates. Check the Search Status Dashboard for ranking updates that overlap the drop and note their start and end dates.^[6]
10. Record findings, then decide. Write down what was found. If the drop is a small shift in position, Google advises avoiding radical changes.^[1]

What should not be done in the first hour?

• Do not delete content. Google calls deleting content a last resort, and says it should be considered only if the content cannot be salvaged.^[7]
• Do not make quick-fix changes because someone says an element is bad for SEO.^[7]
• Do not upload a large disavow file. Google says most sites do not need the tool and that it can harm performance if used wrongly.^[8]
• Do not remove an existing noindex tag or robots rule before recording it. Evidence of what was in place is useful, and the technical failures page explains why.^[9]

What happens after the first hour?

The pattern of the findings decides the path. A whole-site drop on one date leads to traffic drop diagnosis; a message in Search Console leads to manual actions or hacked sites; and a drop that matches an announced update leads to core updates.^[1]

See also

• Emergency SEO
• Traffic drop diagnosis
• Manual actions
• Core updates
• Bad links and disavow

References

1. ^ ^{a b c d e f g} “Debugging drops in Google Search traffic”. Google Search Central. Retrieved 31 October 2026.
2. ^ ^{a b} “Manual Actions report”. Google Search Console Help. Retrieved 31 October 2026.
3. ^ ^{a b} “Security Issues report”. Google Search Console Help. Retrieved 31 October 2026.
4. ^ “URL Inspection tool”. Google Search Console Help. Retrieved 31 October 2026.
5. ^ “Page indexing report”. Google Search Console Help. Retrieved 31 October 2026.
6. ^ ^{a b} “Google Search Status Dashboard: Ranking”. Google Search Central. Retrieved 31 October 2026.
7. ^ ^{a b} “Google Search’s core updates”. Google Search Central. Retrieved 31 October 2026.
8. ^ “Disavow links to your site”. Google Search Console Help. Retrieved 31 October 2026.
9. ^ “Block Search indexing with noindex”. Google Search Central. Retrieved 31 October 2026.