Differences Between IIS URL Rewriting and ASP.NET Routing

There are the following main conceptual differences between IIS URL rewriting and ASP.NET routing:

1. URL rewriting is used to manipulate URL paths before the request is handled by the Web server. The URL rewriting module does not know which handler will eventually process the rewritten URL. In addition, the actual request handler might not know that the URL has been rewritten.
2. ASP.NET routing is used to dispatch a request to a handler based on the requested URL path. As opposed to URL rewriting, the routing module knows about the handlers and selects the handler that should generate a response for the requested URL. You can think of ASP.NET routing as an advanced handler-mapping mechanism.

In addition to these conceptual differences, there are the following functional differences between IIS URL rewriting and ASP.NET routing:

1. The IIS URL Rewrite module can be used with any type of Web application, which includes ASP.NET, PHP, ASP, and static files. ASP.NET routing can be used only with .NET Framework-based Web applications.
2. The IIS URL Rewrite module works the same way regardless of whether integrated or classic IIS pipeline mode is used for the application pool. For ASP.NET routing, it is preferable to use integrated pipeline mode. ASP.NET routing can work in classic mode, but in that case the application URLs must include file name extensions or the application must be configured to use "*" handler mapping in IIS.
3. The IIS URL Rewrite module can make rewriting decisions based on domain names, HTTP headers, and server variables. By default, ASP.NET routing works only with URL paths and with the HTTP-Method header.
4. In addition to rewriting, the URL Rewrite module can perform HTTP redirection, issue custom status codes, and abort requests. ASP.NET routing does not perform these tasks.
5. The URL Rewrite module is not extensible in its current version. ASP.NET routing is fully extensible and customizable.

Which Option Should You Use?

What does all this information mean if you need to choose a technology to enable clean URLs for your Web applications? In this section, we explain how to make this choice.
If your Web application is built by using anything except ASP.NET, use the IIS URL Rewrite module. Otherwise, the rules are:

1. If you are developing a new ASP.NET Web application that uses either ASP.NET MVC or ASP.NET Dynamic Data technologies, use ASP.NET routing. Your application will benefit from native support for clean URLs, including generation of clean URLs for the links in your Web pages. Note that ASP.NET routing does not support standard Web Forms applications yet, although there are plans to support it in the future.
2. If you already have a legacy ASP.NET Web application and do not want to change it, use the URL Rewrite module. The URL Rewrite module lets you translate search engine-friendly URLs into a format that your application currently uses. Also, it lets you create redirect rules that can be used to redirect search engine crawlers to clean URLs.

In practice, however, the choice does not have to be either/or. The technologies can be used together and can complement each other. In the following sections, we outline some scenarios where you can use ASP.NET routing and IIS URL rewriting together.

Related posts:

Rewrite URL-Implement URL Rewriting in ASP.NET

Differences Between IIS URL Rewriting and ASP.NET Routing
SEO with ASP.NET 4.0 Framework

Books
Professional Search Engine Optimization with ASP.NET: A Developer's Guide to SEO (Wrox Professional Guides)
Professional IIS 7 and ASP.NET Integrated Programming
Leveraging httpModules for Better ASP.NET applications (Wrox Briefs)
Ultra-Fast ASP.NET: Build Ultra-Fast and Ultra-Scalable web sites using ASP.NET and SQL Server
Beginning DotNetNuke Skinning and Design (Programmer to Programmer)

Introduction: Mastering Digital Growth in 2025—From SEO to Social Media and AI

In 2025, digital success isn’t just about having an online presence—it’s about strategically connecting the dots between SEO, web design, content creation, and social media. For small businesses and marketers alike, staying ahead means embracing the latest tools and trends that shape how we rank, engage, and grow online.

Whether you're aiming to win local search with cutting-edge SEO for Small Business in 2025: How to Win Local Search and Drive Growth, boost website performance through HTML validation, or understand the impact of bad backlinks on rankings, every element of your digital strategy must work in harmony.

Meanwhile, powerful shifts in content production are emerging, with AI reshaping how we create top-tier content and revolutionizing open source CMS platforms alike.

Social media is no longer just for engagement—it’s now a vital part of your SEO strategy. Learn how to optimize your posts with SEO tools, take advantage of the latest social media advertising trends in 2025, and discover smart social media optimization tricks to strengthen your online presence.

Finally, don’t underestimate the tech stack behind your site. The often-overlooked link between SEO and web hosting can make or break your digital visibility.

This blog brings together the latest insights to help you navigate and thrive in the digital ecosystem of 2025. Ready to elevate your strategy?

SEO for Small Business in 2025: How to Win Local Search and Drive Growth

Build Better Websites: How HTML Validation Enhances SEO

How Social Media SEO Tools Help Optimize Your Social Media Posts

Bad Backlinks Kill Search Engine Rankings: What You Need to Know

Unlocking the Power of AI in Open Source CMS Platforms

AI Is Changing How We Create Top-Tier Content

Social Media and Advertising in 2025: What You Need to Know

The Symbiotic Relationship Between SEO and Web Hosting in 2025

Social Media Optimization Tricks to Boost Your Online Presence