Pages per session: what it means and how to read it

What pages per session actually measures

Analytics tools divide the total number of page views by the number of sessions in a period. If a visitor lands on your homepage, opens a catalog, two product pages and the cart, that is five views in one session. Reloading a page counts too, so some of the depth may be nothing more than a refresh. Yandex Metrica calls this metric page depth, while Google Analytics 4 reports a similar figure as views per session.

There is also a technical trap. On single-page sites and in interfaces where sections change without a new URL, the number comes out artificially low unless the tracking code receives a page-change event. That is a setup problem, not visitor behavior, so confirm your tracking works before you analyze anything.

When a high number is a good sign

On sites where choosing takes comparison, more pages usually means more interest. What matters is that orders, calls, Telegram messages and Click or Payme payments grow along with it.

• Online store: a shopper compares models and moves between categories
• Blog or media site: a reader follows links to related articles
• Service catalog: a clinic, repair studio or training center shows several directions, and the visitor studies them before choosing

When a high number is a warning

Sometimes sessions are long in page count but produce no leads. In that case the visitor is not exploring, but wandering in search of an answer.

• Key information, such as price or address, is buried deep
• The menu is confusing and people circle between sections
• An article is split across several pages just to inflate views
• The order form has several steps, each loaded as a separate page

Why a low number is not always bad

Imagine someone clicks an Instagram ad, lands on a product page and orders at once. That is one page per session, and it is an excellent result. The same goes for a one-page landing page, a contacts page where the visitor finds a phone number and calls, or an article that fully answers a question. Trying to push the number up in these cases only makes the customer's path worse.

How to analyze pages per session properly

A sitewide average blends very different behavior, so split the data and read it next to your goals. Depth with no link to leads says almost nothing.

• Traffic source: search, ads, social networks and Telegram links behave differently
• Device: phone visitors usually open fewer pages, and a combined figure can hide mobile navigation problems
• Landing page: if blog readers move on to a service page, your internal links work; if they leave, make service links more visible
• Converting and non-converting sessions: this shows how many pages people typically need before deciding

How to raise it sensibly, and what to avoid

The aim is not to keep visitors on the site at any cost, but to show them a useful next step. Simple things work: related products on a product page, links to examples of work and reviews on a service page, clear breadcrumbs, a related articles block. Avoid splitting texts into pages, adding mandatory intermediate screens or hiding prices. The figure rises, but conversion falls.

Pages per session in end-to-end analytics

A good habit is to test a hypothesis: change a structure or add a block of links, then compare depth and goals for the same segment a month later. If your blog rarely leads to services, add links to relevant pages inside articles and check whether the number of leads changes. To base such conclusions on data from your analytics counter, CRM and ad accounts rather than one metric, you need end-to-end analytics. If you want help setting it up or reviewing the reports for your site, you can discuss the task with the markdev team.