To set up URL rewrite rules in IIS, first install the URL Rewrite module via Web PI, Windows Features, or PowerShell with Install-WindowsFeature -Name Web-Url-Auth; next, create basic rules using the IIS Manager GUI by selecting your site, opening URL Rewrite, adding a rule, and specifying match patterns and redirect actions; for advanced configurations, edit the web.config file directly with proper XML syntax inside ; use common scenarios like forcing HTTPS, removing .html extensions, or redirecting domains by defining match patterns and appropriate redirect URLs; always test rules in development, back up web.config, and monitor logs for errors after deployment.

Setting up URL rewrite rules for IIS websites is a common task when you want to improve SEO, clean up old URLs, or redirect traffic. It’s not complicated once you understand the basics.

Install the URL Rewrite Module

Before setting up any rules, make sure the URL Rewrite module is installed in IIS. Without it, none of the rewrite features will be available.

• You can install it via the Web Platform Installer (Web PI) or using Windows Features.
• On newer Windows Server versions, use PowerShell with the command:
  Install-WindowsFeature -Name Web-Url-Auth

If you're on a shared hosting plan, check with your provider if the module is already installed — many managed environments have it enabled by default.

Basic Rule Setup via IIS Manager

The easiest way to create a rule is through the IIS Manager GUI, especially if you’re new to this or only need a few redirects.

Here’s how:

• Open IIS Manager and select your site
• Double-click "URL Rewrite"
• Click “Add Rule(s)” on the right-hand side
• Choose a template like Blank Rule or Inbound Rule
• Fill in the pattern, conditions, and action details

For example, if you want to redirect /old-page to /new-page, set:

• Requested URL: ^old-page$
• Action type: Redirect
• Redirect URL: /new-page

This method avoids having to edit XML files directly and reduces chances of syntax errors.

Editing web.config for Advanced Rules

Once comfortable, editing the web.config file gives more control and flexibility.

A basic redirect rule looks like this inside <system.webserver></system.webserver>:

<rewrite>
  <rules>
    <rule name="Redirect old page" stopProcessing="true">
      <match url="^old-page$" />
      <action type="Redirect" url="/new-page" />
    </rule>
  </rules>
</rewrite>

Some tips:

• Use stopProcessing="true" to prevent other rules from interfering
• For complex patterns, use regular expressions (RegEx)
• Test rules in a dev environment before deploying live

Keep a backup of your web.config before making changes — one typo can break your site.

Common Use Cases and Examples

Here are a few typical scenarios you might run into:

• Force HTTPS:
  Match pattern: (.*)
  Condition: {HTTPS} equals off
  Action: Redirect to https://{HTTP_HOST}/{R:1}

• Remove .html extension:
  Match pattern: ^(.*).html$
  Action: Redirect to /{R:1}

• Redirect entire site to new domain:
  Match pattern: (.*)
  Action: Redirect to https://newdomain.com/{R:1}

These aren’t just one-off fixes — they help maintain consistent URLs and user experience over time.

Basically, that's all there is to it. The setup isn't too hard once you get used to working with either the GUI or the config file. Just remember to test each rule after deployment and monitor server logs for any unexpected 404s or redirect loops.

The above is the detailed content of Setting Up URL Rewrite Rules for IIS Websites. For more information, please follow other related articles on the PHP Chinese website!