Menu
Scan my site freeWhatsApp Usman
+92 340 8747609contact@malikusman.me

Fix guide covering the whole topic

Why your website traffic dropped, and how to find the cause

When traffic drops, change nothing yet. Confirm the drop is real and comes from Google search, find the date it started, and see which pages and searches lost clicks. The date and the pattern point to one of a few causes: a site change, a tracking fault, a Google update, a manual action, the season or a competitor.

By Published 14 min read
On this page

This guide is for you if

  • Clicks or sessions fell sharply over a few days
  • Traffic slid down slowly over several weeks
  • One section of the site lost traffic and the rest did not
  • Rankings look the same but visits are lower

A sudden fall in traffic feels like an emergency, and the natural reaction is to start changing things. Resist it for a day. The fastest way to recover is to find the real cause first, and changes made in a panic hide the evidence you need.

This guide is the method I use when someone tells me their traffic fell. It works for a ten page business site and for a store with thousands of products. Work through it in order, write down what you find at each step, and by the end you will either know the cause or have narrowed it to one or two.

What to take from this

  • Confirm the drop in Search Console before you trust Analytics. Many drops are tracking faults.
  • The start date is the most useful clue. Match it to site changes first, Google updates second.
  • A drop across every page points to a site-wide cause. A drop on a few pages points to those pages or their searches.
  • Do not rewrite content or disavow links before you know the cause. Wrong fixes can deepen the drop.

Step 1: confirm the drop is real

Before anything else, check that traffic really fell, and that it fell from Google search.

Open Google Search Console and go to the Performance report. Set the date range to the last six months and look at clicks and impressions. Search Console counts clicks from Google search directly, so it does not depend on a tracking code on your site.

Then compare it with Google Analytics. If Analytics shows a big drop and Search Console does not, the problem is almost always tracking, not search. The usual culprits are a tracking code removed during a redesign, a consent banner that blocks Analytics until the visitor accepts, a second tracking code that double counted before and stopped, or a filter added to the Analytics property.

If both show the drop, it is real. Check which channel it came from in Analytics: organic search, direct, referral, social, paid. A drop in paid or social traffic is not an SEO problem, even if it shows up in the same total.

Step 2: find the exact start date

The date is the single most useful clue. Change Search Console to show daily data over the last three months and find the first day clicks fell below their normal level.

Look at the shape:

  • A cliff, where clicks fell by a large amount over one to three days, usually means something changed: on the site, in Google's systems or with a manual action.
  • A slope, where clicks slid down over several weeks, usually means competition, a slow loss of rankings, or demand falling with the season.
  • A step, where clicks dropped to a new level and stayed flat there, often means a section of the site stopped being indexed, or a set of pages lost a rich result or a feature.

Write the date down. Every step below uses it.

Step 3: list what changed on your site around that date

Before blaming Google, check your own changes. Ask everyone who touches the site, and look at these:

  • A redesign, new theme or new platform.
  • A migration to a new domain, HTTPS, or a new URL structure.
  • Plugin, app or theme updates.
  • Changes to robots.txt, the sitemap or the SEO plugin settings.
  • Pages deleted, merged or renamed.
  • Hosting changes, a new CDN, a new firewall or bot protection.
  • Changes to the menu or internal links.

Site changes are behind a large share of sudden drops, and they are the easiest to fix because you know exactly what to reverse. A redesign that dropped redirects or set pages to noindex can be repaired in a day. If a site move is behind the drop, my migration checklist lists what usually goes wrong.

Step 4: check for technical faults

If nothing obvious changed, check whether Google can still reach and index the pages that lost traffic.

Open the Pages report in Search Console. Look at the indexed count over time. A sharp fall in indexed pages that lines up with your drop is a strong sign of a technical cause. Read the reasons for pages not indexed and look for spikes in "excluded by noindex tag", "blocked by robots.txt", "server error (5xx)" or "redirect error".

Then inspect a few of the pages that lost the most clicks with the URL Inspection tool. Check that the page is indexed, that the canonical Google chose is the one you expect, and that the rendered HTML still contains the main content.

Also check the Crawl Stats report, under Settings. A sudden rise in server errors or a drop in crawl requests can mean the server, a firewall or bot protection started blocking Google.

The full list of technical checks, in the order I run them, is in my technical SEO checklist.

Step 5: check for a manual action

