Traffic drops have a diagnosis order. Rule out broken tracking, check Search Console for a manual action, read the Pages indexing report, then match your drop date against Google's Search Status Dashboard. Most declines are solved by step three.
Rule out a measurement problem first
A GA4 tag lost in a redesign looks identical to a ranking collapse on a chart. Cross-check the two sources: if Search Console clicks held steady while analytics sessions fell, your rankings are fine and your tag is gone. Five minutes here can save a week of chasing a ghost.
Check for a manual action
In Search Console, open Security and Manual Actions and look for a notice. Manual actions are rare, but this is the one cause that arrives with its own explanation and a reconsideration process attached, so it is the fastest box to tick before moving on.
Read the Pages indexing report
This is where most real answers live. Open Indexing, then Pages, and study the excluded categories over time. A climbing count under excluded by noindex tag, blocked by robots.txt, or page with redirect, timed to your drop, is your culprit. Site migrations and redesigns produce these constantly.
Match the date against Google's update calendar
Google publishes confirmed algorithm updates, with dates, on its Search Status Dashboard. If your decline starts inside an update window and the indexing report is clean, you were reassessed, not broken. That changes the fix entirely — there is no bug to find, only content and site quality to improve before the next update rolls through.
A worked example: the redesign that shipped noindex
The most common recovery case I see. A site relaunches, traffic slides over two weeks, panic sets in. The staging site carried a noindex tag to keep it out of search during development, and the tag shipped to production. The Pages report shows excluded by noindex climbing day by day. Remove the tag, request indexing on the key pages, and rankings return over the following weeks. No penalty, no mystery, one line of HTML.
Match the fix to the cause
A noindex or robots block gets removed and reindexed. A core update reassessment gets a content-quality pass on the pages that fell. Lost backlinks get reclaimed or replaced. A competitor who simply out-built you gets competed with. What never works is changing everything at once, because then you cannot tell which change mattered and you may have introduced the next problem.
Set tripwires for next time
Keep a change log of every deploy and site edit so date-matching takes minutes instead of archaeology. Glance at Search Console weekly. Crawl the site before and after any redesign. Declines will happen again; the difference between a bad week and a bad quarter is how fast you can run this same diagnosis.
Key takeaways
- Diagnose in order: tracking, manual actions, Pages indexing report, then core-update dates.
- If GSC clicks held while analytics fell, the problem is your tag, not your rankings.
- Shipped noindex tags from staging are the most common self-inflicted decline after a redesign.
- A drop inside a confirmed update window means quality reassessment; improve pages, do not hunt bugs.
Frequently asked questions
What causes most cannabis SEO declines?
Self-inflicted technical changes, especially noindex tags and robots.txt blocks shipped during redesigns, followed by core algorithm updates. The Search Console Pages report separates the two quickly.
How do I know if a Google update caused my drop?
Compare your drop date with the confirmed updates listed on Google's Search Status Dashboard. A match, plus a clean indexing report, points to reassessment rather than a technical fault.
How long does recovery take?
Technical fixes like removing a stray noindex recover over days to weeks as pages are recrawled. Core-update declines usually need real content improvements and often wait for a following update to fully rebound.
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 ›