Back-and-forth pages: returns and detours
A pricing table or a menu is meant to be returned to.
Pages people come back to in the same visit (A → B → A), and detours that send people straight back where they came from.
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
Within each visit, quietstats spots the pattern of going from page A to page B and straight back to A. It lists pages people return to, with how many visits returned, how many visits saw the page and the return rate, and the detours (A to B and back) with their counts. Anything under 5 visits is hidden.
Why it matters
A pricing table or a menu is meant to be returned to. A page people bounce straight back from may not answer their question. Both are worth knowing.
How it works
- Open your dashboard, go to Deep dives and scroll to Analysis lab.
- Under Content, tap Back-and-forth pages.
- Pick 7, 30 or 90 days (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 (and goals, events or speed checks) 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
- Counts under 5 visits are hidden
- 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 a return a bad sign?
Not for hub pages such as menus, lists and pricing. It is a sign worth checking for the detour page, which people leave straight away.
Does a page refresh count?
No. The pattern needs a different page in between.
Related features
Behaviour and contentExit pages and where visitors went next
Behaviour and contentVisitor journeys
Behaviour and contentReading quadrant: read, skimmed, stuck or missed
Behaviour and contentPages read together: pairs and “read next” ideas
Behaviour and contentSite sections: your site as a folder tree
Behaviour and contentNew page half-life: how fast attention fades
Behaviour and contentTop landing pages by source
Sources and campaigns
All behaviour and content features → · All features → · Docs: Back-and-forth pages 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.