Website traffic dropped? Here is how I find the cause

Who this guide is for, and who should skip it

This page is for owners who can see the drop but not the reason. If you can open Search Console, you can follow every step yourself. If you would rather hand it over, the same steps are what I run in an audit. Before either, a free site scan can rule out the obvious faults on your homepage.

How owners usually describe it

The story I hear most often goes like this. The phone was busy, then it got quieter. Someone opened Google Analytics and saw fewer visitors. Nobody changed anything on purpose, or the only change was a new website that looked better than the old one. Rankings that used to sit near the top are now lower, or gone, and nobody can say when it started.

This is a common pattern, written in my own words. It is not a quote from a client.

A drop leaves marks. It has a start date, a shape, and a set of pages it hit harder than others. Those three things narrow the cause down fast. If your visitors held steady but the enquiries stopped, that is a different problem, covered in my guide to traffic that brings no leads.

Why traffic drops: the usual causes, most common first

Google Search Central lists the main causes in its own guidance on traffic drops. In practice they do not show up as often as each other. This is the order I meet them in, from most to least common, with the way I confirm each one. Shops have a few extra causes of their own, so if you sell online, also read about online stores that stopped ranking.

1. 01

   Your own site changed

   A redesign, a new theme, a platform move, or a new domain is the cause I find most often. Old pages disappear without a 301 redirect, titles and descriptions get lost in the move, internal links point to pages that no longer exist, or a staging setting such as noindex goes live by mistake.

   How I confirm it. I compare the date of the drop with the date of the change, then crawl the old URLs and check where each one lands now.

2. 02

   Google changed how it ranks pages

   Core updates and other ranking updates can move a site up or down without anything being broken. Google says a small drop in position, for example from second to fourth, often needs no action at all. A large drop across many searches calls for an honest look at the whole site, not one page.

   How I confirm it. I line the drop up with Google's published list of ranking updates and check whether the loss is spread across the site or sits in one section.

3. 03

   A technical problem is stopping Google from crawling or indexing

   Server errors, a robots.txt file that blocks too much, pages that return "not found", or a noindex tag on the wrong template can all remove pages from search. A sitewide outage shows as a cliff. A misplaced noindex shows as a slower slide, because Google only sees it as it recrawls each page.

   How I confirm it. I check the Page indexing report and the Crawl stats report for a spike that matches the drop date, then test sample pages with the URL Inspection tool.

4. 04

   People are searching less, or searching differently

   Some drops are not about your site at all. Demand for many searches rises and falls with the seasons, with holidays, or with a new trend. If everyone in your market lost interest at the same time, you did too.

   How I confirm it. I check your top lost queries in Google Trends to see whether the fall is yours alone or happens across the web.

5. 05

   The listing still ranks but fewer people click

   If impressions hold steady while clicks fall, the page is still showing but losing the click. A weaker title link or snippet, or a competitor with a richer result, is the usual reason.

   How I confirm it. I compare clicks, impressions, and click-through rate for the same pages across the two periods.

6. 06

   A manual action or a security issue

   These are less common but serious. A manual action means a person at Google found a spam policy problem. A security issue such as malware or a hacked page can make Google warn visitors before they reach you.

   How I confirm it. I open the Manual Actions report and the Security Issues report. If both are empty, this cause is ruled out in a minute.

7. 07

   The drop is in the report, not in search

   Sometimes nothing dropped. An analytics tag was removed during a redesign, a filter changed, or Google posted a data anomaly for that period.

   How I confirm it. I check Search Console against analytics, and look at Google's data anomalies page for the dates in question.

What I check, in the order I check it

Order matters. Each step rules out a cause before the next, more expensive step. It also stops the most common mistake: changing content before you know what broke. These six steps are also the first week of a full SEO audit when you would rather hand the work over.

1. Step 01

   Set the date range to the last 16 months

   In the Search Console Performance report, I look at clicks and impressions over the longest range the report allows. That shows whether the same dip happened last year at the same time.

   What this finds. Whether this is a seasonal pattern or something new.

2. Step 02

   Compare the drop with the period before it

   I compare the last 3 months with the previous period, and again with the same months a year earlier. Then I click through queries, pages, countries, devices, and search appearance.

   What this finds. Exactly where the loss sits, instead of a single scary total.

3. Step 03

   Sort pages by the clicks they lost

   Sorting the pages table by clicks difference puts the biggest losers at the top. A whole site falling points to an update or a sitewide fault. One folder falling points to a template or a section.

   What this finds. The pages to inspect first, usually a short list.

4. Step 04

   Rule out the quick causes

   I open the Manual Actions and Security Issues reports, check robots.txt, and look for noindex on the losing pages. Each takes minutes and can end the search early.

   What this finds. Penalties, hacks, and blocking rules, or proof that none apply.

