SEO 最佳實踐建議統一網域存取入口,避免重複內容索引。常見需求:將 `https://example.com` (裸域) 永久重導向至 `https://www.example.com`,保持路徑與查詢字串不變。
public class MvcApplication : HttpApplication
{
protected void Application_BeginRequest(object sender, EventArgs e)
{
var request = HttpContext.Current.Request;
var url = request.Url.ToString().ToLowerInvariant();
// 目標:將 https://jb51.net/* 導向 https://www.jb51.net/*
const string sourceDomain = "https://jb51.net";
const string targetDomain = "https://www.jb51.net";
if (url.StartsWith(sourceDomain, StringComparison.OrdinalIgnoreCase))
{
string newUrl = targetDomain + url.Substring(sourceDomain.Length);
// 301 永久重導向 (SEO 友善,傳遞權重)
HttpContext.Current.Response.RedirectPermanent(newUrl);
}
}
}
| 方法 | HTTP 狀態碼 | SEO 影響 | 瀏覽器快取 |
|---|---|---|---|
| Response.RedirectPermanent | 301 Moved Permanently | 傳遞權重,搜尋引擎更新索引 | 會被快取 |
| Response.Redirect | 302 Found | 不傳遞權重,視為暫時 | 不快取 |
**永久重導向務必用 301**。
使用 `StringComparison.OrdinalIgnoreCase` 或 `.ToLowerInvariant()` 確保 `HTTP://JB51.NET` 也能正確導向。
`url.Substring(sourceDomain.Length)` 保留原始路徑 `/about`、查詢 `?id=123` 等,實現精確對應導向。
protected void Application_BeginRequest(object sender, EventArgs e)
{
var request = HttpContext.Current.Request;
var url = request.Url;
// 規則清單:來源 Host → 目標 Host
var redirects = new Dictionary(StringComparer.OrdinalIgnoreCase)
{
{ "jb51.net", "www.jb51.net" },
{ "old-domain.com", "www.new-domain.com" },
{ "blog.example.com", "www.example.com/blog" } // 含路徑前綴
};
if (redirects.TryGetValue(url.Host, out string targetHost))
{
var builder = new UriBuilder(url)
{
Host = targetHost,
// 保持 Scheme (http/https)、Port、Path、Query、Fragment
};
// 若目標包含路徑前綴 (如 blog.example.com → www.example.com/blog)
if (targetHost.Contains('/'))
{
var parts = targetHost.Split('/', 2);
builder.Host = parts[0];
builder.Path = "/" + parts[1].TrimStart('/') + url.PathAndQuery.TrimStart('/');
}
Response.RedirectPermanent(builder.Uri.ToString());
}
}
在 IIS URL Rewrite 模組處理,不經 ASP.NET 管線,效能更高:
<system.webServer>
<rewrite>
<rules>
<rule name="Canonical Host - Redirect to WWW" stopProcessing="true">
<match url="(.*)" />
<conditions>
<add input="{HTTP_HOST}" pattern="^jb51\.net$" />
</conditions>
<action type="Redirect" url="https://www.jb51.net/{R:1}" redirectType="Permanent" />
</rule>
<!-- HTTPS 強制 -->
<rule name="Force HTTPS" stopProcessing="true">
<match url="(.*)" />
<conditions>
<add input="{HTTPS}" pattern="off" />
</conditions>
<action type="Redirect" url="https://{HTTP_HOST}/{R:1}" redirectType="Permanent" />
</rule>
</rules>
</rewrite>
</system.webServer>
// Program.cs (.NET 6+)
var app = builder.Build();
// 內建中介軟體 (需安裝 Microsoft.AspNetCore.Rewrite)
app.UseRewriter(new RewriteOptions()
.AddRedirect("^$", "www.example.com") // 根路徑
.AddRedirect("(.*)", "www.example.com/$1") // 所有路徑
.AddRedirectToHttps()); // 強制 HTTPS
// 或自訂中介軟體
app.Use(async (context, next) =>
{
var host = context.Request.Host.Host;
if (host == "example.com")
{
var newUrl = $"https://www.example.com{context.Request.Path}{context.Request.QueryString}";
context.Response.Redirect(newUrl, permanent: true);
return;
}
await next();
});
ASP.NET MVC 3 在 `Application_BeginRequest` 使用 `Response.RedirectPermanent` 實現全站 301 重導向是經典做法。現代專案建議優先使用 **IIS URL Rewrite** 或 **ASP.NET Core Rewrite Middleware** 在更早管線階段處理,效能更好且支援 HTTPS 強制、多規則管理。核心原則:單一規範網域、301 永久重導向、保持路徑查詢字串、避免重導向鏈。