Why is my website traffic dropping? A checklist to find the cause

Start here: the order to check

Work top to bottom. Each step is cheap and rules out a cause before you spend time on a harder one. Do not change anything on the site until you know which one you are looking at, because a change made in a panic can bury the evidence.

1. Check that your tracking did not break

A sudden drop in website traffic that shows up in your analytics but nowhere else is often not a drop in visitors. Your analytics counts only what its script records, so anything that stops the script running makes traffic vanish from the report while people keep arriving.

Compare two sources for the same dates and pages: the visits your analytics attributes to Google organic search, and the clicks in Search Console's Performance report. They will not match exactly. But if organic visits in analytics fall by half on a Tuesday and Search Console clicks are flat, look at the tracking first. Check other channels, such as an email or paid campaign that ended, separately, since they can lower total visits without touching Google clicks.

• The tag was removed or changed. A theme update, a plugin swap or a redeploy can drop the script from some or all pages. View the source of a few pages and look for it.
• A consent banner started blocking it. If the script now waits for consent, everyone who does not click accept is missing from the report. Our Google Analytics and GDPR guide covers how consent changes what is counted.
• A filter or setting changed. An internal-traffic or data filter applied by mistake can hide real visits. Check recent changes to the analytics property.
• Blockers catch more of the script. Visitors who block the tracker are never recorded, so a change in browser or blocker behaviour moves your numbers without moving your audience.

Open your analytics real-time report in one tab and visit your own site in another. If you do not appear, check the tag, but first make sure your browser is not excluded by a consent setting, blocker or internal-traffic filter. If you do appear, that only shows tracking works on that page today: test an affected published page too, and look at the network requests for the script. Stickybeak's own install check does a similar job for its script. Once tracking looks fine, treat the drop as real and use the checks below. For the basics of reading these numbers, see how to check website traffic.

2. Find which traffic fell

Once the drop is real, narrow it before you theorise. Split the loss by channel, then by page, then by country and device, and write down where the biggest piece sits.

• By channel. If only organic traffic fell, the cause is in search. If direct traffic or referral traffic fell too, look at tracking, campaigns or a site that used to link to you.
• By page. A loss concentrated on a few pages tells you which pages to investigate: check their indexing, availability, impressions and position before deciding they were outranked. A loss spread evenly over every page points more to a technical or sitewide cause.
• By device or country. A fall on mobile only, or in one country only, points at a rendering problem, a redirect rule or a regional change in results.
• By date. Note the exact day it started. Every cause below is matched against that date.

If you use Stickybeak, filtering by referrer, page, country or device is a click on the dashboard, and you can pin a note to the chart on the day you shipped a change. See annotations.

3. Compare the date with Google's ranking updates

Google changes how it ranks pages all the time, and it publishes the larger changes on the Google Search Status Dashboard. Its traffic-drop documentation lists algorithmic updates as the first possible cause. As of 17 October 2026 the dashboard lists these recent updates:

To use the list, take the exact day your search clicks started to fall and see whether an update was rolling out then. Because rollouts run for days or weeks, a fall that begins inside the window is a candidate cause, not proof. Three things make it more likely:

• Only search traffic fell. Direct, email and referral traffic held.
• The fall is spread over many queries, not one page.
• You found no technical problem in steps 1 and 5.

Read what the update was about on the dashboard entry before you act. If a spam update lines up with your drop, check the Manual actions and Security issues reports described in step 6. This guide does not tell you how to recover from a specific update, because the right fix depends on what that update targeted.

4. Look for pages that lost their rankings

Most traffic drops that are not tracking or a sitewide fault come down to a few pages that now rank lower for the searches that used to bring people in. Search Console's Performance report keeps 16 months of data and lets you compare date ranges, so it can show this directly.

1. Set a comparison. Compare the weeks after the drop with the same number of weeks before it.
2. Group by page. Sort by the change in clicks. Note the few pages that account for most of the loss.
3. Open each page and group by query. See which searches lost clicks, and whether impressions or average position fell.
4. Read the pattern. Position fell and impressions held: you were outranked. Impressions fell with position steady: fewer people searched. Position and impressions held but clicks fell: something on the results page changed, for example a new answer or feature above your listing. That is a reading of the numbers, not something Search Console labels for you.
5. Search the query yourself. See who ranks now and what they cover that your page does not.

Some searches now show an AI-written answer above the results. If your impressions held and your clicks fell on informational queries, that is one possible reason; you can only confirm it by looking at the results page for those queries.

5. Rule out a change to your own site

Google's documentation names technical issues, site migrations and URL changes as causes of drops, including a stray noindex tag on pages that should be indexed. If your drop began the day you released something, start here.

• noindex or robots.txt. A noindex tag, or a robots.txt rule blocking a section, can remove pages from results. Check a few affected pages with the URL Inspection tool, and test your file with the robots.txt checker.
• Redirects and URL changes. If URLs changed, old ones should redirect to the matching new page. Google says rankings can fluctuate while it recrawls and reindexes after a migration.
• Indexing and crawling. Search Console's Page indexing report shows pages that dropped out of the index and why. The Crawl stats report shows whether Google could fetch your site.
• Outages and slow pages. Check your host's logs for the date.

Keep a deploy log or add a note to your chart on every release, and this step takes a minute instead of an afternoon.

6. Check security issues and manual actions

Google's documentation lists malware, phishing and spam violations as causes of drops. Two Search Console reports cover them: Security issues for hacked content, malware or phishing, and Manual actions for spam penalties applied by a person at Google. If either shows a problem, that is the cause to fix first, because it can affect the whole site.

7. Allow for seasonality and changing interest

Some topics rise and fall every year, and some fade. Google lists seasonality and changing interests as a cause of lower traffic, and Google Trends shows whether searches for your topic fell for everyone or only for you. Compare the same weeks last year. If last year dipped the same way, it is probably demand, and the right response is to wait and plan for it, not to rewrite pages.

Do not treat this as the default explanation, though. It is easy to blame the calendar, and it is the one cause that requires you to do nothing, so check it after the others.

Put the evidence together

Most drops end up in one of three shapes. Match yours, then act on that cause only.

A fall can have more than one cause at once, and Search Console data arrives with a delay, so recheck after a few days before concluding. Do not publish a rewrite of every page to fix a drop you have not diagnosed.

Where Stickybeak fits

Stickybeak is live analytics for every site you own, and it is in early access. It does not replace Search Console, which reports your Google Search clicks, impressions and average position. It helps with the analytics half of a drop:

• Narrowing it down. Filter by referrer, page, country or device to see where the loss sits.
• Dating the change. Pin an annotation to the chart when you ship something, by hand or from a deploy script, so the date is on the chart when you look back. See annotations.
• Telling real visitors from bots. Bots are labelled and kept out of visitor counts, so crawler traffic does not hide or fake a change. See bot traffic.
• Showing you broke it. After install, Stickybeak checks that the script loads, the tag is on your homepage and a first visitor arrives, so a missing tag is easier to spot. See verify your install.

Ad blockers can still stop any tracking script from recording a visit, ours included. Where first-party serving is available to your workspace, the script comes from your own domain; see serving Stickybeak from your domain.

Sources, checked 17 October 2026: Google Search Central, Debugging drops in Google Search traffic (causes and Search Console reports) and the Google Search Status Dashboard (update dates and rollout times). Stickybeak docs: Annotations and Verify your install.