Error page views: not-found pages, and what sent people there
Every error page view is someone who did not get what they came for.
Views of your not-found and error pages, and the page or outside source that led there, so you know where to fix the 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
quietstats spots error pages by their address (404, not-found, error, oops), counts views, and for each view looks at the page before it in the visit, or the source if the visit started there.
Why it matters
Every error page view is someone who did not get what they came for. Fixing the link on your own page, or redirecting an outside one, wins those visits back.
How it works
- Open your dashboard, go to Deep dives (or Reports on a phone) and open Analysis lab.
- Under Content, tap Error page views. 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
- Error pages and causes under 5 are hidden
- Spots error pages by address only
- 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
My not-found page keeps the broken address. Will this see it?
Not by address. Add data-qs-event="404" to that page and use Event look-up.
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
See your trafficJavaScript errors: which scripts break, on which pages
Behaviour and contentDuplicate addresses: one page, several addresses
Data in and outExit rate movers: pages where more people now leave
Behaviour and contentAttention share: where your visitors really spend their time
Behaviour and contentSearch answers: the page each site search leads to
Behaviour and contentLikely mistyped addresses: broken links hiding in your pages list
Behaviour and contentPrivacy proof page and badge for your site
Privacy and performance
All behaviour and content features → · All features → · Docs: Error page views 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.