Magento2 : Content Pages are not working on frontend

Magento2 : Content Pages are not working on frontend

October 6, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento2 : Content Pages are not working on frontend

Magento2: Content Pages Not Working on Frontend

If you’re facing issues where your Magento2 pages aren’t displaying properly on the frontend, resulting in a “Whoops, our bad…” (404 Not Found) error despite being created and saved correctly from the admin interface, then this guide is for you. Let’s dive into some common troubleshooting steps to resolve this issue.

Understanding the Problem

The 404 Not Found error typically occurs when Magento can’t locate the requested page in your store’s URL rewrites or route configurations. This could be due to incorrect URL key settings, missing router configuration, or cache-related issues.

Step-by-Step Troubleshooting

Reindexing and Cache Clearing

You’ve already attempted the standard troubleshooting steps of clearing the cache (bin/magento cache:flush), reindexing (bin/magento indexer:reindex), and deploying static content (bin/magento setup:static-content:deploy). These commands are essential for ensuring that Magento’s data is up-to-date and accessible.

However, if the 404 error persists after these initial steps, let’s explore some deeper troubleshooting techniques:

Checking URL Key Settings

Navigate to your page in the admin interface (Content > Pages) and ensure that the URL key field is filled with a valid, lowercase, hyphen-separated string. For example, if the page title is “FAQs”, the URL key should be “faqs”.

Verifying Router Configuration

In some cases, the router configuration might not be set up correctly for your custom pages. To verify this:

  1. Open the app/code/Magento/Page/etc/route.xml file in a text editor.
  2. Look for an entry within the <config> tag that matches your page’s URL key.

For instance:

<route id="faq" frontName="page">
  <module name="Magento_Page"/>
</route>

If no matching route is found, you might need to create a custom router or update the existing one to include your new page.

Inspecting URL Rewrite Table

The core_url_rewrite database table stores Magento’s rewrite rules. To check if your page has been added correctly:

  1. Log in to your MySQL server using a client like phpMyAdmin.
  2. Navigate to the core_url_rewrite table.
  3. Search for rows with the target path matching your page ID (e.g., “catalog/category/view/id/7”).

If no relevant entries are found, you can manually insert a new row:

INSERT INTO core_url_rewrite (url_rewrite_id, entity_type, entity_id, target_path)
VALUES ('<new_id>', 'page', '<your_page_id>', 'catalog/page/view');

Enabling Developer Mode

Enabling developer mode can provide more detailed error messages and help pinpoint the issue. To do this:

  1. Open your Magento2 root folder in a text editor.
  2. Rename the app/bootstrap.php file to bootstrap.php.

This will enable developer mode, which can reveal underlying issues causing the 404 errors.

Conclusion

When facing “Whoops, our bad…” (404 Not Found) errors with your Magento2 pages, remember to:

  • Always clear cache, reindex, and deploy static content.
  • Verify URL key settings and check for matching router configuration.
  • Inspect the core_url_rewrite table and manually insert entries if necessary.

If you’re still encountering issues or need further assistance, consider reaching out to our Magento2 development experts at LaravelCompany. Our team specializes in Magento e-commerce solutions and can help diagnose and resolve complex technical problems.

Don’t let 404 errors hold your business back – with the right troubleshooting approach, you can keep your Magento2 store running smoothly and provide a seamless shopping experience for your customers.

Magento 2 Cache Indexing Admin

Our network