How to Fix “Page Not Found” Errors in Joomla
Determine whether the response is really a 404
Open the failing URL directly and inspect its HTTP status with browser developer tools. Joomla can render a friendly error page while still returning a meaningful status code. A true 404 means the requested route or resource was not found; a 403, 500, redirect loop, or proxy-generated error needs a different investigation.
Check the menu item, article, and published state
For a Joomla content page, confirm the target article or component item still exists, is published, is within its publishing dates, and is accessible to the intended user group. Check the menu item that creates the route and verify it points to the expected item. A renamed, unpublished, trashed, or access-restricted target can make an old public URL stop resolving as expected.
Compare the current alias and route
If the article, category, or menu alias changed, old bookmarked or indexed URLs may no longer match the route Joomla now builds. Open the content through its current menu path and compare the generated URL with the failing one. Restore the intended alias or create an appropriate redirect rather than duplicating content merely to satisfy an obsolete URL.
Test URL rewriting separately
If Search Engine Friendly URLs or URL rewriting changed recently, compare behavior with the supported Joomla routing configuration and the web server rewrite file. A malformed or inappropriate .htaccess rule can prevent valid routes from reaching Joomla. Preserve the existing file before testing and do not copy arbitrary rewrite rules from another hosting stack.
Distinguish Joomla routes from missing static files
A missing image, stylesheet, script, download, or other physical file is not fixed by changing a Joomla menu alias. Use the Network panel and server filesystem to identify the exact missing resource. Correct its path, restore the expected file from a trusted source, or update the page that references it.
Use redirects for intentionally moved content
When a public page was deliberately moved or renamed, create a maintained redirect from the old URL to the correct replacement where appropriate. This is safer for visitors and search engines than leaving important inbound links broken. Avoid broad wildcard redirects that hide unrelated routing errors or send every missing URL to the home page.
Retest as both guest and authorised user
Access levels can change what a visitor is allowed to view. Joomla programmer documentation notes that applications may return 403 when a user is not authorised, so do not label every inaccessible page a 404 without checking authentication and access. Retest the final route as the audience that originally experienced the problem and confirm the expected status and content.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.