Skip to content
Stacked translucent data layers with a violet scan-line sweeping across them, coral markers along the edge

Diagnosis

Traffic dropped after a Google update? How to tell what happened first

Ilyes Massoudi7 min read

The short answer

A traffic drop has four possible causes, and you rule them out in order: a recent technical error (a new deployment, a noindex, a broken redirect), a season or a shift in demand, a Google core update that re-evaluated your site, or a manual action. Open the Performance report in Search Console, pin down the exact date of the drop, then compare it with Google's published update dates. A gradual drop on weak informational pages means an update; a sharp drop in a single day means a technical error or a manual action. Change nothing before you know.

Rule one: do not fix before you know

The most dangerous thing a site owner does after a traffic drop is change many things in one week: rewrite pages, delete others, buy links, switch the theme. They then never learn what caused the drop or what stopped it.

Diagnosis precedes repair, and it takes an hour with one free tool. The four causes below are ordered by likelihood, and each leaves a different fingerprint in the Performance report.

Step one: pin down the date and the shape of the drop

Open the Performance report in Search Console, filter by your country, and extend the range to six months. Look at the impressions and clicks curves together:

  • A sharp drop in one or two days. Points to a technical error or a manual action.
  • A drop over one to two weeks, then a plateau at a lower level. The fingerprint of a core update.
  • A gradual decline over months. A competitor advancing, content ageing, or a season.
  • Clicks falling while impressions hold. You are not losing visibility but the click: weaker titles, or an AI Overview above you.

Then ask: which pages dropped? If all of them, the cause is site-wide. If only the informational pages, look at the updates. If a single page, check it technically.

Cause one: a recent technical error

The most common and the easiest. Ask whoever runs the site: what changed in the week before the drop? A new deployment, a theme change, a hosting migration, a new plugin, a URL change.

The checks: the Pages report in Search Console for pages that suddenly became unindexed, URL Inspection for the most important dropped page, the robots.txt file, and the Crawl Stats report for server errors. The usual culprits: a noindex tag deployed by mistake, redirects broken after a URL change, or a canonical pointing to the wrong version.

Cause two: the season and demand

Gulf demand is more seasonal than site owners assume: Ramadan changes all behaviour, summer empties the cities, and back-to-school and the Hajj and Umrah seasons move entire sectors.

The check: compare the same period last year, not last month. And look at impressions: if impressions fell while position held, people are searching less, and that is not your problem.

Cause three: a Google core update

Google releases core updates several times a year and announces their dates. An update re-evaluates every site against quality standards: experience, usefulness, specificity, and the absence of mass-generated content.

Its fingerprint: a drop starting on the update date or a day or two after, lasting one to two weeks, and hitting informational and weak pages more than service pages.

What it means: Google did not penalise you; it found that other pages answer better. The fix is not technical but editorial: delete or merge what says nothing, and rewrite what deserves it with real experience, examples and numbers. Details in the AI content article. Recovery usually comes at the next update, not the next week.

Cause four: a manual action

Rare but decisive: links bought in bulk, mass-generated content, or a hack. The Manual Actions report in Search Console states it explicitly, with the reason and the steps to request a review.

The check takes a minute. If the report is empty, rule this cause out and do not return to it.

The diagnosis table

Fingerprint Likely cause Check Fix
Sharp drop in a day Technical error or manual action Pages report, Manual Actions Fix the error, request a review
Two weeks then a plateau Core update Compare with the update log Delete and rewrite, then wait
Gradual over months A competitor or ageing content Competitor analysis Update the important pages
Impressions hold, clicks fall Titles or AI Overviews Performance report by query Rewrite titles and first paragraphs
Same period last year was lower too Season Year-on-year comparison Nothing

What not to do

  • Do not buy links to “compensate” for the drop; that turns a drop into a manual action.
  • Do not delete pages before you know which ones dropped and why.
  • Do not change the theme or the URLs during diagnosis.
  • Do not believe anyone offering “ranking recovery within a week”; nobody can do that after a core update.

When you need help

If you have pinned the date and found no cause on the list, or found more than one overlapping cause, that is what the Digital Presence Audit diagnoses: a page-by-page reading of Search Console data, a comparison with the update dates and with your three competitors, then an ordered plan that starts with what brings enquiries back first rather than with what looks urgent.

Common questions

Does Google penalise sites in updates?
A core update is not a penalty; it is a re-evaluation of every site against updated standards. A site that drops has broken no rule; Google has found other sites that answer better. The real penalty is a manual action, and it appears plainly in its own report in Search Console with the reason.
When does a site recover after a core update?
Usually at the next core update, months later, and only if the site has genuinely changed. Small fixes a week later do not restore rankings. The sites that recovered are the ones that deleted or rewrote what was weak, added real experience, and then waited.
How do I find the dates of Google updates?
Google publishes an official log of ranking updates with the start and end date of each. Compare the date of your drop with that log. A drop that began on the same day or within two days points to the update; a drop two weeks later does not.