Errors #

This section is designed to help you detect and understand the errors your users encounter while browsing your website. With this information, you can improve user experience, optimize your SEO, and most importantly, avoid losing conversions.

Error chart #

In this chart, you will see the number of errors that occurred over a specified period, which you can adjust by selecting the date in the top-right corner. Errors are categorized by type:

• 4xx Errors: These are caused by issues with user requests, such as pages not found (404) or unauthorized access (401).
• 5xx Errors: Errors related to server issues, such as internal failures (500) or services unavailable (503).
• Other Specific Codes: You will also see less common but equally important codes, giving you a more complete picture of what’s happening.

Detailed error list #

Here is where you can dive into each issue. The list provides precise information about every error that occurred on your site:

• Link: The exact URL that caused the error, allowing you to identify which pages need attention.
• Error Code: The specific HTTP code (404, 500, etc.) that gives a clue about the nature of the problem.
• Country: Where the error originated. This is crucial if you’re optimizing your site for specific markets or notice certain countries experiencing more issues than others.
• Device: Knowing if errors occur more on mobile, tablets, or PCs helps you focus on the right platforms.
• Date and Time: Seeing when each error occurred allows you to cross-reference with other site actions, such as campaign launches or software updates.

This information is essential for identifying behavior patterns, such as errors being concentrated on a specific day or device type, helping you resolve problems faster.

Adding filters and exporting files #

In the top-right corner of the Errors section, you will find the following buttons:

Period customization (1) #

You can adjust the dates to view errors from the last week, month, or a custom period. This helps you analyze the impact of recent updates on your website.

Add filter (2) #

You can filter errors by error code, path, country, or device.

Export to .csv or .pdf file (3) #

If you need to share this information with your team or consultants, you can easily export it in CSV or PDF format. This is ideal for generating reports or having the data handy without needing to be inside the platform.

Why is it important to analyze rrrors? #

Having this information at your fingertips allows you to:

• Detect and Correct Broken Links: With site updates or changes, some URLs can become obsolete. Knowing exactly which ones help you quickly fix them and avoid frustrating users.
• Identify Issues on Specific Devices or Regions: If you notice more errors in certain countries or on mobile devices, it could indicate compatibility issues that need review. Maybe your site isn’t loading properly on certain browser versions or slower networks.
• Prioritize Error Resolution: Some errors, like a 500, are much more critical than a 404 and require immediate attention. Overtracking helps you efficiently prioritize to ensure critical issues aren’t overlooked.

Common error codes and how to fix them #

Below is a quick guide on common error codes, so you know how to interpret them and what steps to take to resolve them:

HTTP 4xx errors (client errors) #

These errors occur when something is wrong with the request the user makes to the server. Here are some common examples:

• 400 Bad Request: This happens when the user’s browser sends a request the server cannot process. It may occur if the URL is misspelled or if important parameters are missing.
• 401 Unauthorized: The user is trying to access a page or resource without the necessary permissions. Generally, this is resolved by prompting the user to log in.
• 403 Forbidden: Similar to a 401, but in this case, access is blocked even if the user has logged in. This may be due to server or permission settings.
• 404 Not Found: A classic. The user tries to access a page that doesn’t exist. This could be due to an incorrect URL or because the page was deleted or moved without creating a redirect.
• 408 Request Timeout: The server didn’t receive the full request from the user in time. This could be caused by connectivity issues or an overloaded server.

HTTP 5xx errors (server errors) #

These errors are more serious because they indicate something is wrong with the server. Some of the most common are:

• 500 Internal Server Error: A generic error indicating that something went wrong on the server. It could be due to a problem with the site’s code or server infrastructure.
• 502 Bad Gateway: This occurs when a server acting as a gateway or proxy receives an invalid response from another server. It’s common on sites that rely on external services.
• 503 Service Unavailable: This happens when the server is temporarily out of service, either due to maintenance or overload. Usually resolves itself, but if it persists, it may require server configuration adjustments.
• 504 Gateway Timeout: Similar to a 502, this error appears when an intermediate server doesn’t respond in time, causing a communication failure.

Practical tips for avoiding errors #

• Correct Redirects: Whenever you delete or move a page, create a 301 redirect to avoid 404 errors.
• Continuous Monitoring: Use Overtracking regularly to identify errors before they affect a significant number of users.
• Testing on Different Devices: Ensure your site looks and functions well on mobile devices and tablets, where errors can be more frequent due to incompatibilities.