Open the Manual Actions report in Search Console. If it says "no issues detected", you can rule this out. If it lists an action, you have your cause: a human reviewer at Google found something against its spam policies, such as unnatural links, thin content or cloaking.

Manual actions are rare compared with algorithm changes, but they are important to rule out because they need a specific fix and a reconsideration request. The differences between a manual action and an algorithm drop, and what each one needs, are in manual action or algorithm drop.

Check the Security Issues report too. A hacked site can lose traffic quickly, and Google may show a warning in search results.

Step 6: check for a Google update

If the site did not change, the technical checks are clean and there is no manual action, look at Google's side. Google lists confirmed ranking updates on the Google Search Status Dashboard. Core updates roll out over a week or two, so the drop can start on any day within the rollout.

A drop caused by a core update usually looks like this: it starts during a confirmed rollout, it affects many pages and many searches rather than one, and the pages lost rankings rather than disappearing from the index.

Core updates are not penalties. Google re-evaluates how useful pages are compared with others, and some pages move down because others moved up. Recovery usually means improving the pages, then waiting for a later update. What to look at, and what not to do, is in checking whether a core update hit you.

Step 7: see which pages and searches lost clicks

Now use Search Console to find where the loss sits. In the Performance report, use the compare option: the four weeks after the drop against the four weeks before. Sort the Pages tab by the difference in clicks, then do the same on the Queries tab.

The pattern tells you a lot:

What lost clicksWhat it usually means
Every page, roughly evenlyA site-wide cause: technical, an update or a manual action
One folder or one page typeA template change, or that section stopped being indexed
A handful of pagesThose pages lost rankings, often to a competitor or a fresher page
Brand searchesFewer people are searching your name, which is a demand or reputation issue
Searches with a questionAn AI Overview or a new feature may now answer them on the results page

Look at average position too. If position held steady but clicks fell, something above you on the page changed: an AI Overview, more ads, a map pack or a featured snippet taken by someone else. That is a different problem from losing rankings.

If you track rankings with a third party tool and it disagrees with Search Console, trust Search Console for this step. I explain why the two differ in rank trackers against Search Console.

Step 8: rule out demand and competitors

Some drops have nothing to do with your site. Check two more things.

Demand. Open Google Trends for your main searches. If interest fell at the same time as your traffic, people are searching less. Seasonal businesses see this every year. Comparing the same months last year in Search Console tells you whether the drop is normal for the time of year.

Competitors. Search your main terms and look at who now ranks above you. A new competitor, a big brand that entered your market, or a rival that rebuilt its pages can take clicks without anything wrong on your side. Note what they offer that you do not.

Drops that look like SEO but are not

A few causes look like a search problem in the reports and have nothing to do with rankings. Rule them out before you spend money on SEO.

A change in how Analytics counts visits. Moving to a new Analytics property, adding a cookie consent tool or changing how sessions are defined can cut the reported numbers overnight. Search Console will not show the same fall.

A change in your own marketing. If you stopped a newsletter, paused ads or ended a social campaign, some people who used to search your brand name after seeing it may no longer do so. Brand searches fall, and so do clicks.

A problem with the business. A closed branch, a product out of stock for weeks, bad press or a run of poor reviews can all reduce searches for your name or clicks to your pages.

Bot traffic that stopped. Some sites have inflated numbers from bots or spam referrals. When those stop, or when you filter them, the total falls. That is a correction, not a loss.

A holiday or event. Eid, Ramadan, exam season, elections and big cricket matches all shift what people in Pakistan search for and when. Compare with the same period last year before deciding anything.

How to read Search Console during a drop

Search Console has a few features that make diagnosis much faster once you know where they are.

Compare mode. In the Performance report, the date picker has a Compare tab. Choose the four weeks after the drop and the four weeks before, and every table gains a difference column. Sort by it.

Filters by page and query. Click a page in the Pages tab, then switch to the Queries tab. You now see only the searches that page gets. Do the reverse to see which pages rank for one search. This is how you find whether a page lost all its searches, or one search lost its page.

Search appearance. This tab shows clicks from rich results, such as review stars or FAQ snippets. If one of these vanished on the drop date, you have found part of the cause.

Country and device. Filter by country to check whether the drop is in one market. Filter by device to see whether mobile and desktop fell together. A drop only on mobile points to a mobile rendering or speed problem.

Annotations and the Insights report. Search Console shows notes for some Google-side events on the chart. The Insights view gives a simpler summary of which pages are trending up and down.

Write your findings down as you go

