The goal is to be told about a drop, then diagnose it in a fixed order: rule out seasonality, check for a core update, then look at your own site. Set up an alert so you are not relying on memory, and most of the panic disappears once you know which of the three it is.
Automate the alert so you are not watching manually
The drops that turn into disasters are almost always the ones nobody noticed for weeks. Relying on remembering to open a dashboard fails exactly when you are busy. So automate the nudge. Search Console will email you when it flags issues, and you can schedule a GA4 email or a Looker Studio alert that pings you when organic traffic falls a set amount week over week. You do not need anything clever, just something that reaches you without being asked. Being told on day two instead of noticing on day thirty — that is the entire game.
Rule out seasonality first
Before assuming something broke, compare the drop to the same period a year ago. Cannabis search is unusually seasonal. It spikes hard around 4/20 and major holidays and then sags for weeks afterward, and if you only look at last month you will read that normal comedown as a catastrophe. Year-over-year is the honest comparison. A dip that mirrors last year's post-holiday pattern is demand doing what demand does, and no fix is needed. A dip that runs well below the same weeks last year is a real signal worth chasing.
Check the Search Status Dashboard for updates
Once seasonality is ruled out, check the timing against Google's Search Status Dashboard, which publicly lists confirmed ranking and core updates with their rollout dates. If your decline lines up with a core update that was rolling out, the cause is almost certainly algorithmic rather than something you did that week. This single check saves enormous wasted effort, because the response to a core update, improving overall content quality over time, is completely different from the response to a technical break, and you want to know which you are dealing with before you start.
Separate a penalty from an algorithm shift
People say "penalty" for any drop, but a true penalty is a manual action, and Search Console tells you plainly whether you have one in the Manual Actions report. If that report is clean and your drop matches an update date, you are looking at an algorithm change, not a punishment. If there is a manual action, that is your answer and your fix. Checking Manual Actions early stops you from treating an algorithm shift as a penalty or the other way around, which sends you down the wrong path for weeks.
Then look at your own site
If it is not seasonal, not an update, and not a manual action, turn to what changed on your end. A recent redeploy that added a stray noindex tag, a robots.txt edit, a site migration, a template change that stripped internal links, all of these quietly tank traffic and all show up in Search Console's Pages report or URL Inspection. Line up the drop's start date against your own change log. Traffic that fell the day after a deploy is rarely a coincidence.
A worked example
A dispensary owner saw organic sessions down 35 percent in early May and assumed a penalty. Year-over-year told the first half of the story: the same drop happened the previous May, the natural comedown after 4/20. But part of the decline was larger than last year, so they kept going, checked the Search Status Dashboard, and found a core update had finished rolling out mid-April. Manual Actions was clean. So the answer was seasonality plus a core update, neither of which is an emergency — and neither of which is fixed by panicking. They planned steady content improvement and let the seasonal traffic return on its own.
Frequently asked questions
How do I get alerted to a traffic drop early?
Search Console can email you when it detects issues, and you can build a scheduled email or Looker Studio alert off GA4 for a week-over-week organic decline. The point is to be told, not to remember to look. Most drops that become disasters are ones nobody noticed for a month, so an automated nudge is worth setting up.
How can I tell a core update from a penalty?
Check the timing against Google's Search Status Dashboard, which lists confirmed ranking updates and their dates. If your drop lines up with a core update rollout, it is almost certainly algorithmic, not a penalty. A true penalty shows as a manual action in Search Console. If Manual Actions is clean and the date matches an update, you are looking at an algorithm shift.
Is my seasonal dip a real problem?
Compare against the same period last year before you worry. A lot of cannabis search is seasonal, spiking around 4/20 and holidays and sagging afterward, so a post-holiday dip that matches last year's pattern is just demand, not a ranking loss. If the drop is far below the same weeks a year ago, then it is worth investigating as a real decline.
Key takeaways
- Automate an alert so a drop reaches you instead of waiting to be noticed.
- Rule out seasonality with a year-over-year comparison before panicking.
- Match the drop date to the Search Status Dashboard to spot core updates.
- A real penalty is a manual action; check that report to tell them apart.
Want this done for your brand?
We build cannabis & CBD search visibility with full transparency, for dispensaries, brands, and MSOs.
Get a free cannabis SEO audit ›