Detour finder: the links your pages are missing
When many people go back to the home page or search to get from one page to another, a direct link from the first page would save them the trip, and fewer will give up on the way.
Journeys that go page → home or search → another page, again and again: a sign of a missing direct link.
Why quietstats: you get this without cookies, a consent banner or storing IP addresses, in every plan including Free.
In every plan, including Free. Behaviour and content.
📘 Step-by-step guide, with screenshots and diagrams →
Start free, no cardSee live demo
- No cookies or consent banner
- No IP addresses stored
- Groups under 5 visitors hidden
- 845-byte script
- Free plan, no card


What it is
In visits of three or more pages, quietstats looks for a page, then your home page or site search, then a different page. Pairs that happen in 5 or more visits are listed with the hub people went through and how often the detour happened.
Why it matters
When many people go back to the home page or search to get from one page to another, a direct link from the first page would save them the trip, and fewer will give up on the way.
How it works
- Open your dashboard, go to Deep dives (or Reports on a phone) and open Analysis lab.
- Under Suggestions, tap Detour finder. You can also search for it on the All reports screen.
- Pick a date range (and any options at the top), read the “How to read this” notes, and download any table as CSV.
Privacy: what is and isn’t collected
Collected
- Nothing new: it reads the pageviews, events, goals or daily totals you already have
Never collected
- Anything about a single visitor
- Links between days: visitor ids still reset at midnight
- Cookies, localStorage or anything else stored on the visitor’s device
- IP addresses or user agents (used in memory, then discarded)
- Anything that links a visitor across days (the visitor ID resets daily)
Rows and limits
- Pairs seen in fewer than 5 visits are hidden
- Only visits with 3 or more pages count
- Up to 92 days and 200,000 pageviews per screen
- Read from the database only when you open it, then kept for 10 minutes
“Rows” are database rows written, which is what our hosting is billed on. Reads are not rows written. Methodology →
Questions
Is going back home always bad?
No, but the same detour by many people is a pattern. Add a link or button for it and see whether the detour shrinks.
Does it store anything new?
No. It is worked out from the pageviews and events you already have when you open the screen, and only the totals are kept for 10 minutes.
Related features
Behaviour and contentEntry and exit pairs: where visits start and end
Behaviour and contentSection flow: how visitors move between sections
Behaviour and contentBounce above expected: pages that bounce more than their traffic explains
Behaviour and contentVisit survival curve: where visits end
Behaviour and contentLikely mistyped addresses: broken links hiding in your pages list
Behaviour and contentChannel gap by page: pages that suit one channel and not another
Behaviour and contentMobile gap finder: pages that fail on phones
See your traffic
All behaviour and content features → · All features → · Docs: Detour finder guide → · Compare features with other tools →
Guides on this topic
Set it up
Nothing to set up: it works with the standard one-line script.
<script data-host="https://quietstats.co.uk" data-dnt="true" src="https://quietstats.co.uk/js/script.js" id="YOUR_SITE_ID" async defer></script>Try it on your own site
Free during launch: one site and 5,000 pageviews a month, no card needed. After launch, paid plans start at £5 a month.