Diagnosis takes a few hours spread over a day or two, and it is easy to lose track. Keep a short document with one line per finding: the date, what you checked, what you saw, and what it suggests. For example: "Pages report, indexed pages fell from steady level on the 14th, same day as theme update. Suggests template change." Add screenshots.

That document does three jobs. It stops you checking the same thing twice. It lets someone else, a developer or a consultant, pick up the work in minutes. And it becomes the first entry in the change log you will keep from now on. When you reach a conclusion, write that down too, with the evidence for it and anything that does not fit.

How to tell the cause from the pattern

Bringing it together, here is how the evidence usually lines up:

  • Drop matches a site change, indexed pages fell, errors rose: technical cause. Reverse or fix the change.
  • Analytics fell, Search Console did not: tracking fault. Fix the tracking code.
  • Manual Actions report shows an action: manual action. Fix the issue, file a reconsideration request.
  • Drop during a confirmed update, many pages, no site change: core update. Improve content and wait.
  • Gradual slide, competitors moved up: competition. Improve the pages that lost most.
  • Same drop at the same time last year: season. No fix needed, plan around it.
  • Position steady, clicks fell: results page changed. Work on titles, snippets and being cited in AI answers.

What to fix first

Fix in order of certainty. If a technical fault is confirmed, fix that before touching content, even if an update rolled out the same week. Technical fixes recover fastest and are easy to verify.

If the cause is a core update, start with the pages that lost the most clicks, not the whole site. Read them as a stranger would, next to the pages that now outrank them, and look for what is missing: first-hand detail, current information, a clear answer, proof. Older pages that slipped are often the best place to start, and the method for those is in refreshing pages that slipped.

What not to do

Some reactions to a drop make it worse.

Do not delete pages in bulk. Removing pages because they lost traffic can remove the internal links and topical depth that the rest of the site relied on. Decide page by page.

Do not disavow links at random. Unless you have a manual action for links, or you know you bought spam links, disavowing is unlikely to help.

Do not change titles, URLs and content all at once. If you change everything, you will not know what worked, and you may introduce new problems.

Do not trust a single day. Search data is noisy. Compare weeks, not days.

A drop I helped reverse

One business services firm had four regional service pages competing for the same searches, and Google kept switching between them. After the pages were merged into single pages by intent, the schema was rebuilt and page speed improved, organic clicks rose by comparing three months with the three months before. Several changes went live together, so the result cannot be credited to one of them. The full write-up is in a recovered drop.

The lesson from cases like that one is the same as the method above: find which pages lost and why, before you fix anything.

Keep a change log from now on

The hardest drops to diagnose are on sites where nobody remembers what changed. Start a simple log today: the date, what changed, who changed it. Include plugin updates, new pages, deleted pages, menu changes and hosting changes. Add Search Console annotations if your tools support them.

The next time traffic moves, you will be able to match the date to a change in minutes instead of days. A shared spreadsheet that everyone who touches the site can edit works well, as long as people actually use it. Review it whenever you look at your monthly reports, so the habit sticks. I explain how to read the Performance and Pages reports together in my guide to Search Console.

When to bring someone in

You can work through this method yourself with Search Console and a few hours. Bring someone in when the evidence points in two directions at once, when the drop is large and costing you money every day, or when you have found the cause but are not sure how to fix it without making things worse.

My traffic drop diagnosis page explains what I look at, what I need from you and what you get at the end.

Questions people ask

Why did my website traffic drop suddenly?

The most common causes are a change to the site, such as a redesign, migration or plugin update, a broken tracking code, a Google core update, a manual action, or a seasonal fall in demand. The date the drop began usually tells you which.

How do I know if a Google update caused my traffic drop?

Check whether the drop started within a few days of a confirmed update on the Google Search Status Dashboard, whether nothing changed on your site at that time, and whether the loss is spread across many pages and searches.

How long does it take to recover from a traffic drop?

A technical cause can recover within weeks of the fix, once Google recrawls the pages. Drops from core updates often take months, and recovery usually comes with a later update after the site has improved.

Should I disavow links after a traffic drop?

Only if you have a manual action for unnatural links, or you know you built spam links in the past. Disavowing at random rarely helps and can remove links that were doing you good.

, independent SEO consultant

I work alone from Pakpattan, Punjab, on technical SEO, local search, ecommerce structure and content clean ups. I write and check every post on this blog myself.

Last reviewed 3 November 2026. How I write and check these posts