What is an exit page? How to read exit pages and exit rate

Every visit ends somewhere, so every page collects exits. What an exit really is, how exit rate differs from bounce rate, which pages are meant to lose people, and how to tell a page that finished the job from one that lost the visitor.

9 min read

Summarize with

In this article
  1. 1What counts as an exit
  2. 2Exits, exit rate and bounce rate
  3. 3Pages that are meant to end a visit
  4. 4Pages where a high exit rate is worth a look
  5. 5Rule out the measuring first
  6. 6Why two tools disagree on exits
  7. 7How to read an exit report, step by step
  8. 8What exit data can't tell you

An exit page is the last page someone viewed in a visit. Every visit has exactly one. If someone lands on your home page, reads a blog post and then leaves, the blog post is the exit page for that visit.

That sounds like bad news, and usually it isn't. Everyone leaves eventually, so every page that gets traffic collects some exits. The useful question isn't which pages people leave from. It's which pages people leave from when they were meant to go somewhere else.

This guide covers what an exit is, how exit rate differs from bounce rate, what distorts the numbers and how to read the report. It works with any analytics tool that lists exit pages. The details about specific tools come from their own documentation, as of November 2026.

What counts as an exit

An analytics tool can't tell when someone has left your site for good. It records pageviews, and in some tools other events such as clicks, groups them into visits, and labels the last page in each visit as the exit.

A visit ends when nothing new arrives for a while. By default, Google Analytics 4 ends a session after 30 minutes of inactivity, according to Google's help page on sessions, and the timeout can be changed for each web data stream. Plausible's metric definitions give the same 30 minutes. Other tools choose their own window, so check yours.

So an exit is the absence of a next pageview, not something the visitor did. All of these look the same in the report:

  • Closing the tab or the browser.
  • Clicking a link to another website.
  • Going on to a checkout, booking page or app on a different domain.
  • Downloading a file, or tapping an email address or phone number.
  • Leaving the tab open past the timeout. If they come back later and click through to another page, that click starts a new visit, and the page they were on has already counted as an exit.
  • Finding the answer and being done.
An exit is the absence of a next pageview. It says where a visit stopped, not why.

Exits, exit rate and bounce rate

Three figures get mixed up here.

FigureWhat it countsDivided byWhat it answers
ExitsVisits that ended on the pageNothing, it's a countWhere do visits end?
Exit rateExits from the pageViews of the page (in some tools, visits that included it)How often does a view of this page end the visit?
Bounce rateVisits that saw only this pageVisits that started on the pageDo people who arrive here go any further?

In most cookie-free tools a bounce is a visit with one pageview, so that page is its entry and its exit at once. GA4 counts a bounce differently, as a session that wasn't engaged, but a bounced session still ends on the page it started on. Every bounce is an exit, but an exit can also end a visit that took in many pages. The guide to bounce rate covers both definitions.

The two rates look at different visits. A page's bounce rate only counts visits that started there. Its exit rate counts every view of the page, wherever the visit began. A small example makes the difference concrete:

VisitPages, in orderEntryExit
AHome → Pricing → Sign-upHomeSign-up
BBlog postBlog postBlog post (a bounce)
CHome → Blog postHomeBlog post

The blog post ended both visits that saw it, so every view of it was an exit. Only visit B started there, though, so its bounce rate is about B alone. Home started two visits and ended none. Read the exit counts on their own and the blog post looks like the problem. Read what each page is for, and it may simply be the page that answered the question.

Exit rate is normally defined as exits divided by the page's pageviews, which is how Plausible and Matomo's help pages define it. Not every report divides by the same thing: the exit rate in Matomo's source code divides by the number of visits that included the page, which comes out higher for a page people open more than once in a visit. If your tool shows no exit rate at all, work it out from the page's exits and its views over the same dates.

Pages that are meant to end a visit

Some pages are the end of the road by design, and a high exit rate there means they're doing their job. Plausible's description of its exit pages report makes the same point about order confirmations and contact success pages.

Confirmation and thank-you pages

The order went through or the form was sent. There's nothing left to do on the site.

Contact pages

If the page shows an email address, a phone number or opening hours, the next step happens outside your site, where the analytics can't see it.

Answer pages

A blog post or docs page that answers one question. The reader got what they came for and has no reason to open another page.

Hand-offs to another domain

A hosted checkout, a booking tool, an app store listing, or an app tracked as a separate site. The exit may well be a sale.

Download pages

The file is the goal. A PDF or a zip file runs no tracking script of its own, so the visit usually ends on the page that linked to it.

