Error pages
Pages answered with an error are counted on the Errors page, and kept out of every other figure.
The Errors page shows which addresses fail, how often, and where their visitors came from, which is where broken links show up. Chrome, Edge and Firefox report errors by themselves. Safari needs one attribute on your error pages’ tag, usually a single change to the template they share.
What counts as an error
A page load answered with an HTTP status of 400 or more: 404 Not Found, 410 Gone, 500 Internal Server Error and the rest. A redirect, or any other status under 400, is an ordinary page. Pages counted before 23 September 2026 aren’t marked as errors, and show as they always did.
Errors are left out of everything else: pageviews, visits, visitors, sources, speed, engagement and goals. A visit that started on an error page is left out whole, with its visitor and its goals. A visit that only passed through one keeps its other pages.
Safari needs data-status
Chrome and Edge 109 and later, and Firefox 129 and later, tell the script the status of the page they
loaded. Safari doesn’t, so give the tag on your error pages a data-status attribute with the
status the page is served with:
<script async data-domain="example.com" data-status="404" src="https://fiveb.ar/js/tally.js"></script>Most sites have a template for each error, or one for all of them with the status to hand, so it’s one
change: data-status="{{ status }}", or however your templates write it. Ordinary pages need
nothing.
Without it, a Safari visitor’s 404 counts as an ordinary page and turns up among your top pages. Where the
browser and data-status both give a status, data-status wins. Only a whole number from
100 to 599 is read.
Where errors show
On the Errors page, reached from the Overview, Speed, Errors and Bots switch under the site’s name, which shows the error rate beside it. It keeps the dashboard’s dates and filters, and shows:
- the errors, the pages they were on, and the error rate, the share of page loads reporting a status that were errors, to one decimal place under 10%, each beside the period before
- a chart of the errors for each day, week or month of the range, and the share of page loads whose status is known
- the errors by status, by the source the visit arrived from, which is where broken links show up, and by device; click any of them to filter the page by it
- every page answered with an error, by status and path, to search and page through
Under a filter, the Errors page counts the error pages that match, by their own source, country and the rest. Filtered by an entry or exit page, or by a goal, it has nothing to show.
A status filters the Errors page alone, since the Overview and Speed leave errors out, so it stays behind when you switch to them. Filtered by one, such as 404, the error rate is that status’s share of the page loads reporting a status, and the rate beside Errors in the switch is still every error’s.
Single-page apps
Only a page the browser loaded has a status. A page a single-page app moves to has none, so a not found page the app draws is counted as an ordinary page.