Redirect
Overview
A redirect is an instruction that sends a client from one URL or route to another destination.
It matters because redirects affect navigation, SEO, caching, migrations, and how users or bots reach content.
What a Redirect Does
Redirects are used to move traffic without leaving the original request unresolved.
They commonly help with:
- URL changes
- domain migrations
- canonicalization
- HTTP to HTTPS changes
- legacy link preservation
That makes them a key tool in both application routing and site maintenance.
Why Redirects Matter
Redirects matter because content and site structure change over time.
Teams use them to:
- preserve links
- avoid dead ends
- support replatforming
- guide crawlers and browsers to the right destination
Without redirects, many content moves become user and SEO failures.
Redirects and HTTP
Redirect behavior is closely tied to http.
That matters because:
- status codes carry meaning
- permanent and temporary redirects behave differently
- browsers and crawlers may cache them differently
The wrong status code can create long-lasting routing mistakes.
Practical Caveats
Redirects are useful, but they can become messy fast.
- Chains and loops are common mistakes.
- Permanent redirects should be chosen carefully.
- Platform-level and app-level redirects can conflict.
- Too many redirects hurt clarity and sometimes performance.
Redirect strategy works best when it is intentional and documented.
Frequently Asked Questions
Is a redirect always an HTTP redirect?
Not always. The term can also be used more loosely in app routing, but HTTP redirects are the most important web form.
Are all redirects good for SEO?
No. The type, target, chain behavior, and implementation quality all matter.
Should a redirect be permanent by default?
Not automatically. The right status depends on whether the change is truly permanent.
Resources
- MDN: Redirections in HTTP
- Cloudflare: Redirect Rules
- NGINX: Return and Rewrite