What is a good value for pages per session?

It depends on the content model, and a value imported from another site does not apply. A news archive is healthy with deep browsing, while a single-product landing page that moves quickly to checkout is healthier with a low value. The right baseline is the site's own history and comparison across traffic segments.

How does this differ from average pageviews per session?

They are the same measure under two report names. What actually changes the value is whether the numerator uses all pageviews or unique pageviews; on a unique basis reloads are not counted and the number comes out lower.

Pages per Session

Beginner

Updated Jul 11, 2026 Shahin editorial 2 min read

PronunciationEN/ˈpeɪdʒɪz pər ˈsɛʃən/

Pages per session is the average number of pageviews recorded in one session, computed as total pageviews divided by total sessions.

The figure is a ratio of two totals, not the average of per-session ratios, so a handful of very deep sessions can lift it while the median session still stops at one page. Single-page sessions sit in the denominator and pull the value toward one, which ties this metric closely to bounce rate. Single-page applications report a value near one until route changes are sent as virtual pageviews, and that collapse is an instrumentation gap rather than a change in behaviour. The most common wrong reading is treating a rise as better engagement: extra pages are also what a lost visitor generates when navigation or site search fails them.

How it is calculated

Pages per session = total pageviews ÷ total sessions

The numerator includes every pageview, reloads and repeat views among them, and the denominator includes every session, single-page sessions among them. The result is a unitless number, and because it is built from two totals it does not equal the average of the per-session values. GA4 reports the same measure as views per session.

FAQ

Sources:GA4 — Analytics dimensions and metrics