Bounce rate has been the SMB-owner scapegoat for two decades. “Our bounce rate is 70%, no wonder we’re not converting.” The trouble is that bounce rate doesn’t mean what most operators think it means — and chasing it has led plenty of well-intentioned site rebuilds nowhere.
What bounce rate actually measures
In old Google Analytics (Universal), a ‘bounce’ was a session with exactly one pageview and no other interaction. In GA4, the definition shifted: a bounce is a session shorter than 10 seconds that doesn’t trigger a conversion event or view a second page. Both definitions miss the same thing — whether the visitor actually got what they came for. The GA4 events that actually matter are the metric to chase instead.
When bounce rate is fine
- On a contact page: visitor lands, calls the number, leaves. That’s a successful session and a 100% bounce.
- On a service-detail page with a phone CTA: same pattern.
- On a blog post that fully answered the visitor’s question: high bounce + long session duration = the post worked.
When bounce rate is a problem
When the bounce comes from a paid landing page where you needed a form fill, when the session duration is under 5 seconds (the visitor never engaged), or when the bounce is concentrated on pages that should be funneling visitors deeper. Look at bounce rate alongside session duration and conversion event firing — the three together tell you what bounce rate alone never can.
The metrics you should be tracking instead
- Conversion rate per traffic source. Google Organic vs. Google Paid vs. Direct vs. Referral — they almost always perform very differently. (Run a UTM convention that survives a year or the source split is noise.)
- Form-completion rate (not just form-view rate). Where in the form do visitors drop off?
- Phone-call attribution. Use a call-tracking number per source so you actually know which channel produced the call.
- Time-to-contact for leads. From form submit to your team’s first response — this is the metric that hides under bad conversion rates.
