Top pages
Everything being viewed, ranked, with the traffic each one accounts for.
- Ranked by visitors
- Filterable by any dimension
- Open the live page from any row
Features·Web analytics
Which pages carry the site.
See which pages get the most views, which bring people in and which lose them.
What it does
Three lists of pages.
A popular page is rarely the one people arrive on or leave from.
Entry pages
The pages where people land first, often different from the ones you planned.
- First page of each session
- Pairs with the acquisition breakdowns
- Shows what search and social really send
Exit pages
The last page of a session, and a good place to look for things to fix.
- Last page of each session
- Compare against entries
- The first place to look for a leak
How it works
Use it in three steps.
01
Collect
Pageviews arrive from the snippet on their own, with no setup per page.
02
Compare the three lists
A page high on entries and exits both is a bounce; a page high on views alone is a stop on the way.
03
Build the funnel
Turn the drop you found into named steps and watch the rate move.
Read next
Usually read beside this one.
Product analytics
See where they fall out.
See where people drop off between steps.
Read moreProduct analytics
The routes visitors take.
Map the paths people take through your site.
Read moreWeb analytics
Search traffic, joined to what it does next.
See your Search Console data next to your traffic.
Read moreFAQ
Questions about this one.
What people ask before they switch it on.
Are query strings grouped or separate?
Grouped. The query string is dropped when a page is stored, so /search?q=a and /search?q=b are one row, and campaign traffic to a page does not fragment your list. UTM parameters are read before that and kept as their own fields.
What counts as an exit page?
The last page viewed in a session. If someone comes back later that is a new session with its own entry.
Can I see the sessions behind a page?
Yes. Filter by the page, or click it in the Overview’s pages card. The filter carries into Sessions and on to one visitor’s timeline.
Does this work for a single-page app?
Yes, with nothing to add. Client-side route changes are picked up on their own, so every screen is a pageview. Hash-based routes (/#/settings) share one row, because only the path is stored.
See your own numbers today.
Free up to 100k events a month · no credit card