How to find out why your website traffic dropped with Google Analytics and Search Console

To find out why your traffic dropped, you work from the total down to the specific pages that lost visits, and only then look for a cause. The total number of visitors is the sum of many smaller streams: people arriving from Google, from ads, from email, from social posts, from other sites that link to you, and from typing your address directly. When the total falls, one or two of those streams usually account for most of the loss. Find the stream, find the pages inside it, and the list of possible causes gets short.

Before any of that, check that the drop is real. Compare the same days of the week, because Monday traffic and Saturday traffic rarely look alike, and compare against the same week last year if your business is seasonal. A week with a public holiday, or a comparison against a week when a post went viral, will look like a drop when nothing is wrong. Then check the measurement itself. If every channel fell at the same moment, including direct visits, the cause is often a tracking tag that stopped loading after a site update or a change to your cookie banner, rather than lost visitors.

Google Analytics 4 is where you find the missing stream. Open the traffic acquisition report, compare this week with the last, and break sessions down by Session default channel group to see whether Organic Search, Paid Search, Email, Referral, or Direct lost the most. Then look at the Landing page report for that channel to see which pages lost their visits, and check device and country if the drop is narrow. A paid campaign that was paused, an email that didn't go out, or a partner that removed a link to you will show up here as a channel or a source that went quiet.

When the drop is in organic search, Google Search Console tells you why. Its performance report shows clicks, impressions, click-through rate, and average position for each query and page. The way those four numbers move together points to the cause:

• Position fell. Your pages slipped in the rankings, often because a competitor published something stronger, Google released an update, or your page changed.
• Impressions fell but position held. Fewer people searched for those terms, which usually means seasonality or a fading trend.
• Impressions and position held but clicks fell. The results page changed around you, for example an AI Overview now answers the question, or your listing lost its snippet.
• A page dropped out entirely. Google may have stopped indexing it because of a redirect, a noindex tag, or a crawl error. The URL Inspection tool and the Pages report show whether it's still indexed.

Google offers some help on its own. You can link Search Console to Google Analytics, which adds Search Console reports to Analytics showing queries and organic landing pages next to your engagement numbers. Google Analytics' Insights panel can also flag an unusual change automatically. Both are useful, but they stop at showing you numbers. Neither one checks whether your tracking broke, compares the drop against last year, looks at what changed on the page, or tells you which explanation the evidence supports. Search Console's data also runs a couple of days behind, so a drop that started this week may not be fully visible there yet.

A good result is a short, specific answer: how big the drop is against a fair comparison, which channel and pages caused it, the most likely reason with the evidence behind it, the explanations you ruled out, and the first thing to fix. Kite does that investigation for you. It reads both tools, checks your site and the web for what changed, and reports what it found in Slack.

Start by telling Kite in Slack what you noticed:

"Our website traffic dropped this week. Can you find out why?"

Kite is an AI marketer in your Slack. It researches your business, builds a growth strategy, and ships the work that brings you new customers. From that research, it already knows which pages matter most to your business, which keywords you compete for, and who your competitors are. So it doesn't need a long brief. If you know when the drop started or which part of the site worries you, mention it, and Kite starts there.

Connect your Google Analytics account and your Google account for Search Console through OAuth so Kite can read your reports. If your account has access to more than one Google Analytics property or Search Console site, Kite lists them and confirms which one belongs to the site you're asking about.

Reading reports is routine work, so Kite starts as soon as the accounts are connected and posts its findings in the thread. It asks for your approval before it publishes any change to your site.

Kite starts by measuring the drop against a fair comparison, so it isn't chasing an ordinary dip. It runs a Google Analytics report on your property for the days in question and compares them with the same days the week before. If your traffic is seasonal, it compares them with the same week last year as well. It reads sessions, active users, and views by date to see whether the drop happened all at once or slid over several days, which already says a lot about the cause.

