Pages per Session (sometimes written as pages/session) is the average number of pages a user views during a single session on your site. It’s a compact way to gauge depth of browsing. High values often signal curiosity or strong internal linking; low values can indicate quick answers or weak navigation. Treat it as an average, not a verdict—one viral article can skew the number.
Formula
Pages per Session = Total Pageviews ÷ Total Sessions
Where a pageview is any load of a tracked page, and a session is a continuous visit window.
Mini example
If your site logged 1,200 pageviews across 400 sessions, then:1,200 ÷ 400 = 3.0 → Pages per Session = 3.0
Tiny table (sample day)
| Day | Sessions | Pageviews | Pages/Session |
|---|---|---|---|
| Mon | 320 | 860 | 2.69 |
| Tue | 280 | 1,050 | 3.75 |
| Wed | 300 | 780 | 2.60 |
How to use it
- Content depth & IA checks. If pillar pages point cleanly to clusters, this metric usually rises. Combine with bounce rate and engagement rate to tell whether people stick or just click around.
- Channel comparison. Organic search might show higher depth than paid social; that’s a content–intent mismatch to fix in targeting or landing pages.
- Navigation experiments. Test internal links, related posts, and sidebar patterns; watch for sustained lifts, not one-day spikes.
Read it with nuance
- Not quality on its own. A knowledge-base article that resolves the problem in one page is success, not failure.
- Device mix matters. Mobile friction often lowers depth; audit speed and above-the-fold links.
- Avoid apples-to-oranges. Content length, markets, and seasonality can shift averages; compare like for like and use medians when possible.
Related metrics
Cross-check with average session duration, exit rate, and unique visitor to understand whether deeper browsing maps to actual satisfaction or just hunting for the right page