How to Fix Joomla SEF URLs Not Working

When Joomla SEF URLs fail, first determine whether the problem is Joomla routing or web-server rewriting. Testing SEF with Use URL Rewriting disabled separates those layers and prevents random .htaccess changes from hiding the real cause.

Establish a clean baseline

  1. Go to System → Global Configuration → Site.
  2. Set Search Engine Friendly URLs to Yes.
  3. Set Use URL Rewriting to No.
  4. Save and clear relevant Joomla/CDN caches.
  5. Test several frontend routes.

If readable URLs containing index.php work, Joomla's SEF router is functioning. Focus next on the server rewrite configuration.

If SEF routes fail even with rewriting off

Test a simple core Articles menu item. Check that the menu item and content are published and accessible, and review aliases for unexpected duplicates or hierarchy changes. If core routes work but one extension does not, investigate that extension's router and compatibility.

Also test direct requests rather than only clicking generated links; Joomla must be able both to build and parse the route.

If failure begins only after removing index.php

This points strongly to the server rewrite layer. On Apache, verify that the active .htaccess contains the appropriate Joomla rules and that the server permits them. On Nginx or IIS, use the server's native rewrite configuration instead.

For a Joomla installation in a subdirectory, confirm the document root and base path. A wrong base can send otherwise valid routes to the wrong location.

Use the HTTP status to narrow the problem

  • 404: request is not reaching the intended Joomla route, or Joomla cannot resolve that route.
  • 500: inspect the web-server/PHP error log for an invalid directive or runtime error.
  • 403: inspect access-control, security, WAF, and file/directory rules.
  • Redirect loop: inspect HTTPS, hostname, proxy/CDN, canonical, and server redirects together.

Record the exact failing URL and timestamp so it can be matched to logs.

Check caches and infrastructure

Purge Joomla cache plus any hosting, reverse-proxy, CDN, or browser cache that may preserve old redirects or 404 responses. If a CDN is present, temporarily bypass it when possible to determine whether the origin server behaves differently.

Verify the fix

  1. Test the home page and several deep menu routes.
  2. Paste clean URLs directly into a private browser window.
  3. Test more than one component.
  4. Check canonical URLs and redirects.
  5. Review server logs for new 404/500 responses.

Once the baseline is stable, re-enable only the URL features you actually need and keep a copy of the working server configuration.


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.

Open a Support Ticket