Pageviews

A pageview is recorded each time a page on a website is loaded or displayed, and pageviews are simply the total of those instances over a period. If one person opens a page, leaves, and opens it again, that counts as two pageviews; if they refresh, many analytics tools count another. So pageviews measure raw viewing volume — how many times pages were served — not how many people did the viewing or how many visits they made. It is one of the oldest and most basic web metrics, easy to understand and easy to collect, which is why it appears on nearly every analytics dashboard. Pageviews answer a narrow but useful question: how much page-level activity is happening on a site, in total, regardless of who is generating it or how it clusters into visits.

Because it is a volume count, pageviews are handy for gauging overall traffic scale, spotting trends over time, and seeing which individual pages draw the most viewing — a spike in an article's pageviews shows it struck a nerve. Many analytics tools also report unique pageviews, which collapse repeated views of the same page within a single visit into one, giving a sense of how many visits included that page at least once. But the plain pageview total remains a gross measure of activity, not of audience. Its simplicity is both its strength and its weakness: it is unambiguous and comparable, but on its own it says nothing about how many real people came, how engaged they were, or whether any of that viewing led anywhere useful.

Pageviews are easiest to understand next to the two metrics they are most often confused with: sessions and unique visitors. A session (or visit) is a single continuous period of activity by one person, which can include many pageviews — someone who lands on a site and reads five pages generates one session and five pageviews. A unique visitor is one distinct person, counted once no matter how many pages they view or how many times they return in the period — that same reader is one unique visitor. So the three answer different questions: pageviews count pages viewed, sessions count visits, and unique visitors count people. Pageviews are almost always the largest of the three, because each person makes several visits and each visit loads several pages.

Getting these straight matters because they tell you different things. Pageviews measure total content consumption and are inflated by repeat views and refreshes, so a high pageview count can mean lots of engaged reading or just a few people reloading. Sessions measure how often the site is visited, useful for understanding visit frequency and behavior within a visit. Unique visitors measure audience size — the reach of the site in people — which is what you want when you care about how many humans you touched, not how busy they were. Reading pageviews alone, without sessions and unique visitors beside them, is a classic way to misjudge traffic: a big pageview number looks like a big audience, when it might be a small audience viewing many pages, or bots and reloads padding the total.

Use pageviews for what they are good at — gauging the scale and trend of content consumption, comparing the pulling power of individual pages, and tracking how total activity moves over time — and always read them alongside sessions and unique visitors so you know whether volume reflects many people or a few busy ones. Prefer unique pageviews when you want to strip out within-visit repeats, and lean on unique visitors when the real question is audience size. Watch for inflation: auto-refreshing pages, single-page applications that fire multiple events, and bot traffic can all pad pageviews without any human reading more. And pair pageviews with engagement and outcome metrics — time on page, scroll, conversions — because volume without engagement or results is just noise.

The failures nearly all come from treating pageviews as something they are not. Reading pageviews as audience size overstates reach, since one person can generate dozens; a page with huge pageviews and tiny unique visitors is being reloaded, not widely read. Chasing pageviews as the goal invites clickbait, pagination tricks, and auto-refresh schemes that inflate the number while degrading the experience and teaching no one anything. Ignoring bots and technical double-counting lets a padded total masquerade as success. And judging content on pageviews alone, without engagement or conversion, rewards volume over value. Used honestly — as a raw volume metric read in the company of sessions, unique visitors, and engagement — pageviews are useful. Used as a vanity headline, they are one of the easiest web numbers to fool yourself with.

The pageview dates to the earliest days of web analytics in the 1990s, when counting page loads was the basic measure of a site's traffic before visits and visitors were distinguished.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where pageviews is a core concern: