Products Solutions Templates Pricing Resources

What descriptive analytics actually shows you about your website

Home / Everything About / Everything About Analytics / What descriptive analytics actually shows you about your website

You publish a new blog post on Monday. By Friday, you're wondering if anyone read it. You check your analytics, see a number next to "pageviews," and then what? You know people visited, but descriptive analytics only answers one question: what happened?

That's actually where most website owners get stuck. They have data but no framework for understanding it. This article covers what descriptive analytics is, why it's the foundation of every smart decision you'll make about your site, and what to actually measure.

Descriptive analytics is the practice of looking at what already happened on your website — the traffic that came, the pages people visited, how long they stayed. It answers the simplest question in analytics: what happened?

Here's the distinction that matters: descriptive analytics summarizes the past. The other types of analytics (diagnostic, predictive, prescriptive) all depend on it working first. You cannot figure out why something happened if you haven't clearly described what happened in the first place.

For a website owner, this means descriptive analytics is your baseline. It's the "before" picture. Everything else builds from here.

Why descriptive analytics is the foundation for everything else

When you check your traffic at the end of the week and see 200 visitors instead of 150, that number is descriptive analytics. The description of what happened.

But here's what makes it powerful: without that clear description, you cannot ask the next questions.

Next week someone asks, "Did that email campaign work?" You can't answer that without comparing this week's traffic to last week's traffic. That's descriptive analytics in action — comparing descriptions of what happened across different time periods.

Same with pages. You publish five pages this month and they get very different traffic. One page gets 500 views, another gets 50. That difference is descriptive data. And once you have the description (one page performed 10x better), you can ask the diagnostic question: why? But first, you need the description.

Descriptive analytics is how you know what you're actually looking at. Without it, you're guessing.

What metrics actually matter for a website

Most analytics tools show you 50+ metrics. Most of them don't matter for a website owner. Descriptive analytics is simpler: you're summarizing what happened. Focus on these.

Visitors (the who)

How many people came to your site. This is your baseline number. Month-to-month comparisons tell you if your website is growing or shrinking.

The detail that matters: where did they come from? Direct (typed your URL), organic search (found you on Google), referral (came from another site), or ads (you paid for them). If 80% of your visitors come from search and search traffic drops by half next month, that's a descriptive fact that tells you something changed in search results — now you can investigate why (diagnostic analytics).

Pages they visited (the what)

Some pages get more traffic than others. That's a descriptive fact. Track which pages are actually getting views so you know what's working, what's stuck, and what nobody is reading.

The detail that matters: traffic over time. Is a page's traffic growing, staying flat, or declining? A page that got 100 views last month but only 50 this month is describing a trend — and now you can ask why it's declining.

Visitor behavior (the how)

Did they look at one page and leave, or did they explore multiple pages? Did they read the whole page or bounce in five seconds?

Track bounce rate (percentage of visitors who leave without doing anything) and average time on page. These describe what visitors actually did. High bounce rate + short time on page = people arrived but left quickly (description). That's different from high bounce rate + long time on page = people read the whole thing then left (different description, probably not a problem).

Actions (the why they matter)

Descriptive analytics should answer: how many people filled out your form, downloaded your lead magnet, or made a purchase? These are the actions that matter to your business.

Your site might get 1,000 visitors a month. If zero of them convert to a lead or sale, that's a critical descriptive fact. One that tells you the next problem to investigate (diagnostic: why are visitors not converting?).

Baseline reporting: how to organize what happened

Descriptive analytics becomes useful the moment you organize it into reports. A report is just an organized summary of what happened.

Set up a simple weekly or monthly report that tracks:

Traffic summary

Total visitors this period, compared to last period. Is it up or down? That's the simplest descriptive question.

Top pages

Which pages got the most views. This tells you what people are actually interested in.

Traffic sources breakdown

Where your visitors came from. Knowing whether your traffic is mostly from search, direct traffic, or ads tells you which channels are working.

Conversions

How many people took an action that matters (filled out a form, made a purchase, signed up for email). This is the single most important descriptive metric for your business.

A report doesn't need to be fancy. Most website owners use a simple spreadsheet or their analytics dashboard. The goal is to see the description of what happened, organized clearly, so you can spot patterns and ask better questions next.

The difference between describing what happened and understanding it

Here's the trap: descriptive analytics is so simple that many website owners stop there. They run a report, see the numbers, and assume they understand their data.

They don't. They have descriptions, not understanding.

Say your conversion rate is 1%. That's a descriptive fact. But 1% compared to what? Compared to last month it could be up or down. Compared to your industry it could be strong or weak. Compared to your goal it could be terrible or fantastic.

Descriptive analytics describes your data. Diagnostic analytics helps you understand what it means. This article is about the first part — getting clear descriptions of what happened.

But the point of getting those descriptions is so you can ask the next question: why did this happen? And then act on the answer. Descriptive analytics is the necessary first step, not the final step.

How to start: three things to track this week

You don't need a complex analytics setup to start with descriptive analytics. Start simple.

This week's total visitors

Open your analytics. Write down how many people visited your site. That number is the baseline description.

Your top three pages

Which pages got the most traffic? Write those down. These are the descriptions of what your site is actually delivering to people.

Conversions

How many people completed an action that matters to you (form submission, purchase, email signup)? Write that down. This is the descriptive metric that connects traffic to results.

Next week, write down the same numbers again. The comparison — week 1 vs. week 2 — is now your descriptive trend. That's all descriptive analytics is: comparing what happened across time periods so you can see the pattern.

Why tracking what happened is actually strategic

Descriptive analytics sounds basic. It is basic. But basic is what most websites lack.

Many website owners have a vague sense that their site "isn't bringing in enough clients" but they don't actually know whether traffic is the problem, conversion is the problem, or the right people just aren't finding them. They haven't described what's happening.

The moment you have clear descriptions of what happened — organized in a simple report, compared month-to-month — you go from guessing to knowing. And knowing is when you can start asking the questions that matter (why did this happen? how do we improve it? what will happen next?).

Descriptive analytics is the foundation. Get it right, and everything that follows becomes much clearer.