Page View
AnalyticsAlso: Pageview · PV
Quick definition
The total number of times a page has been loaded or reloaded in a browser. One of the oldest web analytics metrics. Often misinterpreted because it counts every load including refreshes, bot visits and multiple visits from the same user.
Where it shows up in the data
A page view counts every time a page loads, including multiple views of the same page by the same user in the same session. Unique page views (now largely deprecated in GA4) counted each page once per session. Understanding which you're looking at matters for interpretation.
In GA4, page_view is an automatically collected event rather than a primary metric. GA4 focuses more on sessions, users, engaged sessions and events. The shift reflects a view that raw page view counts are less meaningful than user engagement depth.
A single page view might just mean someone landed and left. Pages per session (total page views divided by total sessions) tells you whether users are exploring the site. Higher pages per session indicates more engagement, though it must be interpreted alongside time on site and conversion rate.
What it actually means
A page view is recorded each time a web page is fully loaded in a browser. It's one of the most basic web analytics metrics and one of the most frequently misinterpreted. Because page views count every load, including browser refreshes, bot crawls and multiple visits from the same user, raw page view counts overstate actual human engagement. In Universal Analytics (the previous Google Analytics), sessions and page views were the primary metrics. In GA4, the focus has shifted toward engaged sessions, events and user behaviour signals that better indicate whether a person is genuinely engaging with content rather than just loading a URL.
Page views tell you how many times your door opened. They don't tell you if anyone came in.
How to calculate it
Pages per Session = Total Page Views / Total Sessions
Worked example. A website records 45,000 page views across 12,000 sessions in a month. Pages per Session = 45,000 / 12,000 = 3.75. This indicates users are viewing nearly 4 pages on average per visit, suggesting reasonable content engagement.
The Australian context
Australian analytics professionals have largely adopted GA4, which deprioritises raw page views in favour of engagement metrics. However, many Australian businesses still report to boards and stakeholders using page view language from the Universal Analytics era. Bridging this communication gap, explaining why engaged sessions and conversion events matter more than page views, is a common challenge in analytics consulting.
Where people get this wrong
Related terms
Common questions
What's the difference between page views and sessions?
A session is a single visit by a user to your website, which can include multiple page views. If a visitor loads 5 pages during one visit, that's 1 session and 5 page views. Sessions count visits; page views count individual page loads.
Do page views affect SEO?
Indirectly. Page views themselves aren't a ranking signal. However, behaviours that correlate with high page views (engaged users returning frequently, exploring multiple pages) are positive signals to Google. The underlying quality that produces page views matters, not the count itself.
Are page views still reported in GA4?
Yes. In GA4, page_view is an automatically collected event and page view data is available in reports. The difference is that GA4's default reporting emphasises engaged sessions, users and conversions rather than placing page views at the centre of the dashboard.
Keep exploring
About New Rebellion
New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.
How we think →