How to Configure Joomla SEF URLs on Microsoft IIS
Joomla SEF URLs on Microsoft IIS require Joomla's SEF routing plus an IIS URL Rewrite rule that internally sends clean requests to Joomla's index.php. IIS uses web.config, not Apache .htaccess.
Verify prerequisites and back up web.config
Confirm Joomla works before changing routing and verify the IIS URL Rewrite module is available for the site. Back up the current web.config; it may already contain PHP handlers, request filtering, security headers, or hosting-specific settings that must be preserved.
Enable Joomla SEF routing first
- Open System → Global Configuration → Site.
- Enable Search Engine Friendly URLs.
- Leave Use URL Rewriting disabled.
- Save and test several frontend routes.
This proves Joomla can generate and parse SEF routes before IIS is asked to hide index.php.
Configure the IIS front-controller rewrite
Use Joomla-provided or host-approved IIS guidance to route requests that are not real files or directories internally to index.php. Merge the rewrite into the existing web.config instead of replacing unrelated configuration. Keep the XML well formed and avoid duplicate rewrite sections.
The public URL can omit index.php, but Joomla still uses that file internally as its front controller.
Enable Use URL Rewriting after IIS is ready
Return to Global Configuration, enable Use URL Rewriting, save, and test a known menu route immediately. If clean routes return 404 while equivalent index.php routes work, focus on IIS URL Rewrite, the application path, and web.config rather than changing article aliases.
Handle IIS applications and proxies carefully
A Joomla site installed as an IIS application below the domain root may need rules that reflect that application boundary. Reverse proxies and load balancers can also change the visible scheme, host, or path. Keep canonical redirects separate from the front-controller rewrite and avoid rules that repeatedly redirect their own output.
Test and preserve a rollback path
- Test the home page, nested menu items, articles, categories, login, and pagination.
- Confirm static files are served directly.
- Request a deliberately invalid path and confirm an appropriate 404.
- Review IIS and PHP logs for failures.
If the change breaks routing, disable Joomla URL Rewriting and restore the backed-up web.config before making the next controlled change.
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.