How to Fix Broken URLs After Migrating Joomla
Broken URLs after a Joomla migration are usually a routing, rewrite, document-root, menu-context, or hard-coded-link problem—not a reason to reinstall Joomla. Diagnose representative failures first, then correct the layer that owns each URL.
Classify the failure before changing redirects
Collect several failing URLs and record their HTTP status codes. Separate Joomla SEF routes from media files, extension routes, old-domain links, and URLs that changed because the menu structure changed. A migration-related 404 can come from Joomla routing, web-server rewriting, a changed document root, missing files, or an intentionally changed public URL. Avoid sending every 404 to the home page; that hides the real failure and creates poor search-engine signals.
Confirm the destination root and hostname
Verify DNS or your private hosts-file test reaches the intended server and that the virtual host points to the directory containing Joomla index.php and configuration.php. If the site moved between a subdirectory and the domain root, inspect RewriteBase, reverse-proxy rules, and any hard-coded base paths. Confirm both the apex and www hostnames behave as intended before troubleshooting individual Joomla routes.
Isolate Joomla SEF routing from server rewriting
Temporarily test whether a failing route works with index.php in the URL. If it does, Joomla routing is likely functioning and the web-server rewrite layer needs attention. On Apache, confirm the Joomla .htaccess rules are active and allowed; on Nginx or IIS, use the server-specific front-controller rules instead of Apache instructions. Review the web-server error and access logs immediately after a failing request.
Review menus, aliases, and hard-coded links
Open important menu items and verify publication state, access, language, aliases, parent relationships, and component targets. Search articles, modules, template overrides, custom HTML, and extension settings for the former domain or directory. Update links Joomla controls to their final destination rather than depending on redirects for permanent internal navigation.
Create redirects only for legitimate moved URLs
For a former public URL that has a clear replacement, create one direct permanent redirect at the Joomla Redirect component, web server, or edge layer you deliberately manage. Avoid redirect chains and loops. Preserve query strings only when the destination needs them, and do not redirect missing assets to unrelated pages.
Verify the repair and monitor remaining 404s
Test representative URLs while logged out, paste deep links directly into a new browser session, and clear only relevant Joomla, server, CDN, and browser caches. Crawl important sections and inspect logs for remaining 404s. If public URLs changed, update canonical output and sitemaps, then continue monitoring high-value old URLs during the migration period.
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.