Products Solutions Templates Pricing Resources

Why Refreshing a Page Is Not the Same as a Pageview

Home / Everything About / Everything About Analytics / Why Refreshing a Page Is Not the Same as a Pageview

You publish a popular blog post and check your analytics. It shows 500 pageviews but only 100 unique pageviews. For a moment you think something broke in the system. Then you realize: the same 100 people refreshed the page five times on average. Or maybe some people are using it as a reference guide, loading it repeatedly throughout the day.

This article explains what pageviews and unique pageviews actually count, why Google Analytics dropped the unique pageview metric, and what it means for how you should read your data.

What is a pageview?

A pageview is counted every single time a page loads. Refresh the page once, you created two pageviews. Load it again, three pageviews. If you visit the same article five times in one week, that is five pageviews, all from one person.

Pageviews answer one simple question: how many times did people view this page? Not "how many people" but "how many times." Every load, every refresh, every return counts.

This metric can be misleading if you do not understand it. You might think a page with 1,000 pageviews is a traffic star until you discover that 50 percent of those are the same person refreshing because they bookmarked it as a reference. Or that many pageviews come from search engine crawlers indexing the page, not actual human readers.

What are unique pageviews?

A unique pageview counts how many individual sessions included a view of that page. If you visit a page once per session, unique pageviews match pageviews. But if you refresh, navigate away, and come back within the same session, it only counts as one unique pageview.

The key word is session. Google's old metric counted one unique pageview per session per page. Load the same page three times in a 30-minute window, it counts as one unique pageview. Load it again the next day in a new session, that is another unique pageview.

This is useful because it tells you how many different times people visited the page. Not how many people, but how many visits. It filters out refreshes and revisits within the same browsing session.

Why Google Analytics stopped tracking unique pageviews

If unique pageviews is useful, why did Google drop it in GA4? Because they realized a better metric exists. Sessions.

In Google Analytics 4, you no longer see "unique pageviews" as a metric. Instead, you see sessions combined with a page dimension. Sessions tell you how many distinct browsing periods included a view of that page. That is the same information unique pageviews gave you, but cleaner.

The shift reflects that Google wants you thinking about user journeys and sessions, not just page counts. A session is a coherent unit of user behavior. A pageview is just a single page load. Sessions are more useful for understanding whether your content worked.

If 100 sessions included a view of your article but 500 pageviews happened on that article, you know 100 different browsing periods landed on it, but people visited the page multiple times per session on average. That distinction matters.

The practical difference in what you should do

If your pageviews are high but unique pageviews (or sessions per page) are low, people are repeatedly viewing the same page. That could mean it is valuable enough to bookmark and return to. Or it could mean your navigation is broken and people keep landing on the same page by accident.

If pageviews and unique pageviews are similar, each visitor views the page roughly once. That is typical for most content. People find it, read it, move on.

A how-to guide or reference page will have higher pageviews than unique pageviews. People bookmark it and reference it multiple times. A blog post people read once and leave will have pageviews close to unique pageviews. Neither is inherently good or bad. They just tell you different stories about user behavior.

How to read pageviews now that unique pageviews are gone

Start with sessions. That is your new baseline for "how many times did this page get visited?" Not how many people, but how many browsing sessions included it.

If sessions per page are climbing, more people are visiting that page. If sessions per page are flat but pageviews are climbing, the same people are visiting repeatedly within their sessions. That could mean they are using it as a reference, or it could mean navigation problems sending them back to the same page.

To understand the difference, look at session duration on that page and bounce rate. If people are staying on the page and navigating onward, multiple pageviews per session is fine. If they are bouncing within seconds, multiple pageviews suggests a usability problem.