5. Step 05

   Check crawling and indexing

   The Page indexing and Crawl stats reports show whether Google stopped reaching pages, and the URL Inspection tool shows what Google sees on a single page.

   What this finds. Server errors, redirect mistakes, and pages dropped from the index.

6. Step 06

   Match the timeline against changes and updates

   I put three dates side by side: when the drop started, when your site last changed, and when Google last announced a ranking update.

   What this finds. The most likely cause, with the evidence written down.

A page has to pass every stage of that pipeline before it can earn a click, starting with Googlebot finding and fetching it. When traffic falls, I work out which stage it is failing at. That is why the checks above move from reports about search results down to reports about crawling.

The drop map: read the shape before the cause

This is the part I lean on most. The shape of the line in Search Console says a lot before you open a single page. I call this reading the drop map. These are the shapes I see and what each one usually means.

The map is a first read, not a verdict. It tells me where to look. The checks then prove or disprove it. When the map points at crawling, redirects, or templates, the fix is usually technical SEO work on the site itself.

A real example from my case files

Not every loss shows up as a sudden cliff. Sometimes a site loses clicks over weeks because its own pages compete with each other for the same searches. Google cannot tell which page to show, so it shows neither one well.

That was the problem for a B2B services firm I worked with. Four regional pages targeted the same searches. I merged them into one page per intent, rebuilt their structured data, and reworked page speed. Clicks grew by +309% organic clicks, last 3 months vs the previous 3 months, view evidence, from 5.7K to 23.3K, comparing the last 3 months with the 3 months before.

What the screenshot does not prove: it shows two 3 month periods, not the exact dates, and it shows a site gaining, not recovering from an update. It is here because the cause, pages competing with each other, is one I find in many traffic investigations. The full story, with the method and the limits, is in the business services case study.

Mistakes and myths that make a drop worse

Most of the damage after a drop comes from the reaction, not the drop. These are the beliefs I hear most, and what is true. If your real worry is that AI answers are taking your clicks, that question has its own page on being missing from AI answers.

What it costs, and what changes the price

I price the work on what the site needs, not on how worried the owner is. All prices are in Pakistani rupees and come from my published price list.

Four things move the price within that range: how many pages the site has, how complicated the platform is, how many changes happened around the drop, and whether I write the fixes for a developer or make them myself. You can see every tier in my monthly SEO packages. For a rough figure before we talk, try the SEO cost calculator. If one hour is enough to point you in the right direction, book a one-off consulting call instead.

A realistic timeline, without promises

I cannot promise when traffic returns. Nobody can, because Google decides when it reassesses a site. What I can promise is what you will have in hand at each stage.

1. Week 1

   The cause, written down

   You get the drop map, the pages that lost the most, and the most likely cause with the evidence for it.

2. Month 1

   Fixes shipped

   Redirects, indexing rules, and technical faults are fixed first, because they are the fastest to take effect.

3. Month 3

   An honest read of the results

   We compare Search Console data before and after the fixes, and decide what to do next based on what moved.

Technical fixes such as a broken redirect can show results quickly once Google recrawls the pages. Recovery from a ranking update usually takes longer, because Google has to reassess the whole site over time. The ecommerce click growth case shows what a three month comparison looks like after crawl and duplicate page fixes.

Notes for businesses in Pakistan

A few things come up often with Pakistani sites, and each one is easy to check yourself.

Many retail and service searches in Pakistan rise before Eid and the wedding season and fall afterwards. Before blaming your site, open Google Trends, set the region to Pakistan, and enter your main searches. If the whole market fell, your site is not the problem.

Search Console lets you filter by country. If you sell both in Pakistan and abroad, check each country on its own. A drop that only shows in one country points to a different cause than a drop everywhere.

Many local sites are rebuilt by a developer without a list of the old URLs. Ask for that list before any redesign or migration, ask for a 301 redirect for every page that moves, and make sure the new sitemap lists only the new URLs. It is the single cheapest way to avoid the most common drop I see, and the first thing I check when website traffic dropped after a rebuild.

If you would like the same checks done for you by an independent SEO expert based in Pakistan, the audit above covers all of them.

The tools I use for this

I keep the toolkit small and use the data Google gives you for free first.

• Google Search Console for clicks, impressions, average position, indexing, crawl stats, manual actions, and security issues
• Google Analytics to check whether the drop is in search, in tracking, or in other channels
• Google Trends to separate seasonal demand from a site problem
• Lighthouse to test speed and rendering on the pages that lost the most
• My own Python scripts to compare large page lists and match old URLs to new ones

Your next step

If you want to check this yourself first, scan your homepage for free and open your Search Console Performance report with the last 16 months selected. If you would rather I find the cause for you, send me the details of when the drop started and what changed around that date. I reply within 24 hours.