What Is a URL Redirect?
URL redirect A URL redirect automatically sends a visitor from the URL they requested to a different destination URL. The server responds with a redirect status code and the new location, and the browser follows it. Redirects power short links, moved pages, and campaign links that can be repointed later.
At a glance
- A short link is a redirect: it forwards the short URL to the real destination.
- A 301 is permanent (SEO value transfers); a 302 or 307 is temporary (original URL is kept).
- Redirect chains (a redirect to a redirect) slow load and can leak tracking parameters.
- A managed redirect can be repointed without changing the link people already have.
How it works
Status code plus a new location
When a browser requests a redirecting URL, the server replies with a 3xx status code and a Location header naming the new URL. The browser then requests that new URL. The visitor usually sees only the final page, and with a short link the whole hop takes milliseconds.
Permanent vs temporary
A 301 (and its method-preserving cousin 308) says the move is permanent, so search engines pass ranking signals to the new URL and remember it. A 302 (and 307) says the move is temporary, so the original URL keeps its value. Choosing wrong can cost SEO equity or confuse crawlers.
Why short links use redirects
A short link is a deliberately temporary-feeling but stable redirect: the short URL stays constant while the destination behind it can change. That is what lets you repoint a printed or posted link, run A/B splits, or route by country and device.
URL redirect types at a glance
| What it tells search engines | Use it when | |
|---|---|---|
| 301 permanent | The page moved for good; pass ranking signals to the new URL and remember it | Domain moves, HTTPS upgrades, renamed pages |
| 302 temporary | The page is elsewhere for now; keep the original URL indexed | A/B tests, short campaigns, maintenance detours |
| 307 temporary strict | Same as 302, but the request method may not change | Temporary redirects in front of forms or APIs |
| 308 permanent strict | Same as 301, but the request method may not change | Permanent moves of form or API endpoints |
| Meta refresh or JavaScript | A weaker client-side hint; slower and invisible to HTTP tools | Static hosts where server redirects are unavailable |
Why it matters
Redirects are the plumbing of the web, and getting them wrong is expensive. The wrong type drains SEO value during a site move, a redirect chain slows every visitor and can drop tracking parameters, and a broken redirect sends people and search engines to a dead end. A managed redirect keeps the link stable while letting you change where it goes.
Frequently asked questions
Is a short link a redirect?
Yes. A short link is a redirect: the short URL is requested, the server records the click, and it forwards the visitor to the real destination. That single hop is what makes the link both trackable and editable.
What is the difference between a 301 and a 302 redirect?
A 301 is permanent, so search engines transfer ranking signals to the new URL and update their index. A 302 is temporary, so the original URL keeps its value. Use 301 for real moves and 302 for short-term or test redirects.
Do redirects hurt SEO?
A single, correct redirect does not. Problems come from the wrong type, long redirect chains that slow load, or redirects that break and return errors. Keep them to one hop, pick the right status code, and preserve query parameters.
Related terms
On Flyn
Sources
Create a trackable redirect
Every Flyn short link is a fast, editable redirect you can repoint, route, and measure anytime.