It also checks whether the problem is measurement. Kite reads the reporting annotations on your property, which often record a site launch or a tracking change. It runs a realtime report to confirm events are still arriving, and it checks your live pages to confirm the Google Analytics tag still loads on them. When every channel fell at the same hour, Kite treats a tracking change as the first suspect and tells you so before it looks for lost visitors.

Kite breaks the drop down by Session default channel group to find the stream that accounts for most of the loss. It compares sessions, engagement rate, and key events for Organic Search, Paid Search, Email, Organic Social, Paid Social, Referral, and Direct between the two periods, and it ranks the channels by how many visits each one lost.

When one channel explains most of the drop, Kite goes deeper inside it. It breaks Paid Search and Paid Social down by campaign, Email by campaign and send date, and Referral by source, so a paused campaign, a skipped newsletter, or a site that stopped linking to you shows up by name. It also checks device category and country, because a drop limited to mobile visitors or to one market points somewhere very different from a drop everywhere.

Kite reads the Landing page report for the channel that fell and finds the pages that lost the most sessions. Usually a small group of pages accounts for most of the loss, and those pages become the focus for the rest of the investigation. Kite separates a page that lost some of its visitors from a page whose traffic fell to almost nothing, because the second kind usually has a technical cause.

When the drop is in organic search, Kite queries your Search Console performance for the same two periods, broken down by page and by query. For each page that lost traffic, it compares clicks, impressions, click-through rate, and average position, and it reads which queries carried the loss. That tells Kite which of the four patterns it's looking at: lower rankings, less search demand, fewer clicks on the same rankings, or a page missing from results.

Kite follows each pattern to its evidence:

• For a page that disappeared, it inspects the URL in Search Console and reads its index status and any issues Google reports against it. It also reads your sitemaps and how many of their URLs Google has indexed.
• For a page that lost rankings, it checks who ranks for those queries now, using its built-in keyword and ranking data, and reads the pages that moved ahead of yours.
• For a page that lost clicks on steady rankings, it checks whether Google now shows an AI Overview for those queries.
• For lower demand, it compares search volume for the affected queries with the same period last year.

Kite reads Search Console's most recent days carefully, because Google takes a couple of days to process them. When the drop is too recent to appear there in full, Kite says which days it could read.

Kite then looks for the event that lines up with the drop. On the pages that lost traffic, it renders the live page and checks for a noindex tag, a changed title, a redirect, or a slow load. Where archived copies of the page exist, Kite compares them with the current version to see whether the content or title changed. Outside your site, it searches the web for a confirmed Google update in the same window and checks whether a competitor launched something that now competes for the same queries.

Kite treats a match in timing as a lead to check, not as proof. When a title change and a ranking drop happened in the same week, it says the two line up and how confident it is, and it separates what the data shows from what it infers.

Kite posts its diagnosis in the Slack thread where you asked. It opens with the answer: how much traffic fell, against which comparison, and which channel and pages account for the loss. Then it gives the most likely cause with the evidence behind it, the explanations it checked and ruled out, and the fix it recommends first. Every figure carries the dates it covers and the tool it came from. When the findings are too long for one message, Kite publishes them as a findings page with charts and tables and links to it from the thread.

From there, Kite can start on the fix. On a site Kite hosts, it can rewrite a page that lost rankings, restore a title, remove a stray noindex tag, or set up a redirect. On a site it updates through a supported CMS such as Webflow, it can rewrite the page and restore its title. It asks for your approval before publishing. It can resubmit your sitemap in Search Console and inspect the affected URLs again once Google has recrawled them. When a drop traces back to a paused campaign or a missed email, Kite tells you which one and what it cost in visits, so you can decide whether to turn it back on.

If you'd like to catch the next drop sooner, ask Kite to run the same check every week and post the results in a channel you choose. For a site Kite hosts, it can also keep a standing watch on your daily traffic and tell you when it falls against the day before or the past week's average.

When Kite finishes, you have an explanation of the drop that you can act on, and a record of how Kite reached it.