Is your site quietly killing conversions?
Fix it fast with our 150-Point CRO Checklist:
• Find out what’s broken
• Learn how to fix it (and turn clicks into cash)
• Use the same tactics that drove $4B+ in ecommerce revenue
Pageview
Short description
A pageview is recorded each time a page on your site loads or reloads in a browser. It measures how often content is viewed, not how many people visit. Pageviews help reveal navigation paths and content interest.
Why it matters
Pageviews show which pages attract attention and which do not. Spikes in product pageviews often follow influencer mentions or ads, which helps you prioritize homepage features, inventory, and ad budgets. Comparing pageview patterns before and after a redesign shows whether changes improved discoverability. Low pageviews on critical pages can indicate internal linking issues or weak search visibility. Looking at pageviews by template, for example PDP versus blog, helps the team size content value and merchandising impact.
How it works
Analytics scripts fire a pageview when the page is rendered. Single-page apps need virtual pageview events to track in-page navigation. A single session can contain many pageviews as a person moves from category to product to cart. Auto-refreshes, bots, and internal users can inflate counts, so filters are necessary. Pair pageviews with time on page and scroll depth to understand visibility and attention.
Example in ecommerce
A sneaker retailer sees pageviews for a limited-edition model spike after a creator post. They add a homepage hero, update product badges, and increase paid search bids for that SKU. Pageviews continue to grow and convert, so the team orders an additional batch and plans a restock email. The same approach later helps them ride a second trend with faster execution.
Common mix-ups
Pageviews are not sessions, which count visits, and they are not unique visitors, which count people. They also differ from events that capture micro actions like clicks or video plays. Using pageviews alone can mislead, so always pair them with engagement and conversion metrics.
Best practices
- Track pageviews for PDPs, PLPs, cart, and checkout.
- Group pages into templates for comparisons that matter.
- Filter bot and internal traffic to protect signal quality.
- Monitor PDP view to add-to-cart ratio to assess product appeal.
- Set alerts for sudden drops on critical pages.
Industry benchmarks
- Large catalogs drive higher pageviews per session than focused stores.
- Navigation changes can shift pageview distribution even when totals stay flat.
- Use your own medians and top quartiles by template to set expectations.
Related terms
You made it all the way down here?
Might as well give us a shot, right? It'll change the way you approach CRO. We promise. In fact, our friend Nate over at Original Grain used element-level revenue data from heatmap to identify high-impact areas of his website to test, resulting in a 17% lift in Revenue per Session while scaling site traffic by 43%. Be like Nate. Try heatmap today.
