A sudden drop in search traffic tempts everyone to start changing things at once. That usually makes it harder to know what happened. Most drops have one of four causes, and you can tell them apart with free tools in under an hour. This lesson is the checklist, in the order that saves the most time.
1. Is the drop real?
Start by ruling out a measurement problem.
- Compare two sources. If your analytics shows a drop but Google Search Console's Performance report does not, the problem is probably the tracking, not the traffic. A missing analytics tag after a site update is very common.
- Check the dates. Compare the same period a year ago, and the same weekday last week. Many sites dip at weekends, in August and over the holidays.
- Check which search. In Search Console, compare queries before and after. If one big query fell and the rest held, the cause is that one page or topic.
2. Is something broken on your site?
Technical causes are the easiest to fix, so check them next:
- Did anything change on the site around the date? A redesign, a plugin update, new redirects or a move to a new address.
- Are important pages still indexed? Use URL Inspection in Search Console on a few of them.
- Did a noindex tag or a robots.txt rule appear by mistake?
- In Search Console, look at the Manual actions and Security issues reports. Both should say no issues detected.
If pages moved, how to change a URL without losing traffic walks through the fix. The redirect checker shows whether old addresses still reach the right page.
The full on-page checklist we use on every page, free by email.
3. Was it Google, or everyone?
If nothing is broken, compare your dates with what happened in search as a whole.
- Google's confirmed updates. Google lists its core and spam updates on its Search Status Dashboard, with start and end dates. A core update can take around two weeks to finish rolling out, and rankings often swing during that time.
- Owlcast. Owlcast measures every day how much Google's first page moved across the same set of searches. A rough day for everyone points to Google. A calm day while your traffic fell points back to your own site.
If your drop lines up with a confirmed core update, the update changed how Google judges pages like yours. It is not a penalty, and there is nothing technical to repair.
4. If it was an update: wait, then improve
The worst response to an update is rewriting everything during it.
- Wait until the rollout ends, plus a week. Many sites recover part of the drop by themselves once rankings settle.
- Compare the pages that fell with the pages that now rank above you. What do they answer better? Are they more complete, clearer, more up to date, written by someone with more first-hand experience?
- Improve the pages that matter most, starting with those that lost the most clicks. Focus on usefulness for the reader, not on keywords. The lesson search intent in plain language is a good place to start.
- Give it time. Improvements are often reflected only after the next core update.
A worked example
A recipe site loses a third of its search clicks in one week of March. Its analytics and Search Console agree, so the drop is real. Nothing changed on the site, URL Inspection shows the main pages indexed, and there are no manual actions.
The Search Status Dashboard lists a core update that started two days before the drop, and Owlcast shows a run of rough days in the same week. The cause is clear: Google re-judged pages like these.
The owner waits until the update finishes, then compares the recipes that fell with those now ranking above them. The winners show the dish being made step by step, list exact quantities and answer the common questions in the recipe itself. Those become the changes, page by page, starting with the recipes that lost the most.
Keep notes of what you changed and when. The next time traffic moves, you will know what was you and what was Google.
This is lesson 8 of the Technical SEO series. To check the health of a single page, run the free audit. For how search works end to end, see crawling and indexing.
