Which Time Period Should You Compare Organic Traffic Against?

A report lands showing organic search traffic down 18%. Nobody asks the first question, which is: down compared with what? The dashboard picked last month, because dashboards default to last month, and the meeting proceeds as though that were a decision somebody made.

The comparison window is the analysis. Choose it after seeing the numbers and you can produce almost any story you like from the same data, which is why it should be chosen before.

Why does month over month make a healthy site look broken?

Because months are unequal in ways that have nothing to do with your work. They differ in length, in working days, in holidays, and in where demand sits in its annual cycle.

February against January starts three days short before any behavior is involved — a 10% handicap on a business whose traffic arrives on weekdays. Add a public holiday, or a month where a bank holiday falls midweek and pulls two adjacent days down with it, and a flat business reports a decline. Then the reverse happens next month and someone claims credit for a recovery that is just the calendar unwinding.

What is the window supposed to control for?

Seasonality first, then calendar shape, then the size of your own changes. The right window holds constant everything you are not trying to measure.

Year over year controls for season, because the same week last year sat at the same point in the demand cycle. It fails to control for everything you did in between, so a year-over-year gain cannot be attributed to last month's work. Week over week controls for season almost perfectly and for nothing else, so it is sensitive enough to catch a broken template within days and far too noisy to judge a content program.

Neither is right or wrong. They answer different questions, and most reporting arguments are two people using different windows to answer different questions while believing they disagree about the data.

Which window fits which question?

Match the window to the decision in front of you, not to a reporting habit.

The last row is the one most reports omit. A plotted line over thirteen months answers the question everyone actually has — is this going up — without forcing a two-period comparison onto a business that moves continuously.

What if the site is too young for year over year?

Use a rolling window and say so explicitly. A site with nine months of history cannot control for season, and pretending otherwise is worse than admitting the gap.

Rolling 28-day periods are the practical substitute: they equalize weekday counts, they smooth single-day spikes, and they move every day rather than lurching on the first of the month. They still carry seasonal drift, so the honest framing is "up 22% on the previous 28 days, in a period where we would expect some seasonal lift anyway."

Keep a note of what the season did to your category the first year you observe it. That record is what makes the second year's reporting trustworthy, and nobody ever regrets having written it down.

How do you compare when the site itself changed?

You annotate, and you stop comparing across the change without saying so. A migration, a redesign, a tracking rebuild or a shift in what counts as a session all break comparability in ways no window can repair.

Three things are worth recording on the same timeline as the traffic: deploys that changed templates or URLs, analytics configuration changes, and anything that altered how conversion rate is calculated. When a comparison crosses one of those lines, the report should show the line. Half the disputes about a traffic drop end the moment someone points at a tracking change three weeks earlier.

Does your data retention decide the window for you?

Partly, and it is worth knowing where the edge is before you plan around it. Google Search Console holds roughly sixteen months of performance data, which supports one year-over-year comparison and no more.

That limit is a reason to export. A monthly snapshot of query, page, clicks and impressions kept somewhere you control turns a sixteen-month window into a permanent record, and it costs a few minutes a month. Teams that started doing this three years ago can answer questions the rest of the industry cannot.

What should the report actually show?

One trend line, one comparison chosen in advance, and a note on anything that broke comparability. That is enough for almost every conversation about organic performance.

The discipline is to fix the window before the number arrives. A team that decided in January to judge the program on rolling 28-day periods can read a bad month calmly, because the standard was set when nobody had anything to defend.

Open your current report and find out which window it defaults to. If nobody chose it deliberately, that default has been shaping every conclusion your team has reached for as long as the report has existed.