HTTP/HTTPS and redirect chains: build one canonical path

A domain can usually be requested through four common entry points: HTTP without www, HTTP with www, HTTPS without www, and HTTPS with www. Without a consistent policy, multiple variants may return content, create different redirect paths, or disagree with canonical tags and internal links.

The test keeps the original path and query string while changing only the protocol and hostname variant. This reveals broad redirect rules that work on the home page but fail on deep pages, filtered views, tracking parameters, or campaign URLs.

• Preferred result Every alternate entry point reaches the same HTTPS URL and finishes with a successful response.
• Warning pattern A variant needs several hops, changes the path, drops the query, or returns content on a second hostname.
• Failure pattern A loop, network error, invalid Location header, or final 4xx/5xx response prevents a usable destination.

A redirect response uses a 3xx status and a Location header. The status communicates whether the move is permanent or temporary and, for non-GET requests, whether the request method must be preserved.

• 301 Moved Permanently The established choice for permanent page or hostname moves. Historical clients may change non-GET methods.
• 308 Permanent Redirect Permanent like 301, while explicitly preserving the request method and body.
• 302 Found A temporary destination. Use it when the original URL is expected to become authoritative again.
• 307 Temporary Redirect Temporary like 302, while preserving the request method and body.
• 303 See Other Directs the client to retrieve another URL with GET, commonly after a form or write operation.

A hostname normalization rule should normally transform only the hostname or protocol. Redirecting every old URL to the home page hides broken mappings and gives crawlers a destination that does not match the requested content.

Query parameters require intent. Preserve parameters needed for content, language, filtering, attribution, or application state. Remove known tracking parameters only through a deliberate policy, and make sure analytics and canonical handling agree with that policy.

Requested:  http://www.example.com/products/widget?color=blue
Preferred:  https://example.com/products/widget?color=blue

Avoid:      http://www.example.com/products/widget?color=blue
         →  https://www.example.com/products/widget
         →  https://example.com/

Map each hop from the requested URL to the final response. A common chain is HTTP → HTTPS on the old hostname → HTTPS on the preferred hostname. Combine those rules so the first response points directly to the final URL.

Then update internal links, canonical URLs, hreflang values, XML sitemaps, structured data, and marketing templates to use the destination directly. Redirects protect old external references; they should not be the normal path for your own links.

• Server or edge rules Best for protocol, hostname, and large deterministic URL migrations.
• Application redirects Useful when the destination depends on content state, permissions, or business logic.
• Redirect map Use an explicit old-to-new mapping for migrations where paths do not follow one predictable pattern.