A Google core update
Content judged less helpful or less trustworthy than competing pages, often because of thin or outdated pages.
A sudden drop is stressful, and guesses make it worse. I work out whether the cause was a Google update, a technical fault, a penalty, a migration or a content problem, then lay out the recovery in the order that makes sense.
4.9/5 from 81 reviews · Diagnosis first, fixes second
Get a free first look
Send your website. I will reply myself with what I see and what I would fix first.
or
Chat on WhatsAppA traffic drop has a cause, and the fix depends entirely on which cause it is. A manual penalty, an algorithm update, a broken redirect, a noindex tag left on by mistake, a slow server and a competitor overtaking you all look the same on a traffic chart.
I begin by dating the drop and matching it to what changed: a Google update, a site release, a plugin change, a migration. Then I look at which pages and queries lost the most. The pattern usually points to the cause quickly.
Recovery then follows that diagnosis. It may be a technical SEO repair, a rewrite of thin or outdated pages with content SEO, or a clean-up of risky links. I tell you honestly when a drop is a normal fluctuation and no action is needed.
Content judged less helpful or less trustworthy than competing pages, often because of thin or outdated pages.
Pages accidentally blocked, noindexed, redirected wrongly or knocked offline.
Lost URLs, changed content and broken internal links after a move.
A direct penalty shown in Search Console, usually for spam, unnatural links or similar.
Rivals who published better pages or earned more authority while yours stood still.
The first question is whether the drop is real. I compare Search Console clicks and impressions with the same weeks last year and check that tracking has not broken, because a changed analytics tag can look exactly like a collapse.
Next I line the date of the drop up with known events: a Google core update, a site migration, a template change, a robots.txt or noindex mistake, or a hosting move. A fall on a single day usually points to something technical or a manual action. A slow slide over several weeks more often means that content has been overtaken or that quality signals are weak.
Then I check for manual actions in Search Console, which are the only penalties Google reports to you. If there are none, the cause is almost always an algorithm change or a technical fault, and the fix is different in each case. I also split the loss by page type, country, device and group of searches, because a fall concentrated in one section tells you exactly where to look.
Only after that do I plan fixes. Recovering from a core update rarely comes from one trick. It means improving the pages that lost, usually by making them more useful, more trustworthy and more clearly written, and then waiting for Google to reassess them. That can take weeks, or until the next update, so I will not promise a date. What I can promise is that you will know the cause, the plan and what changed each month.
I compare periods in Search Console and analytics to see exactly when and where traffic fell.
Update dates, release logs and crawl data help identify what changed.
Manual actions and security issues are ruled in or out first.
Repairs and improvements are ranked by likely impact and effort.
We follow impressions, clicks and rankings, and I adjust the plan if the data says so.
If the drop followed a move, see site migration. For a wider health check, start with an SEO audit. To understand why rivals now outrank you, a competitor analysis shows what they did differently.
Send me your site and roughly when the drop began. I will give you a first read on the likely cause.
No obligation · Reply from Nazirul Islam Nakib himself
Nazirul Islam Nakib