What Is a Pageview?
A pageview is the most granular measure of content consumption in web analytics. Every time a browser requests and fully renders a page, whether it is a home page, a blog post, a product listing, or a contact page, one pageview is recorded. If a user visits the same page multiple times during a session, each visit counts as a separate pageview. This means total pageviews will always be equal to or greater than the number of sessions.
In Google Analytics 4, the metric is referred to as "views" rather than pageviews, and it counts page_view events. The distinction matters when you configure tag managers, because sending a page_view event more than once per page load will inflate your view counts. GA4 also tracks screen views for app content using the screen_view event, and both are combined into the "views" metric in standard reports.
Pageview data is particularly useful for understanding which content on your site is generating the most interest. Sorting your pages by pageview count quickly identifies your top-performing content and your least-visited pages. For a South African business, this analysis often reveals that a handful of pages drive the majority of traffic, while dozens of product or service pages receive almost no organic visits. That imbalance points directly to where SEO and content improvement efforts should be focused.
It is worth distinguishing pageviews from unique pageviews, a metric that existed in Universal Analytics. Unique pageviews counted how many sessions included at least one view of a specific page, collapsing multiple views of the same page in a single session into one. This gave a clearer picture of how many distinct visits a page received. In GA4, you can approximate this by looking at users per page rather than total views.
Pageview In Practice
A Johannesburg travel agency runs a content blog alongside their booking site. Looking at monthly pageview data in GA4, they notice their article on "best game reserves near Johannesburg" accumulates four times more pageviews than any other article. That single data point tells them there is strong audience demand for this type of content. By creating additional related articles about specific reserves, seasonal visit guides, and packing lists, they capitalise on that demonstrated interest and generate a cluster of pages that collectively drive significant organic traffic.
For a Cape Town restaurant group, tracking pageviews on their individual venue pages reveals that two of their five venues receive virtually no organic traffic, even though they are among their highest-revenue locations. This tells the team that those venue pages need SEO attention, specifically targeted keywords, better meta descriptions, and locally relevant content about the area, the food style, and what makes each venue distinct. The pageview data identifies the gap; the SEO work closes it.
What pageviews measure
A pageview is recorded each time a page on a website is loaded or reloaded, so it counts content consumption, how many pages are being viewed, rather than how many people visit. One visitor reading five pages generates five pageviews; refreshing a page adds another. This makes pageviews a useful measure of how much content is being consumed and which pages attract the most views, helpful for understanding what content resonates. But pageviews say nothing on their own about how many distinct people visited, how engaged they were, or whether they achieved anything, which is why pageviews are a starting point rather than a conclusion. A high pageview count is only valuable if those views come from real interest and lead somewhere, so pageviews are best read alongside metrics of visitors, engagement and conversion.
Reading pageviews in context
Pageviews are easy to inflate and easy to misread, so context matters. High pageviews can mean engaged readers moving through content, or they can mean people clicking around lost, or a single visitor refreshing, so the number alone does not indicate success. This is why modern analytics, including GA4, de-emphasises raw pageviews in favour of engagement-based metrics such as engaged sessions, which better reflect whether visits were worthwhile. Pageviews remain useful for specific questions, which individual pages get the most views, how content consumption trends over time, but as a headline measure of a site's performance they mislead, since they reward volume over value. The sound approach is to use pageviews for what they genuinely show, content consumption by page, while judging overall performance on visitors, engagement and conversions.
FAQ
What is the difference between a pageview and a unique pageview?
A pageview is recorded every time a page loads, including repeat views by the same user in the same session. A unique pageview counted the number of sessions during which a page was viewed at least once. In GA4, the equivalent is comparing total views against users per page, which gives a sense of how many distinct visitors each page is reaching versus how much repeat viewing occurs.
Are pageviews still a useful metric in GA4?
Yes, pageviews remain useful in GA4 for identifying your most visited pages, understanding content popularity, and tracking navigation patterns. GA4 supplements pageviews with richer event data and engagement metrics that give a more complete picture of how users interact with your site beyond simply loading a page.
Are pageviews still useful in GA4?
Yes, for understanding content consumption by page, but GA4 emphasises engagement-based metrics such as engaged sessions over raw pageviews as headline measures, because they better reflect whether visits were worthwhile. Use pageviews for page-level content questions, and engagement and conversion metrics to judge overall performance.