Information checked: 21 July 2026.
A redirect sends a request from one URL to another. It is appropriate when content has moved or a canonical route must be enforced, but it should not be used to conceal missing content or compensate for an uncontrolled URL strategy.
In brief: Map each old URL to the closest relevant destination and test the final response.
Choose a redirect deliberately
| Type | Use | Caution |
|---|---|---|
| 301 | Permanent move for most HTTP/1.1 implementations | Caches and signals a lasting change |
| 308 | Permanent move preserving method | Confirm application and client support |
| 302 | Temporary move | Do not leave indefinitely when the move is permanent |
| 307 | Temporary move preserving method | Useful for method-sensitive requests |
| Meta refresh or JavaScript | Fallback where server control is unavailable | Slower, less robust and not first choice |
Build a redirect map before a migration
- Export every indexable and valuable old URL.
- Choose a one-to-one equivalent based on purpose, not keywords alone.
- Mark URLs with no replacement for 404 or 410.
- Implement rules without broad wildcards that capture unrelated paths.
- Test status, chain, destination, canonical and page content.
- Keep monitoring after launch.
Preserve methods and security where relevant
Redirecting a simple page view differs from redirecting form submissions, APIs or checkout requests. Avoid changing methods or exposing query parameters without understanding the application behaviour.
Readiness check
Every migration redirect should complete in one hop where practical and land on a page that genuinely satisfies the old request.
What often breaks
Redirect rules are often added one at a time without a central register. Later changes create overlapping wildcards, methods are altered unexpectedly and nobody knows whether an old rule remains necessary. The browser appears to work because it follows the chain automatically.
Information to keep outside the platform
- Master redirect map
- Server/CDN/CMS rule locations
- Status and destination tests
- Temporary-rule expiry dates
- Post-migration monitoring
First implementation step
Export every current redirect from all technical layers and combine them into one reviewable map. Identify duplicates, broad patterns and routes with more than one hop.
Sources and date checked
This practical guidance was checked against the following primary sources. Date checked: 21 July 2026.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.