---
title: Modify error handling pages
slug: configured-commerce/docs/classic-modify-error-handling-pages
docTags: 
createdAt: 2026-08-13T10:46:26.000Z
---

Manage error-handling page templates in the Optimizely Configured Commerce to provide contextual help or links to existing content when website errors occur. Configured Commerce provides three standard error handling pages:

- 403: Unauthorized Access: The user does not have permission to view the requested file or resource.
- 404: Page Not Found: The page or file cannot be found or does not exist.
- 500: Unhandled Error (aka HTTP 500 error): Generic error suggesting a problem with the website's server.

Use the steps below to customize these pages:

1. To customize a page, sign in to the Admin Console as an **ISC\_ContentEditor** or **ISC\_ContentAdmin**, then access the website using **View Websites**.
2. Select the **Show CMS** icon in the upper left corner of the screen, then select **Show CMS**.
3. Select the **Content Tree** in the upper left corner to expand the Content Tree.
4. Click **Edit**.
5. Select the expand arrow to the left of **Home** to expose the section.
6. Select the expand arrow to the left of **Unhandled Error** to expose the section.

   ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/ZdpA5u3A2oXK01Pmdf-FD-20260720-144614.png)
7. Select a page: **Unhandled Error**, **Page Not Found** or **Unauthorized Access**.
8. Click **Edit this Page** in the upper right corner.
9. Enter the desired content into the appropriate field. For instance, the **Page Title** could be updated from **Page Not Found** to **Page No Longer Exists**.
10. Scroll down and click **Save**. The edited page in the Content Tree will appear orange until it is published.

    :::hint{type="info"}
    **Note**

    If a widget is modified on a page, an orange box surrounds the widget until it is published. Some modifications update the widget, but do not require the widget to be published; for example, if the **Page Information** and **Page Title** are modified. the widget automatically inherits that edit.
    :::
11. If you are an **ISC\_ContentApprover** or **ISC\_ContentAdmin**, click **Publish** in the upper right corner to approve the new content and publish it to the website.

## Troubleshoot

If the Application's error handling pages are not returning correctly for the expected events, or if users are seeing the generic IIS error page, the **web.config** file may not be set up correctly. The example below shows the proper mapping to ensure the correct page returns:

```clike
<customErrors mode="RemoteOnly" defaultRedirect="/Error">      <error statusCode="403" redirect="/Error?ErrorCode=403" />      <error statusCode="404" redirect="/Error?ErrorCode=404" />      <error statusCode="500" redirect="/Error?ErrorCode=500" />    </customErrors>
```