Don't try to push these numbers down. Splitting a page in two lowers its exit rate without helping a single reader.

Pages where a high exit rate is worth a look

Other pages exist to move people on. A high or rising exit rate there is worth a closer look:

  • A pricing page, when the next step, a sign-up or a checkout, is on your own domain.
  • A step in a sign-up or order flow hosted on your site.
  • A product or feature page with an obvious next action.
  • A category or search results page, where people should be picking something to open.
  • A page you changed recently.

Worth a look isn't the same as broken. It means open the page and check it, with the steps further down.

Rule out the measuring first

Before acting on an exit number, make sure it describes your visitors and not your setup.

  • Single-page apps. If the site changes pages without a full page load and the script doesn't record those changes, every visit looks one page long, and the first page becomes the exit page for nearly everyone. Open the site, click through a few pages and check that each one shows up. The Next.js guide walks through that test, and the same clicks work on a site built any other way.
  • A page without the script. If one template or section lacks the tag, visits seem to end on the page before it. A sudden rise in exits on a page that links to a new section is a typical sign.
  • Separate sites for separate domains. If the marketing site and the app are tracked as two sites, every move from one to the other is an exit on the first.
  • Several tabs. People open links in new tabs and read them in any order. A visit is put together in time order, so the page opened last isn't always the page read last.
  • Automated traffic. A monitor or scraper that loads one page at a time adds an exit with every load. How much of it reaches the report depends on how your tool filters bots.
  • Small numbers. A page with a handful of views can show a very high or very low exit rate by chance. Use a longer date range, or leave low-traffic pages out.

Why two tools disagree on exits

Two tools will list different exits for the same page, and that's normal. They split visits on different timeouts, filter different bots and are stopped by different blockers. They don't always mean the same thing by an exit, either. Google's reference for GA4 defines Exits as how many times the last event in a session happened on a page, which isn't always the last page that loaded. Check that both tools rise and fall on the same days, and read why no two analytics tools agree on your traffic for where the rest of the gap comes from.

How to read an exit report, step by step

  1. Pick a long enough date range. Several weeks gives a steadier picture than a single day, especially for pages with modest traffic.
  2. Put exits next to pageviews. Work out the exit rate for your most viewed pages if your tool doesn't. A spreadsheet is fine.
  3. Label each page. Is it meant to end a visit, or meant to lead somewhere? Use the two lists above.
  4. Sort the pages meant to lead somewhere by exit rate, and look at the top few only.
  5. Open each one on a phone and on a desktop. Is the next step visible without hunting for it? Do the links work? Does the page load quickly?
  6. Split by device or source, if your tool can. A page that loses mobile visits far more often than desktop ones often has a layout or speed problem on small screens. A page that loses visits from one source may be getting people who expected something else.
  7. Compare with an earlier period. A change in a page's exit rate says more than the rate on its own.
  8. Change one thing, then wait. Give it enough traffic to compare, then check the same figures again.

What exit data can't tell you

Exit data says where visits ended. It doesn't say why, or whether the person was happy. A visitor who read your docs page, solved the problem and left looks exactly like one who gave up.

To judge an exit, pair it with something that shows an outcome: sign-ups, sales, support emails, replies. If exits from the pricing page rise while sales hold steady, those exits may simply be people on their way to a checkout on another domain. Watching a few recorded visits, if your tool records them, or asking a one-question survey on the page can show more of the why.

Treat the exit report as a list of pages to check, not a list of pages that failed.

Lomen shows exit pages as a tab of the Pages card, next to Top pages and Entry pages: the pages where the most visits ended, each visit counted once and split on a 30-minute gap. It lists exits as counts, not as a rate, so for a page that appears in both tabs, divide its exits by the views Top pages shows for it. The script records page changes in single-page apps, crawlers and automated browsers are dropped, and pageviews only count from the domain you added and its subdomains. Lomen AI, a chat in the dashboard, answers questions about those pages from the site's own figures. The standard script sets no cookies and keeps nothing in the visitor's browser, and Lomen never stores IP addresses. Session recordings, for playing some visits back, only run with the With cookies version of the snippet, which keeps a random ID in the visitor's browser and needs a cookie banner. Lomen has no funnels or custom events, so it can't follow a multi-step sign-up as one flow. It's free during the public beta.

Numbers you can ask questions

Lomen is one cookie-free script: sources, campaigns and AI referrals on one dashboard, and an AI that answers from your own figures. Free during the beta, no credit card.