Timecode · the first 72 hours
Your website traffic dropped suddenly. The clock started when the line on the chart fell. What you do in the next 72 hours decides whether you fix the real cause or make it worse.
Tell me how long ago it happened. The timeline jumps to your hour, marks what you should already have checked, and lights up your next move.
If your website traffic dropped suddenly, do not edit the site yet. First confirm the drop is real, then check whether Google is rolling out an update, then rule out a manual action, a security issue and a technical fault. Only after that do you look at content.
Google names six main causes of a search traffic drop: algorithm updates, technical issues, security issues, spam issues, seasonality and site moves. An update is only one of them. Most bad recoveries start with someone rewriting pages on day one for a problem that was a broken tag.
Choose a time above to find your place in the timeline. Without a choice, read from the top.
Hour 0: Hands off the site
Do nothing to the site itself. No rewrites, no plugin changes, no redirects, no deleting pages. Every change you make now becomes a second variable, and you will not be able to tell what caused what.
Do this instead: write down the time you noticed, the last change anyone made to the site, and the date range where the line falls. That note is your case file.
Hour 1: Confirm the drop is real
Many sudden drops are measurement faults. Before you believe the chart, compare two sources.
- Search Console clicks versus your analytics sessions. If Search Console is steady and analytics fell, your tracking broke. Check the tag, the consent banner and any recent theme update.
- Organic versus other channels. If every channel fell at once, look at the server or the tracking, not at Google.
- Yesterday versus the same weekday last week. Search Console data lags, and the most recent day is often incomplete.
Hour 2: Check whether Google is rolling out an update
Open the Google Search Status Dashboard and look at the ranking section. It lists every confirmed update with its start date and how long it ran. For example, it lists 2026 core updates that began on 27 March and 21 May, each taking about 12 days to finish.
If your drop lines up with the start of a rollout, that is a strong clue and also an instruction to wait. Rankings move throughout a rollout. Google’s guidance is to let the update finish, wait a further week, then compare that week with a week from before it started.
Hour 4: Rule out a manual action or a hack
These two are rare, serious and quick to check. In Search Console open Security and Manual Actions.
- Manual actions. If a human reviewer at Google has penalised the site, it is stated here in plain words with the reason.
- Security issues. Hacked content, malware or injected spam pages appear here. Also search for your own brand name plus words you would never publish. Unknown pages in the results mean you have been compromised.
If either report shows a problem, stop this timeline. Fixing that issue is now the whole job.
Hour 8: Hunt for the technical fault
By now you know the drop is real and it is not a penalty. Next, check whether Google can still reach and index your pages.
- Inspect a page that lost traffic with the URL Inspection tool. Look for a noindex tag, a blocked crawl or a canonical pointing somewhere else.
- Open robots.txt. A staging rule that blocks everything is a classic cause after a redesign.
- Read the Pages report for a jump in “not indexed” and the Crawl stats report for server errors.
- Ask what shipped. A migration, a new theme, a changed URL structure or an expired certificate in the past two weeks is a prime suspect.
Hour 24: Find out exactly what fell
A site rarely drops evenly. In Search Console, compare the week after the drop with the week before and sort by click difference.
- By page. One page, one folder or the whole site? A single folder points to a template or intent problem.
- By query. Did you lose position, or did searches fall? If impressions fell but average position held, demand dropped and nothing is wrong with your site.
- By country and device. A drop in one country or on mobile only narrows the cause quickly.
- By search appearance. Losing a rich result or a featured placement can cut clicks while rankings look unchanged.
Hour 48: Look at who replaced you
Take the five queries that lost the most clicks and search them yourself. Do not look at your own page. Look at what now sits above it.
- Same kind of page, better version? Then it is a quality gap you can close.
- A different kind of page? If guides were replaced by product pages, forums or videos, the intent of the query has shifted and rewriting your guide will not bring it back.
- An AI answer or new feature above everything? Your position may be unchanged while clicks fall. That is a click-through problem, not a ranking problem.
Toni B. reported in January 2026 that her wedding site had fallen to page 3 in the organic results. The same site still ranked in Google Maps for its main keywords and was being cited in AI answers. A drop in one surface is not always a drop everywhere, so check them separately. This is her written report, with no screenshot.
Hour 72: Decide. Fix now, or wait.
You now have enough to choose a path.
| What you found | What to do |
|---|---|
| Tracking fault | Fix the tag. There was no traffic drop. |
| Manual action or hack | Clean up, then file a reconsideration or security review request. |
| Technical fault | Fix it today and request indexing on the affected pages. |
| Demand fell | Nothing is broken. Plan for the season or the trend. |
| Update still rolling out | Wait for it to finish, then a further week, before judging. |
| Update finished, pages outranked | Improve the weakest pages against what now ranks. |
After the 72 hours: what recovery really looks like
Google is direct about this. It says improvements can take from a few days to several months to show. If a few months pass with no effect, the next core update may be the next chance. It also says there is no guarantee that your changes will produce a noticeable result.
Bryan M. saw his site hit in early September 2025. He worked on experience and trust signals on his pages. By late December his six-month Search Console view showed 14,100 clicks and 2.7 million impressions, with the line climbing again. This is from a screenshot he posted on 26 December 2025.
That is roughly three to four months from hit to visible rebound. It is one site, and I cannot prove which change caused the recovery.
The 72-hour checklist
- Hour 0: change nothing and start a case file.
- Hour 1: compare Search Console with analytics to confirm the drop.
- Hour 2: check the Search Status Dashboard for a rollout.
- Hour 4: check Manual Actions and Security Issues.
- Hour 8: inspect URLs, robots.txt, the Pages report and recent releases.
- Hour 24: segment by page, query, country, device and search appearance.
- Hour 48: search your lost queries and study what replaced you.
- Hour 72: choose one path from the table and commit to it.
Sources
- Google Search Central: Debugging drops in Google Search traffic
- Google Search Central: Core updates guidance
- Google Search Status Dashboard: ranking update history
- Member results: posts in the SearchGAP Method community Results tab, dated as shown. Members are named by first name and initial.
If the 72 hours end with “my pages were outranked”, the fix is finding queries where you can still win. That is what we work on inside SearchGAP Method.
See SearchGAP Method