How Search Console's date comparisons can help narrow down when traffic changed
When your website traffic drops (or spikes), the first question is always "when did this actually happen?" The second question, naturally, is "why?" Search Console's date comparison feature can help with the first question rather well. The second one requires a bit more detective work.
The comparison tool in Search Console's Performance report lets you put two date ranges side by side and see what changed between them. It's not going to solve your traffic mystery on its own, but it will tell you whether the problem started three weeks ago or three months ago, and whether it's affecting everything or just specific pages. That's surprisingly useful information when you're trying to work out what went wrong.
How the comparison feature actually works
In Search Console, you'll find the date range selector at the top of the Performance report. Click it, and you'll see an option to compare date ranges. You pick your two periods, apply the filter, and the interface shows you the difference between them in clicks, impressions, click-through rate and average position.
The clever bit is that you can then drill down. Click on the Pages or Queries tabs, and you'll see which specific pages or search terms gained or lost traffic between your two date ranges. Sort by the difference in clicks, and the pages that changed most dramatically float to the top. It's like having a highlighter pen that marks exactly where to look first.
You can compare any two periods you like, though comparing similar lengths usually makes more sense. If you're comparing a week to a month, the numbers get a bit odd. Most people compare the last 28 days to the previous 28 days, or this month to last month, or this week to the same week last year if they're accounting for seasonal patterns.
Narrowing down when something changed
The real value here is in narrowing down timing. Let's say you've noticed your traffic is down, but you're not sure when it started. You could compare the last month to the previous month and find clicks are down 30%. That's useful, but it doesn't tell you whether the drop happened on day one or day twenty-eight.
So you start breaking it down. Compare the last week to the week before. Still down? Compare that week to the one before it. Eventually you find the week where the change actually occurred. Now you've got a specific window, and that's when you start looking at what else happened during those dates.
You can also filter by device, country, or search appearance to see if the change only affected certain segments. If mobile traffic dropped but desktop stayed steady, that's a different problem than if everything fell off a cliff together. If one country dropped and others didn't, you're looking at something regional. The comparison tool won't tell you what caused these patterns, but it will show you the patterns exist.
What the comparison can't tell you
Here's where people often get unstuck: they find that traffic dropped in a specific week, notice that Google announced an update around the same time, and immediately assume the update caused the problem. Sometimes that's true. Often it isn't.
Search Console shows you what changed, not why it changed. A drop in clicks could be caused by a hundred different things. Maybe you deployed new code that broke something. Maybe your product went out of stock and you removed those pages. Maybe seasonal demand shifted. Maybe a competitor launched something new. Maybe there was a reporting delay and the data corrected itself the following week.
Before blaming algorithm updates (especially the minor ones that get announced seemingly every other week), it's worth checking a few other possibilities. Look at your website releases and see if you deployed anything around that date. Check Google's index coverage report to see if pages dropped out of the index. Consider whether search demand for your topic might have genuinely changed. Check whether other analytics tools show the same pattern, or whether it's just Search Console behaving oddly.
Sometimes the cause is blindingly obvious once you look. A site redesign, a technical error, a major news event that shifted what people search for. Other times it's genuinely mysterious and requires proper analysis. Either way, knowing exactly when the change occurred gives you a starting point that's better than "sometime in the last few months, probably."
Seasonal comparisons and year-on-year data
One of the more sensible uses of date comparison is comparing the same period across different years. If you run a website about gardening, comparing this May to last May makes more sense than comparing May to April, because search behaviour follows the seasons rather than the calendar.
Year-on-year comparisons help you separate "we're down because it's winter" from "we're down because something actually broke." They also show you whether your traffic is growing or shrinking over the long term, rather than just bouncing around with seasonal variation.
The downside is that if something did change, a year is a long time to wait before you spot it. Most people use a combination: week-on-week or month-on-month for spotting immediate changes, and year-on-year for understanding the bigger picture and filtering out seasonal noise.
Pages and queries that moved
When you're looking at the comparison data broken down by pages or queries, you're often looking for outliers. The pages that gained or lost traffic disproportionately compared to the rest of your site. Those are usually where the interesting stories are.
A page that lost 90% of its clicks while everything else stayed flat suggests something specific happened to that page. Maybe it's no longer ranking for its main keyword. Maybe it got de-indexed. Maybe the content became outdated and stopped matching what people search for. You'd need to investigate further, but at least you know where to look.
Similarly, queries that suddenly drove more or fewer clicks tell you something about changing search behaviour or your rankings. If a query that used to send you traffic has disappeared, either people stopped searching for it, or you stopped ranking for it, or both. Knowing which queries changed helps you understand what kind of problem you're dealing with.
The limitations of reporting quirks
Occasionally, Search Console just does something weird. Data gets delayed, then arrives in a lump. A reporting bug appears and gets fixed. Thresholds for anonymised data change. These quirks can make it look like traffic changed when it didn't, or didn't change when it did.
This is why it's always worth cross-referencing with other data sources. If Search Console says you lost half your traffic but your server logs show no change, something's off with the reporting. If both agree, you probably have a real problem. Don't rely on Search Console in isolation, even though it's often the most detailed source for organic search data.
Using comparisons as part of ongoing monitoring
Rather than only checking when something goes wrong, some people set up regular comparisons as part of their routine monitoring. Weekly or monthly checks to see what's trending up or down. It's a way of spotting problems early, before they become catastrophic.
If you notice a page steadily losing traffic over several weeks, you can investigate before it disappears entirely. If you spot a query that's suddenly gaining traction, you might want to create more content around that topic. Regular comparisons turn Search Console into an early warning system rather than just a diagnostic tool for when things have already broken.
It does require a bit of discipline and record-keeping. You need to actually look at the data regularly, and you need to remember what you found so you can spot patterns over time. But for anyone who depends on organic search traffic, it's generally time well spent.
More reading on search and analytics
If you've found this useful, we've written quite a bit more about Search Console, analytics and the occasionally baffling world of organic search traffic. There's plenty more in our Search Analytics section to dig into when you're ready.
How to Use the URL Inspection Tool in Google Search Console: The "Check My Work" Button
Why your 'Average position' in Search Console doesn't mean what you think it means
Why your internal site search is probably lying to you about what customers want
Why we write about this stuff
We write about search and analytics partly because we find it interesting, but mainly because it's part of our job. When we build websites for clients, setting up proper analytics and understanding how search works is just part of what we do. It's not a bolt-on extra; it's built into the process from the start.
We also offer an ongoing management service where we take care of all this for clients who would rather not spend their time learning the finer points of Search Console date comparisons. Some people enjoy this sort of thing. Many don't, and that's entirely reasonable. Either way, we've got it covered.
Work with us
If you'd like us to build you a website (and help you understand what's actually happening with your search traffic), or if you've already got a site but could do with someone keeping an eye on these things, get in touch. We'll have a proper conversation about what you actually need, rather than trying to sell you things you don't.
Ongoing Website Management Prices
How do I compare date ranges in Google Search Console?
Go to the Performance report in Search Console and click the date range selector at the top. You'll see an option to compare date ranges—just pick your two periods, apply the filter, and you'll see the differences in clicks, impressions, CTR, and position.
What's the best way to figure out when my website traffic actually dropped?
Start by comparing broader periods like the last 28 days to the previous 28 days. Then break it down week by week until you find the specific week where the change occurred. This narrows down your timeline so you know exactly when to investigate what might have caused it.
Can Search Console tell me why my traffic went down?
No, it only shows you what changed, not why. A traffic drop could be caused by a site update, technical issues, removed pages, seasonal changes, or competitor activity—you'll need to do detective work to figure out the actual cause.