---
title: "Page not found analytics"
slug: "page-not-found-analytics"
description: "The Page not found analytics page shows the list of URLs for which 404-page error is displayed after the Uniform Resource Locator is accessed."
updated: 2026-07-23T06:34:41Z
published: 2026-07-23T06:34:41Z
canonical: "docs.document360.com/page-not-found-analytics"
excludeFromExternalSearch: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.document360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Page not found analytics

The **Page not found** analytics page in Document360 displays all URLs within your knowledge base domain that returned a 404 error, along with details about who accessed them and when. Use it to identify broken or deleted URLs and set up redirect rules to fix them before they affect your readers or your search engine rankings.

---

## Why use Page not found analytics

- Use it to spot URLs that readers or search engine bots are hitting but that no longer exist, so you can set up redirects promptly.
- Use it to distinguish between reader-facing 404 errors (Browser) and bot-generated ones, so you can prioritize fixes by impact.
- Use it after a content restructure or article deletion to confirm that redirect rules are working as expected.

---

## Access Page not found analytics

In the knowledge base portal, navigate to **Analytics** (<span class="fa-duotone fa-solid fa-chart-mixed"></span>) in the left navigation bar, then click **Page not found** in the left navigation pane.
<div align="center">
<img src="https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/Screenshot-Page_not_found_analytics.png" class="article_image" alt="Page not found analytics overview showing total pages, browser, unknown, and bot counts.">
</div>

The Page not found analytics page opens, showing data for the last 7 days by default.

### Apply filters

1. Click the **Date** filter dropdown and select a predefined range (such as **This month** or **Last month**), or choose **Custom** to specify a date range.
2. Click the **All user agents** dropdown and select a user agent type to filter the data.

:::(Info) (<p class="fa-regular fa-circle-exclamation" data-type="icon"></p> NOTE)
The page refreshes when the **Date** filter is applied. Always apply the **Date** filter first, then the **All user agents** filter. Analytics data is available from July 7, 2023 onwards when using a custom date range.
:::

---

## Understanding Page not found metrics

The overview page shows four metric tiles:

<table>
<thead>
<tr>
<th>Metric</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Total pages</strong></td>
<td>Total number of URLs that returned a 404 error in the selected period.</td>
</tr>
<tr>
<td><strong>Browser</strong></td>
<td>URLs accessed through a browser that returned a 404 error.</td>
</tr>
<tr>
<td><strong>Unknown</strong></td>
<td>URLs returning a 404 error from an unidentified user agent type (not Browser or Bot).</td>
</tr>
<tr>
<td><strong>Bot</strong></td>
<td>URLs returning a 404 error when accessed by bots such as search engine crawlers (Google, Bing, Yahoo).</td>
</tr>
</tbody>
</table>



### URL report

Below the tiles, the URL report lists all 404 URLs with the following details:

<table>
<thead>
<tr>
<th>Field</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>URL</strong></td>
<td>The URL that returned the 404 error, along with how many times it was accessed.</td>
</tr>
<tr>
<td><strong>User agent type</strong></td>
<td>The type of user agent that accessed the URL (Browser, Bot, or Unknown).</td>
</tr>
<tr>
<td><strong>User agent</strong></td>
<td>The specific access type within the user agent hierarchy.</td>
</tr>
<tr>
<td><strong>URL referrer</strong></td>
<td>The page that linked to the 404 URL.</td>
</tr>
<tr>
<td><strong>Date (UTC)</strong></td>
<td>The date the URL was accessed.</td>
</tr>
</tbody>
</table>

Hover over a URL to reveal the **Copy** (<span class="fa-regular fa-copy"></span>) icon and copy it.

Click **Export CSV** to download the full URL report in `.csv` format to your local storage.

---

## Best practices

- **Set up a redirect rule whenever you delete, deprecate, or hide an article.** This prevents the old URL from returning a 404 error. See <a href="https://docs.document360.com/docs/article-redirect-rules" target="_blank">Article redirect rules</a> for details.
- **Change article URLs only when necessary.** If you do change a URL, add a redirect rule immediately so existing links continue to work.
- **Double-check URLs when adding hyperlinks.** Linking to a non-existent or mistyped URL is one of the most common causes of 404 errors.
- **Prioritize Browser 404s over Bot 404s.** Browser errors indicate real readers hitting dead links. Fix those first, then address bot-related errors for SEO. Use <a href="https://docs.document360.com/docs/links-status" target="_blank">Link status analytics</a> to find and fix the underlying broken links across your knowledge base.
- **Export and bulk-import redirect rules after a major restructure.** Navigate to **Settings** (<span class="fa-solid fa-gear"></span>) and go to **Knowledge base site** and then **Article redirect rules** to import rules in bulk rather than adding them one by one.

---

## FAQ

<div class="faq-wrapper" data-type="details-wrapper">
<details open>
<summary><p>What is a 404 error?</p></summary>
<div data-type="details-content">
<p>A 404 error occurs when a webpage cannot be found. This typically happens when a URL has been deleted or changed without a redirect rule being set up.</p>
</div>
</details>
<button class="details-arrow" type="button"></button>
</div>

<div class="faq-wrapper" data-type="details-wrapper">
<details>
<summary><p>What causes a 404 error?</p></summary>
<div data-type="details-content">
<ul>
<li><strong>Deleted URL:</strong> The page no longer exists.</li>
<li><strong>Changed URL:</strong> The URL was changed but no redirect was set up. See <a href="https://docs.document360.com/docs/article-redirect-rules" target="_blank">Article redirect rules</a>.</li>
<li><strong>Incorrect URL:</strong> The URL was mistyped or linked incorrectly.</li>
<li><strong>Server issues:</strong> A server problem prevented the page from loading.</li>
</ul>
</div>
</details>
<button class="details-arrow" type="button"></button>
</div>

<div class="faq-wrapper" data-type="details-wrapper">
<details>
<summary><p>Why is it important to fix 404 errors?</p></summary>
<div data-type="details-content">
<p>A high number of 404 errors harms both reader experience and SEO. Search engines like Google and Bing may penalize sites with many unresolved 404 errors, reducing your knowledge base's discoverability.</p>
</div>
</details>
<button class="details-arrow" type="button"></button>
</div>

<div class="faq-wrapper" data-type="details-wrapper">
<details>
<summary><p>How do I fix 404 errors in my knowledge base?</p></summary>
<div data-type="details-content">
<ol>
<li>Navigate to <strong>Analytics</strong> (<span class="fa-duotone fa-solid fa-chart-mixed"></span>) and click <strong>Link status</strong>. The <a href="https://docs.document360.com/docs/article-redirect-rules" target="_blank">Link status analytics</a> page shows all broken, redirected, and working links across your project.</li>
<li>Click <strong>Filter</strong>, select <strong>Broken</strong> from the <strong>Status</strong> dropdown, and click <strong>Apply</strong>.</li>
<li>Click <strong>Export CSV</strong> to download the list of broken links.</li>
<li>Navigate to <strong>Settings</strong> (<span class="fa-solid fa-gear"></span>) and go to <strong>Knowledge base site</strong> and then <strong>Article redirect rules</strong>.</li>
<li>Add a redirect rule for each broken URL, or import rules in bulk.</li>
</ol>
</div>
</details>
<button class="details-arrow" type="button"></button>
</div>