Bounce rate: definition and why it misleads
Bounce rate is the percentage of sessions with only one interaction. Its definition shifted: classic tools counted single-pageview sessions; GA4 derives it from engaged sessions instead. A high bounce rate is not inherently bad — for a single-answer page it can mean success — which is why context matters more than the number.
What this means
Bounce rate is the share of sessions in which the visitor did one thing and left. Classically, a 'bounce' was a session with a single pageview and no further hit. GA4 reframed it: bounce rate is the inverse of the engagement rate, where an 'engaged session' lasts long enough, has a conversion, or has multiple pageviews.
Why it misleads
Because the definition changed, the same site can show very different bounce rates in different tools — they are not measuring the same thing. And a high bounce is not automatically a problem: a recipe page or a definition page that answers the question in one view will bounce by design. Judge it against what the page is for.
- Classic: single-pageview sessions
- GA4: inverse of engaged-session rate
- High bounce can mean satisfied intent, not failure
How it appears in analytics and logs
A high bounce rate means many visits ended after one interaction. Whether that is good or bad depends entirely on the page's job — an answer page satisfying intent and a leaky landing page both show high bounce.
Diagnostic use case
Interpret bounce rate against page intent rather than as a universal quality score, and know that the definition differs between GA4 and older tools.
What WebmasterID can help detect
WebmasterID measures engagement from first-party events, so you can read single-interaction visits without third-party cookies or cross-site tracking.
Common mistakes
- Comparing bounce rate across tools that define it differently.
- Treating any high bounce rate as a problem to fix.
- Ignoring page intent when reading the number.
Privacy and accuracy notes
Bounce rate is computed from interaction counts, not identity. No personal data is needed to derive it.
Related pages
- Pageviews: what the metric counts
A pageview is recorded when a page is loaded (or a virtual page is rendered in a single-page app). It is the oldest web-analytics metric and the easiest to misread: pageviews count loads, not people, and modern apps and prefetching can inflate or hide them. This page defines the metric and its caveats.
- Conversion rate: definition and denominators
Conversion rate is the share of some base that converted. The trap is the denominator: conversions per session, per user, and per unique visitor give different numbers and mean different things. Without stating the base, a conversion rate is ambiguous — and comparing rates with different bases is meaningless.
- Bot traffic in analytics: filtering it out
Bots — crawlers, scrapers, monitors, scanners — generate requests that, unfiltered, inflate pageviews and distort every metric. Client-side analytics often misses bots (many do not run JavaScript) or miscounts the ones that do. Server-side classification at ingest is the reliable way to keep bot traffic out of human reports.
- Website observability
Engagement and traffic signals on one fabric.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.