Don't let 404 errors drive visitors away: Here's how to track and fix them

When building a website, ensuring a seamless browsing experience for visitors is crucial. However, encountering a 404 error page, which indicates that the requested page cannot be found, can be frustrating for users and may result in them leaving your site. To prevent this from happening, it's essential to track these error pages and address any issues promptly.

In this article, we'll walk you through the steps to track 404 error pages in Howuku.

Firstly, you need to have a 404 error page. With a Content Management System (CMS), you can easily set up a custom 404 page. For example, in WordPress, all 404 pages loading a custom 404 template. If you don't use a CMS, you can usually specify a 404 custom page in your web server configuration file.

To track 404 error pages in Howuku, follow these steps:

  • View Recordings with the 404 Error Page

In the Recording features, select Search Users > Visited URL and paste the 404 URL to filter the recordings that have recorded the error page.

Session Recording Filtering
  • Generate a Heatmap for the 404 Error Page

In the Heatmap features, enter the URL that you want to visit and go to Search Users > Visited URL. Paste the 404 URL to identify the website element that users clicked on and brought them to the 404 URL. You can also enter the 404 URL to generate a heatmap.

Heatmap filtering
  • Event Tracking on the 404 Error Page

Add the event Javascript API on the 404 error page.


Whenever a user accesses the 404 error page, Howuku will record it. You can see how many visitors encountered a 404 error, where they were coming from, and what pages they were trying to access. This information can help you identify any issues on your site that may be causing 404 errors and address them accordingly.

Event Tracking

By implementing these steps, you can effectively track 404 error pages on your website and provide your visitors with a better browsing experience.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us