Time series forecasting: predicting your traffic patterns

Home / Everything About / Everything About Analytics / Time series forecasting: predicting your traffic patterns

Your website gets about 400 visitors most weeks. But last week was 600. Next week might be 300. The pattern isn't random—it's seasonal. Summer gets less traffic. End of month gets more. Weekdays get more than weekends.

Time series forecasting uses those patterns to predict future traffic. This article covers how to recognize patterns in your data and use them to forecast what's coming.

Time series forecasting is the practice of analyzing historical data ordered by time and using patterns to predict future values. You look at your traffic week-by-week or month-by-month over a year. You identify patterns (peaks, troughs, seasonal cycles). Then you project those patterns forward.

Unlike general predictive analytics, time series forecasting is specifically about sequences over time. It acknowledges that what happened last week influences what happens this week. Weather might affect traffic. Seasons affect shopping. Days of the week affect behavior.

What patterns exist in website data

Most websites have repeating patterns. Learning to spot them is the first step to forecasting.

Daily patterns

Weekdays get more traffic than weekends for B2B sites. Weekends get more for e-commerce and entertainment sites. Morning hours get more office visits than afternoon. These are consistent week-to-week.

If your traffic is 600 on Mondays and 400 on Saturdays, that pattern likely repeats. Time series forecasting uses that regularity.

Weekly patterns

If you publish content on Tuesdays, traffic spikes Tuesday. If you send email campaigns on Thursday mornings, traffic peaks Thursday. These patterns repeat weekly.

Track a month of data and you'll see the weekly rhythm. Once you see it, you can predict it.

Seasonal patterns

January is slower than December. Summer is slower than fall. Tax time is busier for accounting services. Time series forecasting captures these multi-month cycles.

You need at least a year of data to identify seasonal patterns. Six months is the minimum for weekly patterns.

Trend patterns

Beyond seasonal cycles, some sites have longer trends. New sites grow steadily (upward trend). Mature sites plateau. Some decline. Time series forecasting separates the long-term trend from the seasonal noise.

If your trend is growing 10 percent annually and your seasonal pattern shows Q4 spikes, you can forecast Q4 next year: last year's Q4 plus 10 percent growth plus seasonal adjustment.

The math behind time series forecasting

You don't need to know the math to use it, but understanding the concept helps.

Time series forecasting breaks your data into components:

Trend: long-term direction (growing, declining, flat)

Seasonal: repeating patterns (daily, weekly, monthly, yearly)

Random variation: noise that doesn't follow a pattern

Formula: Actual value = Trend + Seasonal + Random

Forecasting predicts the trend and seasonal parts. The random part stays unpredictable.

Example: Your traffic this week was 500.

Trend component: +50 (growing 50 per week)

Seasonal component: +100 (this week is peak season)

Random component: -50 (just noise)

Actual: 50 + 100 - 50 = 100. Base of 400 + 100 = 500.

Next week without the special event (no random spike):

Trend: +50

Seasonal: -75 (next week is off-peak)

Random: 0

Forecast: 400 + 50 - 75 = 375

This is simplified, but the concept is that your forecast separates signal (trend plus season) from noise (random).

Simple forecasting methods for website owners

You don't need complex algorithms. Simple methods work well.

Method 1: Same-period comparison

Traffic this Monday averaged 600 over the past year. Next Monday will probably be around 600.

This is the simplest forecast: look at the same day or week last year.

Method 2: Trend plus seasonal

Traffic grew 10 percent year-over-year and Decembers are 50 percent higher than average.

Forecast for December next year: (Last December) times 1.10 (for 10 percent growth) equals your forecast.

Method 3: Moving average

Average the last 4 weeks of traffic. That's your baseline. Then add seasonal adjustment.

If baseline is 500 and December usually runs 550, your December forecast is 550.

Method 4: Exponential smoothing

Give more weight to recent data than old data. Recent weeks matter more than data from a year ago because things change.

If the last 4 weeks averaged 480 and the year-ago average was 450, trust the recent data more. Forecast closer to 480 than 450.

Seasonal decomposition: the key technique

Seasonal decomposition separates your data into trend, seasonal, and random components. It's the foundation of most accurate forecasting.

Step 1: Collect a full year of data (or multiple years if you want accuracy).

Step 2: Calculate the average for each period (each Monday, each month, etc.). These are your seasonal indices.

Step 3: Calculate the trend by fitting a line through the data. Is it growing? Declining? Flat?

Step 4: Remove the trend and seasonal to see the noise. Random variation is what's left.

Step 5: Project forward using the trend and seasonal components. Add back the seasonal variation to the trend line.

You can do this with simple spreadsheet math or use forecasting tools that do it automatically.

Tools that make time series forecasting easy

You don't need advanced software. Basic tools work:

Google Sheets: Built-in FORECAST function

Excel: FORECAST or FORECAST.LINEAR

Python libraries: Prophet (made by Facebook), ARIMA, LSTM

Analytics platforms: Many track forecasts automatically

WEMASY's analytics could integrate forecasting, showing you predicted traffic for next month based on historical patterns.

Limitations of time series forecasting

Time series forecasting assumes the past predicts the future. It doesn't account for unique events.

If you launch a major campaign, the forecast breaks. If Google changes search results, the forecast is wrong. If the economy shifts, patterns change.

Time series forecasting works when conditions stay stable. It fails when conditions change.

How to use forecasts practically

Forecasts aren't guarantees. They're guides for planning.

If you forecast 600 visitors next week, plan for 600 but stay flexible. If you hit 450, investigate what changed. If you hit 800, celebrate but understand why.

Use forecasts for:

Capacity planning: Will you need more servers? More support staff?

Campaign planning: When is the best time to launch?

Revenue forecasting: What will revenue look like next quarter?

Baseline comparison: Did that change move the needle or was it just seasonal?

Frequently asked questions

How much historical data do I need to forecast accurately?

What if my data is erratic with no clear pattern?

Can I forecast different segments of my traffic separately?

Should I adjust my forecast manually?

How often should I update my forecast?

Is time series forecasting the same as predictive analytics?